Comment on [sh.it.post] We're #5! We're #5!
Trainguyrom@reddthat.com 2 weeks agoI’m thinking more unifying communities that either have the same mods or for annexing communities with inactive mods, and I keep referring to redundancy because that’s the specific purpose in my mind, with the side effect of cleaning up the multiple dead communities with the same name on various instances.
There’s a real risk in the Fediverse of the one server hosting a community going offline, and we’ve already seen at least one notable Lemmy host shamble on as a zombie server with absent instance administrators. Instead of forcing communities to tell eachother to migrate or to recreate themselves on a new instance should one disappear suddenly, by having the community effectively load balanced and replicated across 2 or more instances is a lot more resilient
I fully respect when moderator teams have different opinions running similar communities with different rules and expectations and in not saying that should be taken away. I’m just thinking about technical solutions to improve overall Fediverse health
OpenStars@discuss.online 2 weeks ago
There’s a reason the current Lemmy sourcecode is named 0.19.8 - this is beta version software, awaiting very many changes to reach completion. Heck, reports don’t even reach moderators on remote instances yet, as the whole drama with 196 is showing (they left the mod reports there for days, then got mad when the instance admin did what she said she would and cleaned up in the absence of the mods being willing to do anything about the situation).
But people either don’t know Rust (it’s reputedly difficult), don’t want to deal with those developers, or simply don’t want to help with the writing of code. Hence the creation of K/Mbin, PieFed, and Sublinks to deal with the former pair of issues, though not catching up to feature parity with Lemmy yet (except PieFed is already quite ahead, in some ways even though not ready for the masses in some fewer but more foundational and crucial ways).