Asklemmy

There are benefits to each community being local and server specific (moderation, culture, community), but there are also benefits to the idea of a single community being spread over multiple instances (decentralisation, resilience, activity/reach). There are reasons why few people want to start a or post content to a community on a random server, and most people opt for the biggest one. There's relatively few people as it is already and creating duplicates, fragmentation and inevitable manual content replication doesn't seem like the way to go about things.

This is why I like the idea of a potential future feature where on top of /c/acommunity we would also get a /t/atopic that aggregates all the communities with the same name from all the instances into one place/feed. This would NEED to be optional and the community mods would have to have an optin/optout feature for their community being included in the /t/topic feed. I think that would make both sides happy.

As it is, I don't see having active communities on other instances likely, unfortunately. Individual accounts can work just fine from other instances, and the content gets auto replicated, but the parent hub is still in one place.