I’ve been wondering about this for a couple of days. Having users-only instances could help with moderation and content visualization (think in beehaws.org pulling the plug on lemmy.world), while giving the freedom to different communities mods to treat their content as they want.
This would lend to three levels of administration/moderation.
- At community level: Mods can let their communities be run as they want
- At content-server level: By letting content-server admins run their instances with their own ethos. Letting people from certain users-only instances post, while other only read, and others are simply blocked.
- At users level: By letting users-only server’s admin to let their users access certain instances that are aligned with their own interest (no-porn instances, no-nsfw instances, etc.)
This can lead to a kind of meta-db, where instances can declare their ethos, and then be automatically peered, or automatically severed.
I think that the main benefit for this is that it’s easier for newcomers to visualize. While having mixed instances removes redundancies, having this separation allows for more streamlined experience for the users.
I was also pondering about that. Even though I haven’t really looked into how it all works behind the scenes in depth, on high level I do think it makes a lot of sense to separate content hubs (communities) and consumers (users).
The issue is that content from any instance is physically hosted on the instance you access it from, which could lead to major legal consequences based on the data that might be hosted and the local laws.
If you want full control, set up your own instance. It’s what I’m gonna do as well once my financial situation goes beyond eating spaghetti all day
Huh, I guess? I didn’t understand most of what you said. But whatever is good for decentralisation is good for everybody, I think.
