• kevincox@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    The problem of which instance to host a community on is a big problem for Lemmy. Grouping is an interesting idea but it causes problems as now there are different mods and admins that control subsets of the community.

    Picking a single “winner” and letting the others wither seems like the right approach and will probably happen naturally but if the original instance ever shuts down or struggles under the load you will have a mess to migrate to a new instance.

    If Lemmy communities were decentralized it would make a huge difference. You could just have a single community but it could survive instances coming and going (as well as many other performance and resiliency benefits). But that would be a huge change to the underlying implementation of communities.

    • sbv@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      The problem of which instance to host a community on is a big problem for Lemmy.

      Seeing the same content posted six times in six communities is a problem. It pollutes the feeds, it fragments the conversation, and prevents the natural death of low-traffic communities.

      • kevincox@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Avoiding showing identical posts to a user separately seems like a very easy problem to solve.

    • maboesanman@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I think it probably makes sense to host similarly moderated content together.

      programming content being grouped together makes sense because it’s moderated to a similar extent between languages and communities.

      For example discussions/posts on rust programming and porn are moderated very differently, so they should be on different instances.