There’s been an ongoing debate about whether communities should combine or stay separate. Both have significant disadvantages and advantages:

Combine:

  • Network effects. Smaller communities become viable if they pool together their userbase. Communities with more people (up to a point!) are generally more useful and fun.
  • Discoverability. Right now, I might stumble on a 50 subscriber community and not realize everyone has abandoned it for the lively 500 subscriber community somewhere else, maybe with a totally different name.

Separate:

  • Redundancy. If a community goes down, or an instance is taken down, people can easily move over.
  • Diffusion of political power. Users can choose a different community or instance if the current one doesn’t suit them. Mods are less likely to get drunk on power if they have real competition.

This isn’t an exhaustive list, but I just want to show that each side has significant advantages over the other.

Sibling communities:

To have some of the advantages of both approaches, how about we have official “sibling communities”? For example, sign up for fediverse@lemmy.world and, along the top, it lists fediverse@lemmy.ml as a sibling community.

  • When you post, you have an easily accessible option to cross-post automatically to all sibling communities. You can also set it so that only the main post allows comments, to aggregate all comments to just one post, if that’s desirable.
  • The UI could detect sibling cross-posts and suppress multiple mentions of the same post if you’re subscribed to multiple sibling communities, maybe with a “cross-sibling post” designation. That way it only shows up once in your feed.
  • Both mod teams must agree to become siblings, so it can’t be forced on any community.
  • Mods of either community can also decide to suppress the cross post if they feel it’s too spammy or not suitable for cross discussion.
  • This allows you to easily learn about all related communities without abandoning your current one. This increases the network effects without needing to combine or destroy communities.

Of course, this could be more informal with just a norm to sticky a post at the top of every community to link to related communities. At least that way I know of the existence of other communities. I personally prefer the official designation so that various technologies can be implemented in the ways I mentioned.

  • queermunist she/her@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    10 months ago

    Redundancy has been so important recently with the DDoS attacks, and even as that subsides it’s still definitely an important infrastructural perk that federation offers. It’d be a shame to lose that to centralization.

    • dbilitated@aussie.zone
      link
      fedilink
      arrow-up
      2
      ·
      10 months ago

      it would be good to have some kind of linking.

      my feed is usually ten copies of the same thing posted to similar communities on different servers

    • fresh@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      1
      ·
      10 months ago

      I agree. Do you feel this proposal doesn’t address that? My hope is that sibling communities would allow us to keep redundancy and diversity while still enjoying some of the benefits of sometimes coming together.

  • Mane25@feddit.uk
    link
    fedilink
    English
    arrow-up
    0
    ·
    10 months ago

    You’ve just reminded me of something that used to happen around 20 years ago on smaller forums which is “forum affiliates”, where two or more forums with overlapping discussion interests would simply agree to link to each other to drive traffic.

    I’m not sure how common that ever was or if it just happened with the types of forums I would visit, but it worked and there’s nothing really similar in the Fediverse. Normally as a rule I tend towards the “stay separate” camp for communities - but something to boost visibility of related communities might at least help with the perceived drawbacks.