102
The Beatings Will Continue Until Morale Improves: Cohost and the Fate of Centralized Platforms
(audiovalentine.com)
this post was submitted on 12 Sep 2024
102 points (96.4% liked)
Fediverse
28351 readers
688 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.