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?

  • zinklog@lemmy.fmhy.ml
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    For this to happen every single instance will have to fetch every community from every instance to aggregate posts and make sure new similar community is added which isn’t feasible (I think).

    Give it some time, and I think organically 1-2 most popular communities will emerge for each specific topic and people will then just subscribe to those ones.

    • effingjoe@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Give it some time, and I think organically 1-2 most popular communities will emerge for each specific topic and people will then just subscribe to those ones.

      This is kind of what I was thinking, too. There’s no limit to how many duplicate subs there can be on Reddit but that didn’t stop people from eventually finding the “main” subs. Lemmy just needs a critical mass of users first, so that the clear winners are easily seen. With numbers being so low right now, there’s no clear winner among duplicates.