correct. so let’s have a way to “connect” communities, a way for any 2 communities on 2 different instances (or the same instance) to “merge” their content, even if they have different names (e.g. “games” “gaming”). now maybe this could be user-defined, a per client thing, like multireddits, but with a recommendation on each community page that shows the most frequent “client community-merge-configurations”
communities across instances could essentially link their feeds
yes, that’s pretty much what i’m saying. in the background, that is what would be happening, but on the frontend, the user just sees “communityname” and a bunch of posts that are pulled from all instances that have a community matching that name.
to clarify, “admin of an instance” is different from “moderator of a community”.
good point with being able to switch to another if a mod goes haywire. but i think that there just shouldn’t be any mods – or rather, the community members should moderate themselves via some algorithm that uses votes, discussion, etc. to hide/remove posts. you could choose to view a hidden post that has been downvoted a lot if you want.
27yo tech enthusiast and worker and linux user here
i think enough people want the feature that the benefit would be worth it
you actually wouldn’t have to limit it to exact same name if you’re making a front-end thing, if you allow for the user to configure their “merged communities”