Not really. You can get manual pumps for PEX A which are about the same price as a tile cutter… They are fine. You only need those 500$ power tool expanders if you were doing plumbing all day every day.

I guess it depends what you run, and how the projects/containers are configured to handle updates and “breaking changes” in particular.

But also, I’m being a bit broad with the term “breaking changes”. Other kinds of “breaking changes” that aren’t strictly crashing the software, but that still cause work include projects that demand a manual database migration before being operational, a config change, or just a UI change that will confuse a user.

The point is, a lot of projects demand user attention which completely eclipses the effort required to execute a docker update.

Are you updating 1000’s of stacks every week? I update a couple critical things maybe once a month, and the other stuff maybe twice a year.

I don’t recommend auto updates, because updates break things and dealing with that is a lot of work.

Documentation is for onboarding other people. Why on earth would I need to onboard other people to something self-hosted?

How is the average person going to know that? If Joe blow can’t easily get to the distro they “should be using”, Linux ain’t happening for most people.

I enjoyed the depth of this answer. That being said…

4 copies seems like a level of paranoia that is not practical for the average consumer.

3 is what I use, and I consider that an already more advanced use case.

2 is probably most practical for the average person.

Why do I say this? The cost of the backup solution needs to be less than the value of the data itself x the effort to recover the incrementally missing data x the value of your time x the chance of failure.

In my experience, very few people have data that is so valuable that they need such a very thorough backup solution. Honestly, a 2$ thumb drive can contain most of the data the average user would actually miss and can’t easily find again scouring online.

Society has been steadily forgetting the importance of reliability, all in the name of convenience. And in the end, you get neither.

“They don’t make it like they used to”. Sure. Sure. Old man yelling at clouds. Blah blah. But when your light switches stop working because of some overly complex system that requires the switching data to travel twice around the world just to fucking turn a light on (or an AI to invent 15 Python scripts and a mathematical proof just to add two integers together), you’ve got a really fucking fragile system.

And you know what isn’t convenient? Fucking fragile products that break as soon as you touch them. Who the fuck wants a hammer made out of salami? Sure, it might look like a hammer, it might taste great, but it can’t drive a nail for shit. That’s a garbage product that belongs in the garbage.

An LLM can tell me a (lame) joke. So can Bob. Bob can also turn on the lights, and is pretty good at that. But those things together don’t automatically mean an LLM is good at turning on lights. They are fragile, by design, like the salami is!

Stay in your fucking lane tech companies.

Enshitification is the specific process of capturing a supplier/consumer market through short term subsidies, squeezing out the competition, and then squeezing the suppliers and consumers directly.

Increasing prices alone isn’t enshitification. But increasing prices after sustaining artificially low prices for the purpose of creating a monopoly or quasi monopoly is enshitification.

Plex most definitely was providing a good quality product but was not generating revenue, and has little to no competition (Jellyfin is a bit debatable) as a result. Was it intentional or just incompetence? Hard to prove either way. I’d say the biggest argument against enshitification is that Plex is mostly a product instead of market space hosting suppliers and consumers, like Google, YouTube, AirBNB, Uber, etc.

I love Linux. I use it wherever I can. I don’t use Linux on my primary gaming workstation, for the simple reason that the display drivers, specifically mixed extended desktop and screen mirroring is just straight up ass.

I would not try to create a separate path to ground. The ground should be bonded to neutral at one and only one place: at or just behind the main panel.

GFCI is rated to protect two wire receptacles downstream of the GFCI, but check with the local authorities on the subject.

Talk about a radicalizing event. Its like an instant 3000 more alt right militants.

Yeah, … but also no. If your conclusion is “the left is out to get us” in the middle of confusion and chaos, before any evidence comes forward, then I am afraid you were already radicalized.

I think the design philosophy is that each tile represents no more than a single entity at a time, and compact enough that you can arrange the entities in a section to represent a device, room or group.

In your example, perhaps the room also has a humidifier and/or heater. So in reality, the room temperature entity isn’t truly tightly coupled with the fan. The heater and or humidifier are also a part of the whole.

With tiles, you are in complete control to arrange groups of entities that represent a larger whole, in whatever scope you like.

IMO, setting it up at home is not the bar for decentralization. I don’t think it’s even practical to run your own self-hosted fediverse server.

I think we can get just about all the same benefits of decentralization at the scale of the city.

Assuming a constant rate of change of anything involving people over a period of ten years is straight up nonsense.

I’m using off-the shelf CT-clamps with an ESP. Obviously it’s a fair amount more work, but it’s cheaper than a commercial solution, fully offline and no subscriptions, you know exactly what you are getting, and you can build a solution that is just the right size for your application, and infinitely modifiable if your needs change.

Surely the SVGO package can be compiled into a browser bundle.

I might look into this myself…

Does this support SVG, i.e. SVGOMG/SVGO? If not, that’s a glaring omission.

Tried a couple matter devices. Ended up having to create an account with the manufacturer. Was there truly a local option? Who knows. So far I haven’t been impressed.

Disagree. A detached house with yard unlocks room for so many hobbies. Like planting a vegetable garden. Playing instruments or music without pissing off the neighbours. Beekeeping. Woodworking. Backyard astronomy. Backyard BBQ. Bonfires. Etc.

Suburbs themselves are not a dirty word. It’s how some people choose to execute it that is the problem.

Before I understood Docker, I used to have HA installed directly on bare metal side by side with other “desktop” apps.

To be able to access devices, HA needs many different OS-level configurations (users, startup, binding serial ports, and much more I don’t have a clue about). It was a giant mess. The bare OS configuration was polluted with HA configurations. Worse, on updating HA, not only did these configurations change, the installation of HA changed enough that every update would break HA and even the bare OS would break in some ways because of configuration conflicts.

Could this be managed properly through long term migration? Yeah, probably, but this is probably a ton of work, for which a purpose-built solution already exists: Docker. Between that and the extra layer of security afforded by dedicating an OS to HA (bare metal or virtualized), discouraging the installation of HA in a non-dedicated environment was a no brainer.