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.

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.

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.

Yes, but also no. Older hardware is less power efficient, which is a cost in its own right, but also decreases backup runtime during power failure, and generates more noise and heat. It also lacks modern accelerated computing, like ai cores or hardware video encoders or decoders, if you are running those appd. Not to mention lack of nvme support, or a good NIC.

For me a good compromise is to recycle hardware upgrades every 4-5 years. A 19 year old computer? I would not bother.

I think it’s a good idea, everyone should be automating this anyway.

This is still not possible in all scenarios. For example, wildcard certificates for DNS providers with no API support.

Arrogance: a tale in two acts.

After months of trying, I still can’t get Linux to recognize the 2.5Gbit network cards, or to function with multiple monitors. If the hardware support was better, I would ditch Windows for good instantly.

I spent an unhealthy amount of time on Reddit. Getting bored of Lemmy is a feature, not a bug. Embrace it.

Terminals are powerful and flexible, but still slower than a dedicated UI to see states at a glance, issue routine commands, or do text editing.

Terminal absolutists are as insufferable as GUI purists. There is a place and time for both.

The only thing holding me back now is inertia with compatibility to extensive software/game collection. But yeah, about to jump ship.

You deftly evaded the leading attack vector: social engineering. Root access means any app installed could potentially access sensitive banking. People really are sheep and need to be protected from themselves, in information security just like in anywhere else.

You don’t get a “accept the risk” button because people don’t actually take responsibility, or will click on those things without understanding the risk. Dunning Kruger at play.

Why is this prevalent on Android but not desktop Linux? Most likely a combination of 1) Google made it trivially easy to turn on, and 2) the market share of Android is significantly large enough to make it a problem warranting a solution.

The fact that you know how to circumvent it is inconsequential to the math above. Spoiler: you never were nor ever will be the demographic for these products, in their design, testing, and feature prioritisation.

Anyone can build a bridge. Only an engineer can build a bridge that barely stands.

In the same way, the fact that one built a large online platform, that doesn’t necessarily mean it was built with minimal ressources and without taking past or future risk.

Engineering is, as a profession, specifically the application of scientific principles to solve problems the right way, the first time, that is to say efficiently, and with minimal risk.

The fact that one codes, or wields a wrench, or operates a C&C machine does not mean one is applying science to solve problems efficiently and managing risk. These are entirely different skills and professions.

Fork the last commit with a LGPL commit?

GPL mentions explicitly that it is irrevocable, where as LGPL doesn’t mention anything about it. IANAL, but it looks like there is a case for irrevocable without violation of clauses by default https://opensource.stackexchange.com/questions/4012/are-licenses-irrevocable-by-default#4013

For people considering contributing to FOSS in the future, maybe check for irrevocable clauses? I wish licenses selectors https://choosealicense.com highlighted this part more clearly.

You should perhaps skim through https://docs.docker.com/storage/ quickly. That document explains that docker containers only have very limited persistence (this is kind of the whole point of containers). The only persistence of note is volumes. This is normally how settings are saved between recreating containers.

As for dependencies, well it’s possible that one container depends on the service of another. Perhaps this is what you are describing?

Either way, for more detailed help, you will have to explain your setup with more specific technical details.

This wouldn’t pass PR review and automated tests, unless they were a senior dev and used elevated privileges to mess with things behind the scenes.

Software dev is full of obscure keywords that describe otherwise pretty simple or basic concepts you stumble upon in practice naturally and that you probably already understand.

• singleton: a class/object that is designed to be single use, i.e. only ever instantiated with a single instance. Typically used when you use class/objects more for flow control or to represent the state of the program itself, rather than using it to represent data
• immutable: read-only, i.e. unchangeable
• dependency injection: basically when you pass a function or object into another function object, thereby extending their effective functionality, typically for modular code and to separate concerns.

Here’s one more of my favourite examples of such a keyword: memoization

No one else uses the term “cloud” like that.

That part of this comic really stuck out like a sore thumb. I can’t tell if it’s an oversight, a comment about the challenges of self-hosting, or subtle mockery of self-hosting hypocrisy.

This a 1/1000 likely outcome. Bankrupted companies will typically sell assets including IP and software to other companies to pay creditors (which excludes open sourcing them). And well before bankruptcy, any financial issues will cause Plex to be modified to support shitty monetization to the point that you won’t want the source code amyway.

Sorry for the bad outlook, better that you be ready than to hope for a unicorn.