FOSSDLE PieFedThe Beatings Will Continue Until Morale Improves: Cohost and the Fate of Centralized Platforms
submitted by
Riley
submitted by
Riley
If there are no admins, who can ever decide who is a moderator? How do you decide that? The way it is currently decided is via admins granting mods powers on communities on that admin's instance. If you don't have admins, I don't see how you could possibly have mods.
Create the community > you're the mod, if people aren't happy with your moderation they create their own community
I suppose communities would not have unique names then - otherwise I'll just go ahead and create communities from all the words in the dictionary and then I control all communities.
So if they don't have unique names, how in the world do we refer to them? By some opaque UUID or something? I mean I guess it's possible, maybe.
Who's hosting this new community you just made? Where does it live? The description of the community, you know the side bar in a Lemmy community, where is that physically speaking?
You realize the way things work currently doesn't prevent that, right?
As I said from the beginning, front end and back end are separate.
Ok, let me put it another way. Reddit's content is decentralized already (everything isn't hosted on a single server, everything is backed up on multiple servers in multiple locations) but all its content is available from a single web page.
What I'm suggesting is that the hosting is "done the same way" just handled by anyone who wants to provide servers instead of dealing with a service like AWS. Now contrary to Reddit, that content is then made publically available so anyone can develop a front end for it. There could be a default option (Lemmy.com or whatever) but it would give users access to the exact same thing as any other website that offers access to the database via a UI. No defederation bullshit, no admins that can decide to wipe out part of the site (everything is backed up, you wipe your server, no one cares, all that content is pulled from another server instead), just a huge decentralized database anyone can access.
It totally does prevent it because every community has a unique name, when you include the instance domain. Which is the whole point. The instance is where the community lives.
Ok, but you can still go ahead and create the same community on every instance so you control all the communities with that name.
No! That's exactly what you can't do, because if you tried you'd get banned by the admin! In your scenario, there are no admins to stop such a bad actor. But ultimately admins control what communities are on their instance, so you can't just hijack all communities like that.