Are the registry procedures causing the problem? Since most of my communities are on lemmy.ml, wouldn’t I still be using lemmy.lm’s bandwidth? Or is it more crucial to ensure that the communities are distributed more evenly across different instances?

  • bdonvr@lemmy.rogers-net.com
    link
    fedilink
    English
    arrow-up
    15
    ·
    1 year ago

    It doesn’t really. I’m viewing this post from my instance, which has saved a copy of this post from lemmy.ml

    Me viewing this post doesn’t hit lemmy.ml at all, although making this comment will.

      • aponigricon@beehaw.org
        link
        fedilink
        English
        arrow-up
        10
        ·
        1 year ago

        All the users and communities registered there will cease being able to connect to the rest of the network, but the data should still be cached on all the other servers.

        • tiwenty@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          The keyword is “cache”. Lemmy doesn’t guarantee the cache, so if an instance X would go down permanently, you would eventually lose this data.

          • aponigricon@beehaw.org
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            My presumption was that with over 200 instances, maybe over 1000 in the near future, all the old data should be collectable in theory without loss. But you’re right, there’s no guarantee of this.

      • bdonvr@lemmy.rogers-net.com
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        Media from users of lemmy.ml won’t load. You wouldn’t be able to subscribe to communities on lemmy.ml. But I think every other instance would show cached data and hold any new comments/posts/votes to sync when lemmy.ml comes back up. I’m not sure how long that cache is kept.