Unpopular Opinion
Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
- If your post is a "General" unpopular opinion, start the subject with [GENERAL].
- If it is a Lemmy-specific unpopular opinion, start it with [LEMMY].
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
view the rest of the comments
Ok. So just like Lemmy but communities are spread using some hash table over multiple existing nodes?
Yep, divide everything so no one has real power and it's the users that decide what they want and don't want on their feed, allow the hosts to decide if they want to host NSFW content or not (and the users can make the same choice), make it so the users don't have to decide what instance they register with, their credentials are just stored in the database.
For the front end you then have two ways to deal with it, a single one and the hosts "vote" on how to deal with it (crypto style) or the hosts are the database that anyone can access and it allows anyone to create a front end...
Your second scenario where the hosts decide and the users choose the hosts is what Lemmy is doing now
Not really though, with Lemmy the host and front end are the same. You access Lemmy from hacker talks, I access it from shitjustworks, both our respective instances host our respective data and provide us a UI to access their instance and could decide to only give us access to the content that they host as some instances already do.
What I'm talking about is front end devs not having to host any of the content themselves, just accessing the database hosted by others and showing that info in the UI they developed and pushing changes to the database when the users sign up or post comments.
Front end doesn't have control over where the info is stored and don't store anything locally, back end doesn't have control over who's pulling and pushing data, they can just choose to filter out NSFW content from their own servers but it just means it won't pick them to host that content and will instead pick servers that don't mind hosting it.
In this way the hosting is the same as any hosting services but completely decentralized and the data is open to all and no host can wipe it because of the backups (contrary to Lemmy where if an instance disappears all the content it hosted is gone).
So the data would be stored in something like IPFS? Or ceph?
Ceph has issues because the The metadata nodes needed for disc admission are central points of control
IPFS could work, but the cost of hosting go up exponentially. But yeah you could build Lemmy on top of IPFS