If I understand Lemmy correctly, you can create duplicate communities on different instances. Isn’t this kinda counter productive because this may lead to less user interaction in those communities, because the user base gets split up between competing communities.

Is there a way to fight this division of the (small) userbase or is this effect even desired because it leads to more tight knit communities on the different instances?

  • Aardonyx
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    The most effective solution is to search for existing communities on federated instances before creating a new one on your instance. Then new communities are ideally only made if the existing community doesn’t meet your particular need or specific interest (eg. UnitedKingdom vs UKCasual), or if your instance doesn’t federate with the main community.

    The same dispersion of userbase is present on reddit but the more popular urls/content will eventually become clear and less popular communities will either aggregate into the main one or become more niche (eg r/games vs r/gaming).

    • CaptainBlagbird
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      It would be nice if on creating a new community which already exists on another instance, a recommendation is displayed. Something like

      /c/whatever already exists on the following instances:

      You would probably reach more lemmings there.
      Would you still like to continue creating your_insurance.com/c/whatever?

      Right now where each instance doesn’t yet know many remote instances, it would not work that good yet, but once instances have more users that already added many remote communities it could work great.