Alt account of @Badabinski

Just a sweaty nerd interested in software, home automation, emotional issues, and polite discourse about all of the above.

  • 0 Posts
  • 17 Comments
Joined 3 months ago
cake
Cake day: June 9th, 2024

help-circle

  • The advice I’ve always heard is that if you can do it yourself, it’s always better. Animals can’t tell you that they’re sick, so every bit of info you can get on how they’re doing is important. Having the machine automatically clean the litter box deprives you of that option.

    With that being said, a clean litterbox is also really important. I plan on getting a couple of cats in the next 5 years after I’ve gotten my shit together (cats and incredibly messy houses don’t mix), and I will probably get an automatic litter box because I don’t want my depressive episodes to result in my cats being miserable. As this post shows, you should do your research. Find a litter box that has been endorsed by multiple unrelated reviewers if possible. Some of these boxes are dangerous, and many of them are kinda worthless.

    The video in the OP was recommended to me a few days ago and was my introduction to this whole fiasco. This person has done a ton of reviews and has a couple of boxes he’d recommend.

    EDIT: I literally linked to the video in the OP… I thought it was the video from one of the people who had a cat die.


  • Badabinski@kbin.earthtoMemes@lemmy.mlawHell Naw
    link
    fedilink
    arrow-up
    1
    ·
    6 days ago

    Hopefully we’ll be able to find a working one soon :( our emissions here are exclusively OBD2 based for anything 1996 or newer. I’ll probably do what some other folks have recommended and try to “remanufacture” one myself.

    EDIT: no idea why my client decided to post my comment twice.



  • Badabinski@kbin.earthtoLinux@lemmy.mlGoldilocks distro?
    link
    fedilink
    arrow-up
    26
    arrow-down
    8
    ·
    6 days ago

    For me, it’s Arch for desktop usage. When I first started using Arch it would not have been Arch, but now it’s Arch. The package manager has great ergonomics (not great discoverability, but great ergonomics), it’s always up to date, I can get a system from USB to sway in ~20 minutes (probably be faster if I used the installer), it’s fast because it doesn’t enable many things by default, and it’s honestly been the most reliable distro I’ve ever used. I used to use OpenSUSE ~10 years ago, and that broke more in one year than Arch has in ten.

    I personally feel like Arch’s unreliable nature has been overstated. Arch will give you the rope to hang yourself if you ask for it, but if you just read the emails (or use a helper that displays breaking changes when updating like paru) and merge your pacnews then you’ll likely have a rock solid system.

    Again, this is all just my opinion. It’s easy for me to overlook or forget all of the pain and suffering I likely went through when learning how to Arch. I won’t recommend it to you, but I’ll happily say how much I’ve come to enjoy using it.




  • Badabinski@kbin.earthtoMemes@lemmy.mlawHell Naw
    link
    fedilink
    arrow-up
    25
    arrow-down
    1
    ·
    6 days ago

    Seriously. The ECU in my partner’s truck decided that it was done with magic smoke and Marie Kondo’d that shit out, leaving her stranded. Her truck is an old 2002 Dodge Dakota that we’ve been nursing along while the used car market cools down (we want to get her something small and fuel efficient, but cars cost too damn much). Back in 2000 or 2001, some bean counter at Dodge decided that the company really had to cheap the fuck out with their ECUs for the 2002 model year. Because of this, any 2002 Dodge truck has either had its ECU replaced or is a ticking fucking time bomb.

    What’s even better is that nobody makes these shit-ass ECUs anymore. The only replacements you can get are remanufactured units, and it’s highly likely that you’ll get at least one dud before you can find anything decent. We’ve been a tiiiiiiny bit less lucky than that, meaning we’re on our 13th ECU. Our mechanic has gone through everything else to make sure there’s not something external that’s exploding the ECUs, and he hasn’t found anything. Over the course of like 9 weeks, we’ve completely deleted the stock of these stupid things in Utah and all of the surrounding states. We’re now ordering one from Florida that’s been remanufactured by a different company which hopefully won’t grenade itself.

    Fuck American car companies, and apologies to anyone who’s currently having a hard time sourcing an ECU for a 2002 Dodge Dakota. We screened all the bad ones out for you. The only good part about all of this for us is that our mechanic isn’t charging us for anything more than one ECU replacement. The damn truck has been in the shop for 9 weeks, and we’re only going to pay like $1000.





  • The tiered storage stuff is pretty cool. You can say “I want this data on this disk, so if I get a cache miss from a faster disk/RAM it’ll come from this other disk first.”

    I believe it also has some interesting ways of handling redundancy like erasure coding, and I thiiiink it does some kind of byte-level deduplication? I don’t know if that’s implemented or is even still planned, but I remember being quite excited for it. It was supposed to be dedupe without all of the hideous drawbacks that things like ZFS dedupe have.

    EDIT: deduplication is absolutely not a thing yet. I don’t know if it’s still on the roadmap.

    EDIT: Erasure coding is deffo implemented, however.


  • Badabinski@kbin.earthtoLinux@lemmy.mlHyprland is now fully independent!
    link
    fedilink
    arrow-up
    62
    arrow-down
    4
    ·
    edit-2
    2 months ago

    What if you need to file a bug? What if you have a question on the config that’s not easily answered by the docs? If you never, ever find bugs and never, ever have questions, then sure, separate the two. There are genuinely people like that, but they’re not common. If you’re one of them, then I’m genuinely glad for you.

    My opinion is this: You use software. You don’t use people, but you sure as hell rely on them.





  • The other person may have responded with a fair amount of hostility, but they’re absolutely correct. I run Kubernetes clusters hosting millions of containers across hundreds of thousands of VMs at my job, and OOMKills are just a fact of life. Apps will leak memory, and you’re powerless to fix it unless you’re willing to debug the app and fix the leak. It’s better for the container to run out of memory and trigger a cgroup-scoped OOM kill. A system-wide OOM kill will murder the things you love, shit in your hat, and lick your face like David Tennant licked Krysten Ritter.