• vulpes_mittens@vlemmy.net
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    1 year ago

    The ability to merge/join communities across instances. Right now, there’s lots of duplicated communities - which isn’t a big problem, but I feel that it’ll hinder adoption as it fragments the audience for a given topic.

    Edit: also worth saying that it seems like that the if the instance hosting a community goes away, so does the community.

    • dogmuffins
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I was concerned about this but I’ve made peace with it. It’s just the nature of the fediverse.

      Basically people just need to subscribe to all of them, which is the natural response to seeing multiple communities with the same name.

      I’m concerned that linking communities might be an attempt to make lemmy emulate something that it’s not.

      I haven’t really thought this through but an alternative would be groups of communities. Like one click to subscribe to a curated group of all the /c/selfhosted communities.

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

      The people would have to communicate and agree on terms, which is a positive in its own way I think. But as you know, some people don’t wanna give up power.

      Over time people will find which fragment they like the best and each will developed its own culture. Some will combine I’m sure.

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

      Yes, it is worth saying. In fact I was scrolling for this. There should be a way to adopt refugee communities with all its posts from other instances so as to not lose all the information when the server goes down for good. It needs consensus, but only from admins of original community and the new host, this last to prevent server abuse. Also, if communities can get merged, the list of instances hosting the community would serve both as redundant backup and as distributed (instead of fragmented) service.