A multi-community would be all communities with a certain name, across all instances. It would prevent powermods from being a problem on Lemmy. i think it should be notated with m/<insert name here>, just like communities but with m instead of c.
Lemmy is open source. The developers are working on this for free (minus some sponsorships). PR’s are always welcome to help add new features you want :)
I dare say it’s not helpful to ask why something hasn’t been done on a community-based open-source project. Comes off as demanding and antagonistic. If you want it bad enough, you could contribute.
While it has started a discussion, this is more of a support question. Please see the sidebar for a list of communities on where you can find further support. Removing under rule #3.
Let’s make it turtles all the way down; allow for federation at the community level, subject to the federation guidance at the instance level. If memes@lemmy.world and memes@foo.bar are sufficiently similar to share content and as long as lemmy.world and foo.bar are federated, then content from both communities appears in both communities.
If moderation issues arise or if the communities diverge in interest, they can split. Users can pick either or both communities to interact with. The world goes on.
Of course, I have no idea whatsoever how to do this, and there’s probably a better idea already in the pipeline… but if it works at the macro level I think it’s got a shot at the next level down.
Another feature I’d like to see is instance admins proposing multi-communities, as in: multi-communities which pop up in the search results and allow you to subscribe to all the the communities grouped together with one click/touch. This way the problem of community fragmentation across multiple instances (e.g. multiple instances having a a “memes” community) would be solved (or mitigated at least).
