• terribleplan@lemmy.nrd.li
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    Communities are inherently tied to the instance on which they are created and cannot be moved. If the instance is overloaded then that community will not federate properly. If the instance goes down nobody can post to the community. If the instance goes away that community goes away (except for the “cache” that other instances have).

    • LachlanUnchained@lemmyunchained.net
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Hmm. I’m not sure if that’s the case. I’m interested to see what the plan is for account migration. Weather posts will follow the user. Or stay with the instance.

      • terribleplan@lemmy.nrd.li
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        Migration of ActivityPub stuff is pretty rough… Everything has an ID, and that ID is the URL, so the ID of the post you replied to is literally https://lemmy.nrd.li/comment/227095… AFAIK there are some (non-standard, at least not in core AP) ways you can mark things to be like “yeah, this moved to over here”, but that isn’t built in to the spec so whether those mechanisms actually work is a crapshoot.

        • LachlanUnchained@lemmyunchained.net
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          1 year ago

          Looking at my sql databases, I noticed there’s other identifiers on users and content. Not the url.

          It may be that the url is linked to the ID. And that ID can just change.

          I’m pretty much a noob. Just a lurker on the matrix chats.

          • terribleplan@lemmy.nrd.li
            link
            fedilink
            English
            arrow-up
            4
            ·
            1 year ago

            I’m talking purely from an ActivityPub/Activity Streams/Activity Vocabulary/JSON-LD perspective. There are some other local identifiers for things in Lemmy, but those do not matter for the purposes of federation. Any Object that is federated is expected to have an ID that is a URL at which you can make a GET request with the proper Accept header and you will get the latest version of that Object. AFAIK there is no provision for IDs to change.

            • LachlanUnchained@lemmyunchained.net
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Understood. I don’t know how the devs intend to overcome that challenge. If if it’s even a realistic goal. I just know it gets discussed often.

        • Tetsuo@jlai.lu
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          1 year ago

          I think we should expect/aim to just have some “mass repost script” that can take an extract of a community’s content and just “repost” it on a new community.

          Basically, a script that would “replay” a community in one go. I don’t know if you could create “new comments” that immitates perfectly the original commenter but that would be the idea for a quick and very dirty “community mover script”.

          A bit like in GIT when you want to change/remove a specific commit, you can only replay/rebuild everything from the start by creating new everything posts/comments.

          Or maybe that’s a terrible plan ;)