Oh no!

Anyway…

Imagine working under Daniel Micay… Fucking yikes.

This is the kind of attitude that drives people away from open source.

Yes, people should read the manual, but at some point they will have questions, and there are a lot of projects that aren’t clear on certain things. Such as YAML changes.

I’m convinced that battery life is intentionally nerfed to one day on every single smartphone. Because every single year manufacturers come out with this same bullshit “don’t worry, this year’s model will get you that multi-day battery life you want without compromise!”

It’s just a carrot on a stick to get people to buy the newest device.

Oh fuck off, dipshits. You chose this route despite the community that built you.

Could it be a competitor for that particular product? Hired some foreign entity to hit anything related to their own product?

This lets you root while keeping the bootloader locked.

Wait, what? That’s a pretty big deal!

Oh boy, Daniel is off his meds again.

Valid, I can respect that choice. I prefer having full access available, but that’s just how I do.

I don’t need root, but there is something about a company trying to tell me “no you can’t” that makes me really want to prove them wrong.

I’ve rooted every single one of my Android devices over the last 15 years. I have no plans to stop. I paid for the device, therefore it is mine, and I will do what I damn well please with it.

Syncthing itself is fine. Syncthing-Fork, a completely separate project that wraps Syncthing into a neat app for Android, is what’s going through the repo drama.

Besides - it looks like the new repo owner is pretty transparent about the whole thing and appears to be making good-faith efforts to keep the original Syncthing-Fork devs involved.

I mean, 35W maximum is still incredibly low. At that point, you’re looking at a cost difference in the single-digits over the course of an entire year.

My little lab has 5 machines, 3 of which are tiny/mini/micro PCs. Total draw from my entire setup, including the t/m/m machines, is right around 100W. And since I started measuring it back in February, it’s used a total of 635 kWh. And most of that is from the spinning rust hard drives. For reference, my whole household’s monthly usage averages around 1200 kWh.

I haven’t figured out the whole high availability thing yet; I just move VMs/containers to different nodes if I need to bring a node down, or shift resources around, or whatever.

A 7th-gen i7-powered tiny/mini/micro is perfect for HA. Plenty of grunt for lots of HA addons and integrations, lots of USB ports for dongles (zigbee, z-wave, etc), often with 2x M.2 slots (usually one B/M key and one A/E key) and SATA interface, very low power draw, and cheap due to businesses offloading them all the time.

I have a Proxmox cluster and still went with a separate machine for HA. I figure the thing controlling my house should be on it’s own, since the cluster is more a playground for me than anything else.

I stopped using CF tunnels specifically because of shit like today’s outage.

It was posted Sunday afternoon.

Today is Tuesday.

Ahh. To my knowledge, iRobot units aren’t rootable, and are therefore unsupported by Valetudo.

https://valetudo.cloud/pages/general/supported-robots.html

My Wyze is based on an ODM unit, the 3irobotix CRL-200S. Companies like Wyze, Xiaomi, Viomi, iLife, Conga, and other brands customize and sell it as their own models since that’s cheaper than manufacturing their own units. Parts are swappable between them as they are all the same robot underneath… Kinda like how car companies rebrand models based on region. As far as I’m aware though, iRobot builds their own robots.

What?

I had to replace the motherboard with one from a different variant (same base robot) that could be rooted. Outside of that - super easy.