Sibling communities: A middle way - eviltoast

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.

  • spaduf@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    One big issue with the existing cross-posting feature is that it does not work AT ALL with text based posts, just links.

    • Die4Ever@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      one thing that’s annoying about this is that sometimes new content will be added to an old URL

      like Steam Hardware Surveys, there’s no way to perma-link to a specific month, their page only shows the most recent results

      https://store.steampowered.com/hwsurvey/

      which can cause weird issues with Lemmy thinking it’s the same post and only showing 1 of them

      I had this issue with one of my own communities, I was posting links to the Github Releases page for every new release (which is usually good because people finding old links on Google should see the latest release and the full list of releases, not the one specific release)

      but I realized only 1 post would be visible at a time, and if you did Top All sort then it would be a post about an old release, now I gotta post directly to the specific release

      when Lemmy has some form of sibling communities or grouped communities, I think it can be less aggressive in detecting “cross-posts” and only explicit cross-posts would be handled as such