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?

  • arkcom@kbin.social
    link
    fedilink
    arrow-up
    10
    ·
    1 year ago

    I’ve mentioned this elsewhere but it could just be a UI thing handled by/for each user, that way moderation and control will stay where they are

    Basically I could make a group of communities/magazines, for example
    selfhosted@kbin.social
    selfhost@lemmy.ml
    selfhosted@lemmy.world
    selfhosting@chirp.social
    selfhosted@lemmy.ml
    selfhosting@slrpnk.net

    For browsing, up/downvoting, and commenting it could be totally transparent. When you want to make your own thread it could just have you select the specific magazine/community from a drop down.

    This wouldn’t fix the problem of seeing multiple duplicate posts from each.

    • png@kbin.social
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I think this is the ideal solution, but you should be able to share the groups you create with others, exactly like multireddits. That way, collections of these groups could be made available to others, for them to add to their feed.