An app to manage important config and unit files (fstab, hosts, sysctl, systemd units, …), and present them as settings menu or editor with auto completion and tooltips. Kinda like how VSCode handles settings, where you can use the GUI or a context-aware text editor.

Starting your own instance doesn’t solve the problem of big communities being reliant on the one specific instance they are hosted on to not go down or rogue.

I imagine it like friend requests between communities: x@instance.a, all-about-x@instance.b and x-is-great@instance.c could send each other friend requests and merge into one federated meta-community about x. Then if one instance goes down the other two are still there to keep the meta-community alive, and if one goes rogue the others can just unfriend and keep going without it.

The nice thing about manual federation is that the communities don’t have to have exactly the same name, and the mods can keep malicious or troll communities out. And ofc you could still have client-side control if you want to, e.g. add or remove a community just for you locally, or create your own local meta-community.

The database, storage and network are usually the bottlenecks in these kinds of websites, not the programming language. It might add a few ms of latency, but the big lags come from congestion or bad db queries.

Oh, he is even “urging” them, so brave!

What comment?

RHEL is not Fedora. It’s still lead by a community council, even if you don’t agree with some of their decisions.

In case of your first link it wasn’t even about making a decision. The project has always had the clear stance to not include patented works, so there were no two ways about it.

What’s wrong with Fedora?

Fedora! To me it sits right at the sweet spot of stability and bleeding edge (they call it “leading edge”), and I’m very happy with how they run things (including the most recent controversy!).

Apparently ChatGPT is really good as a personal tutor. You can ask it specific questions and it will answer with detailed tutorials and step-by-step guides.

While this is probably still true, I doubt it’s a big factor when talking about mass adoption.

You can update a standard release distribution just fine, no need to reinstall anything. It does basically the same thing as a rolling release, just not as often and more packages at once.

What does the release cadence have to do with that?