Asklemmy

43945 readers

638 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

Is there a way to create Super Communities? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by PotjiePig@lemmy.world to c/asklemmy@lemmy.ml

31 comments fedilink hide all child comments

I've noticed in the explosion that we are getting duplicate communities in multiple instances. This is ultimately gonna hinder community growth as eventually communities like 'cats' will exist in hundreds of places all with their own micro groups, and some users will end up subscribing to duplicates in their list.

A: could we figure out a system to let our communities know about the duplicates as a sticky so that users can better find each other?

B: I think this is the best solution, could a 'super community' method be developed under which communities can join or be parented to under that umbrella and allow us to subscribe to the super community under which the smaller ones nest as subs? This would allow the communities to stay somewhat fractured across multiple instances which can in turn protect a community from going dark if a server dies, while still keeping the broader audience together withing a syndicated feed?

you are viewing a single comment's thread
view the rest of the comments

[–] WhoRoger@lemmy.world 3 points 1 year ago (1 children)

That's programmer logic. What we need is that mods of example.com/c/community and instance.xyz/c/realcommunity can agree on connecting, and from then on, everything from either would show up on the other as well.

No need to make things too complex.

[–] Galactic_hitchhiker@mander.xyz 5 points 1 year ago (1 children)

Even after they connect, a user needs to subscribe to topics of their interest. It would be burdensome for a user to subscribe to the same topic multiple times on multiple servers, because everything is fragmented.

[–] lucien@beehaw.org 3 points 1 year ago* (last edited 1 year ago)

Maybe something closer to migration management in mastodon? Two groups of moderators on separate servers agree to a common set of moderation guidelines, publish an event or setting which says "these communities are merging", and from that point on they act like aliases for a merged community which share responsibility across servers.

These "merged" communities could be visually flagged as distinct from the normal rules / moderation of their respective servers to prevent conflicts arising from differences in server management.

Feature support would be limited by the server events are sourced from. E.g. if beehaw.org and lemmy.ml merged their technology communities, people on beehaw still wouldn't be able to downvote posts or see downvotes, but lemmy.ml would unless they explicitly disable to feature as a part of the merge contract.

When subscribing, you might see a list of merged communities which share responsibility for moderating the final one, and you have the ability to choose which "entrypoint" you use.