Re reverse proxies, not exactly. Tried reading vanilla nginx configs and trying to understand nginx proxy manager, couldn't grasp either. Also gave haproxy a shot.
rpm-ostree
I guess I don't exactly understand the value of rebasing the core system. Small atomic core with snapshot-based rollbacks, with containerized beyond core stuff seems to get you 99% of the way there, no?
If you can host thelounge on your LAN and access it over VPN on the go, it makes for a very nice IRC experience.
Otherwise, ssh (termux or whatever) to your irc host running irssi or weechat
Atomic automatic updates with snapshot creation? Maybe consider opensuse microOS if you are going headless...didn't quite understand from your description. I have a VPS running microOS that has been doing its automatic updates/reboot thing for a year+ now without a single issue. Opensuse's rolling stuff works very well, and you get native btrfs and snapper integration out of the box.
Easy to use reverse proxy - I really like Caddy. Reading/writing the config for that clicks better for me than others.
I like the novelty of using filesystem tools for backups, but can't shake the feeling that tools like restic and borg are more widely deployed and battle tested.
Sad news. Here is a link to an impact study (PDF), which describes many (all?) of the projects that benefited from funding. But a few you may recognize include Lemmy, Kbin, and Mastodon:
I always find responses like this funny. You know how old you are, but (mostly) nobody reading the comment does. You could be anywhere from 11 to 50!
I mostly blame Apple for walling off the default text messaging app on the iOS platform. It is ridiculous to me that we are over 10 years into the smartphone era and are stuck in a duopoly with two players that would rather degrade communications between platforms than prioritize interoperability for some base level functionality. I hope that Beeper's campaign forces regulation that puts an end to the insanity.
You can point out back and forth violence going into the 1800s. Nobody has clean hands in this conflict.
I think the headlines play on mushrooms for outrage and clickbait. It makes readers feel better that there is something tangible that can be "controlled" rather than a hard to define cause of someone's seemingly functional brain misfiring badly.
Another article said he did shrooms 48 hours before the flight.
Selfishly, I would like to see beehaw remain on the fediverse. I enjoy the community, the curation, and desire for strong moderation. It is a great window to the broader fediverse link aggregator community. Beehaw's ideals and structure clearly appealed to many Redditors and the like. The concept of federated communities seemed appealing, and beehaw is an important voice in the evolution of the moderation of a federated network.
However, the sacrifice that the admins have had to put into making the platform survive while the software finds its uncertain way through a mountain of growing pains seems unsustainable (just my pov through the last 3 months) - not just on the technical side. There's that saying - when you find yourself in a hole, quit digging. It's hard to see how moving from Lemmy to something more sustainable, if it exists, would be the wrong move.
Painful decisions rarely come with a flashing light that scream "now's the time" - but the loss of your major technical contributors sounds stunningly close.
Edit> fixed a typo or two
The rise of distributed computing was at a time that CPUs didn't really throttle down. CPUs in general were just a lot more power hungry. But if you had to leave the computer on for some reason and had spare CPU cycles, it made sense to contribute them to a distributed computing project - the power was being spent anyway and it seemed like a good cause. Today, modern CPU sip power and throttle down and you are actively driving power consumption by taxing the CPU. There is a much less favorable cost/benefit equation today, but in terms of the cost of the power consumed AND the climate cost of the power consumed.
Technically true, but FOSS isn't "free" in the sense that someone is contributing labor to build and maintain the software. Free to use, but not free to make. I personally wouldn't expect or shame a person for using FOSS without contributing. But if you make a profitable business off a FOSS project, it seems reasonable to expect some form of contribution back to the project - not because it is technically required, but because who better to sponsor a project than someone profiting from it?