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.
shrugal
joined 1 year ago
I imagine it like friend requests between communities: [email protected], [email protected] and [email protected] 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.
Fedora as well, with drivers from RPM Fusion.
I've been using Nvidia+Wayland+Gnome with two different monitors for a while now, and never had any problems with this setup. The X11 setup before that had some issues years ago, but worked fine for the last few years before switching to Wayland.
I also connect different external monitors to my Intel-based laptop fairly often, and it works 99.9% of the time.
Multi-monitor is really just plug and play nowadays.
Most point and click adventures take about 6-10 hours in my experience. My favorites are the Monkey Island and Deponia games.
Oh, he is even "urging" them, so brave!
What comment?
I've literally never seen anyone say this except FediPacters as a strawman.
I've seen that quite a few times already, mostly in the form of "it's stupid to preemptively defederate, we can always defederate later".
Not likely, you'd typical just use the user agent string for that.
view more: next ›
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.