That’s why projects like this are great: https://github.com/Hypfer/esp8266-midea-dehumidifier
My Midea Cube dehumidifier can never be bricked and will never send data outside of my home. It talks to Home Assistant via MQTT and nothing else.
Alt account of @Badabinski
Just a sweaty nerd interested in software, home automation, emotional issues, and polite discourse about all of the above.
That’s why projects like this are great: https://github.com/Hypfer/esp8266-midea-dehumidifier
My Midea Cube dehumidifier can never be bricked and will never send data outside of my home. It talks to Home Assistant via MQTT and nothing else.
I’ll mirror what others have said. Arch is the most stable distro I’ve ever used over the long term. Even with heavy AUR use, I’ve been rocking the same installation for over a decade on one of my computers.
Each VM can be sized appropriately for the demands of the container. With docker desktop, you can’t have a container use all of your system cores without making the VM have access to all of your cores all the time always. One of the biggest benefits (imo) of running containers on a Linux workstation is that if you don’t define a CPI limit, a container can use all the compute/memory on your system. You just can’t do that with Docker desktop. This also affects multi threaded container builds when you’re using buildkit.
Being able to spin up a vm to build a container with all cores accessible to it, and then run the actual container with a smaller number of cores would make container builds so much faster.
EDIT: I’ve looked, and it appears that podman desktop also does 1 big VM, rather than having 1 VM per container.
I’m not sure. To me, the most interesting thing is that each container gets its own VM. I don’t know if podman does that or not. I’d guess not, since CoreOS isn’t the lightest OS around (I’ve used CoreOS and Flatcar extensively at my job and it’s a lil chunky as far as immutable container host OSes go).
Using the open source Containerization package, it runs a lightweight VM for each container that you create.
A big improvement over the stupid shit Docker Desktop did (running a bigass ugly VM for all containers). I’ll still stick with my Linux laptop ;)
There’s also ZZ
👉😎👉 Same caveats apply, smash that fukken esc key (for bonus points rebind caps lock as esc) then ZZ Top your way out of that shit.
I mean, systemd-networkd and systemd-timesyncd are both completely independent and are not required by systemd. I use connman and chronyd on my arch box and systemd gives not one fuck.
There’s still some totally valid concern to be had over how bundled a lot of this stuff is, but it’s not all one big blob.
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.
I need the truck to pass emissions, unfortunately :( Are there programmable ECUs that can pass emissions via OBDII tests? I was under the impression that there aren’t, although I’d love to find out I was misinformed.
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.
I mean, yeah. I wouldn’t have found that project and gone to the effort of using it if a simple dehu was all I needed. I wanted something I could control with my local home assistant install, and you can’t just hard power cycle a dehumidifier, it kills them.