This is a big problem. It creates the illusion that /c/cats on one particular instance is the real /c/cats.

This is the root of re-centralization and it must be pulled out.

  • federico3@lemmy.ml
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    3
    ·
    edit-2
    1 year ago

    This is not a communication problem. Communities are indeed centralized and if an instance is shut down permanently or loses its data all the communities are gone. This is a big design problem of Lemmy.

    Edit: it’s sometimes possible to rebuild new communities on another instance and recover past messages that have been replicated on other instances (if there were full replicas) but this requires all users and moderators to agree on where to migrate and avoid splits and so on.

        • HTTP_404_NotFound@lemmyonline.com
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          2
          ·
          1 year ago

          Its actually possible to take the local copy, and set it as a local community…

          With a few database commands.

          So, migrating communities from offline servers is possible as long as it was federated and synced beforehand

          • federico3@lemmy.ml
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            That’s besides the point. Of course it’s always possible to create new communities on new instances, and import posts from various sources, but the original community would be still gone.

            If an instance is shut down or becomes unusable for a long time there is no way to automatically migrate users to a new instance. Additionally, there is also no guarantee that all users will move to the same alternative instance. This can also cause unnecessary conflict around which alternative instance becomes the “legitimate” successor.