Why not use fwupd? (link is the Arch wiki but should be relevant for any distro). I've been using fwupd to keep my Dell XPS15 BIOS updated for the last few years, with no problems at all.
How could we not have done? When electricity was first being proposed of a way of powering homes and industry we couldn't even agree on a standard for distribution (Tesla vs Edison). The world's governments didn't step in because this was a dispute between private companies. Just like governments didn't decide whether we should use VHS vs Betamax, or drink Coke vs Pepsi.
And then once a country decided on a standard distribution method they had to pick a voltage, a frequency, and a plug/socket design. Again, there was no real reason for governments to get heavily involved at this point - after all, nobody knew if this new-fangled electricity thing would ever really catch on.
Can we just start again?
Sure. But it will cost maybe hundreds of billions. Maybe more than that. It doesn't matter which plug/socket design you say is the right one for the whole world, most of the world won't already be using it (just look at the map!). So all those countries are going to have to change not only the plug on every single appliance in existence in their country, but also every single socket on every wall in every building. And what's the benefit to the countries that have spent al those billions doing that? Absolutely nothing - the advantage and profits will be reaped by product manufacturers who don't have to produce a variety of connectors.
No. The whole point of Federated software is that things happen on one server, and by the very design of the system those things get shared out to other servers. "Things" could be anything from posts to comments to up/down votes.
The only way to have anonymous voting would be to make the up/down votes strictly local to a particular server, which kind of defeats the purpose of a federated system.
I'm still struggling to understand what advantage Docker brings to the set-up.
Maybe the application doesn't need to write anything to disk at all (which seems unlikely) but if so, then you're not saving any disk-write cycles by using docker.
Or maybe you want it only to write to filesystems mounted from longer-life storage e.g. magnetic disk and mark the SD card filesystems as --read-only. In which case you could mount those filesystems directly in the host OS (indeed you have to do this to make them visible to docker) and configure the app to use those directly, no need for docker.
Docker has many great features, but at the end of the day it's just software - it can't magic away some of the foundational limitiations of system architecture.
I'm not sure why Docker would be a particularly good (or particularly bad) fit for the scenario you're referring to.
If you're suggesting that Docker could make it easy to transfer a system onto a new SD card if one fails, then yes that's true ... to a degree. You'd still need to have taken a backup of the system BEFORE the card failed, and if you're making regular backups then to be honest it will make little difference if you've containerised the system or not, you'll still need to restore it onto a new SD card / clean OS. That might be a simpler process with a Docker app but it very much depends on which app and how it's been set up.
Yes, I think that 'masquerading' is the key bit to grasp. The MITM Proxy isn't just intercepting the traffic, it alters the traffic as it passes through.
DigitalOcean's guides in general are pretty good for all sorts of things, whether it's a generic discussion of a concept like the ones you've posted, or a step-by-step guide for installing and configuring specific systems or software. Even if you're not using DO as a host, much of what they suggest is still very useful.
Do you want zombie orphans? Cos that's how you get zombie orphans. Listen to the AI, it's trying to save the world from becoming a dystopian TV series!
Neither sausage-on-a-stick fast food nor sausage-in-a-bun fast food bear any resemblance to the traditional German way of serving wurst. Neither is "closer" they are both a million miles away from the original.
How is this supposed to be enforced? In a decade's time are shopkeepers going to have to challenge anyone buying a packet of fags who looks under 28? And then later it'll be "sorry mate, can you prove you're 44?" and so on.
That looks amazing. In the last year or two I've found a pretty good, reliable dough recipe, but I'm never really satisfied with the tomato sauce I use. Do you have a recipe you stick to?
If you are on (or migrate to) a server using the Glitch-Social fork of Mastodon, you'll get markdown support. It's a game-changer, in my opinion. (glitch-soc has lots of other nice features too, btw).
While true, I think most people's concern is that their laptop is stolen and along with it all the access details for their email, online banking and so on.
If you're doing things that mean you're going to be the target of people with the knowledge, time, and technology to freeze the RAM and attempt to recover the data, you're presumably already well aware of those (and other) dangers anyway.
Maybe in the wider world of all the operating systems installed on all the computers, but for Linux-based computing it is, like it or not, near ubiquitous these days. And in particular for server systems (and this is, after all, /m/selfhosted), good luck finding something that isn't systemd-based unless you're deliberately choosing a BSD or aiming for a system which has ever-decreasing amounts of support available.
This post is generating waves of nostalgia for /r/Fryup for me. We need somewhere on the Fediverse to post, lust over and critique other people's fry-ups.
That all seems ... incredibly complicated.
Why not use fwupd? (link is the Arch wiki but should be relevant for any distro). I've been using fwupd to keep my Dell XPS15 BIOS updated for the last few years, with no problems at all.