Asklemmy

Lemmy is decentralised, so there's no way to establish the concept of a 'super community' without decided a specific instance plays that role - an instance that, ultimately, is hobby run and just as vulnerable to outages as the others. What happens when the instance running the Super goes down?

There's also no way to make a Super any more official than any other. It can handshake a bunch of instances, but unless a user registers to the Super, they still need to search for them like they do now to introduce them to their own instance. A 'Super' may as well just be an instance deciding to put a Megathread of federated servers in its own Support community.

If the Super federates with a bunch of different instances, it also limits those instances abilities to defederate from each other. We'd end up with one of the following:

1. several 'supers', each with their own federations (meaningless bloat compared to the current system - you also can't prevent somebody from making their own super, so this is practically inevitable anyway)
2. many instances that are effectively 'shadowbanned' because they aren't in 'The Official Super'
3. users using the Super to be active across defederated communities and limit moderation's ability to keep out bad actors
4. large instances becoming defederated from the Super to limit 3.

I'd suggest users subscribe to duplicates, for a few reasons (ultimately about federation and safety in redundancy).

1. Connectivity.

Until an instance first reaches out to introduce itself to another instance, communities are not visible. Somebody on lemmy.ml can look for 'gaming', but until somebody searches for [email protected] to introduce lemmy.ml and beehaw.org to each other, then beehaw's communities like beehaw.org/c/gaming will not be in the results.

Having duplication helps communities find people across many instances. While it's true that one will likely get bigger than the other, people cross-posting in them or being active in both will allow them to act as bridges to each other, improving how instances network.

2. Longevity.

Lemmy is federated. That means we have dozens of different servers running in different homes, basements, hobbyist offices. It's not centralised, and they're passion projects. So not only is decided which instance should be the 'official' one meaningless, having at least two active somewhat-duplicates provides a level of redundancy if one of them shuts down. (Say, the owner dies, or goes bankrupt, or their office is hit my a natural disaster.)

3. Community.

So you raised the idea of each smaller community having duplicates. This is a problem for a platform that wants an aggregate that reaches as many as possible, such as a tech support community. But for social communities, the smaller ones have their own niche. You might not get as much volume in cat pictures (you can always sub to more cat subs if you wish) but the c/cats on your own instance is going to develop it own instance-specific community, where you know each others' cats by name. Hey @[email protected], how is Madame Biscuits doing today? She seems to like her new bed!