Most people access the Fediverse through one of the large instances: lemmy.world, kbin, or beehaw. New or small instances of Lemmy have no content by default, and can most easily get content by linking to larger Lemmy instances. This is done manually one “Community” at a time (I spent 15 minutes doing this yesterday). Meanwhile, on larger instances, content naturally aggregates as a result of the sheer number of users. Because people generally want a user experience similar to Reddit, I think it’s inevitable that most user activity will be concentrated in one or two instances. It is probable that these instances follow in the footsteps of Reddit- the cycle repeats.
I actually think the Fediverse is in the beginning the process of fragmenting into siloed smaller, centralized instances. Beehaw, which is on the list of top instances, just blacklisted everyone from lemmy.world. Each of the three largest instances now are working to be a standalone replacement for Reddit and are in direct competition with each other. It is possible that this fragmentation and instability? of Lemmy instances will kill the viability of Federated Reddit altogether, but hopefully not.
These are my main takeaways from my three days on the Fediverse. I will stick around to see if the Fediverse can sustain itself after the end of the Reddit blackouts.
Counterpoint, allowing people to create their own communities is how new ideas for communities come up. If it wasn’t for that freedom, people wouldn’t have come up with ama, meirl and all the other weird concepts that took off
I’m not saying you shouldn’t be allowed to create a new community. I’m saying that due diligence should be taken BEFORE creating a new community, to be sure that community doesn’t already exist.
Mental bandwidth. By adding the requirement of a mod approval before creating a new community will cause most people to not bother at all.
As a counterpoint to that: any new community that gets created on an instance is now a possible liability the site admins have to own.
Makes a lot of sense that you wouldn’t want anyone to make anything on your site, since that’s how you end up with /r/jailbait, and /r/fatpeoplehate and so on.
Seems reasonable you’d want to make sure you understand who is creating what and why on a platform you’re ultimately responsible for.
It’s really not difficult to delete a unwanted community. The cost benefit analysis I think still leans towards open for all, as a breakaway success story makes up for it.
It’s not just the difficulty, it’s that the fediverse runs on reputation.
If you get a reputation for being an instance that has offensive/illegal content, you’ll get defederated and your users will get a materially worse experience than the rest of the instances that are federating with each other - and it really only takes one or two things to get that reputation.
sh.itjust.works is a prime example: it didn’t take an awful lot to get them down the defederation road, and I suspect most admins would want to maintain their reputation and an easy way to do it (until we get like… moderation tools) is to just gatekeep what communities show up on your instance.
Actually that problem is usually registered users going into established communities of other instances and trolling, not new communities pooping up that nobody knows about.
I’d say for the majority of people who are coming here from Reddit, the concept of federated servers and looking for duplicates would be a pain. I think most people who come to a site like kbin search to see if there’s a local community and if not would want to create it.
Admins I’d assume would be able to search connected other sites to see if a community exists elsewhere, but that sounds like it puts more work on them when they’re busy with PRs and infrastructure work.
I’ve got no idea about what the best approach is, but it needs to be somewhat simple it we want people to join and stick around I feel.