Is lemmy.ml down? I can’t even open the page

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

      It’d be nice if servers could choose to mirror eachothers’ communities and users too - so you could log-in elsewhere, and post to a community from anywhere acting as a load balancer.

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

    Seems that way. lemmy.ml has been very sporadic all day. They simply don’t have a powerful enough server for the number of users they have, I think.

    All the more incentive to spread out and decentralize things.

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

    Lemmy.ml migrated to a new server today. I think probably about an hour before you posted. Things should smooth out a little, but that said the popular servers are getting absolutely hammered.

  • metarmask@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    Looks like it. Does this mean that what you wrote here will only be visible in the sh.itjust.works instance until lemmyml is online again, or is it more resilient than that?

    • TacoThrash3r@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      That I’m not sure, this community and instance is separate but is a fork so lemmy.ml may have something to do with it.

      I’m a bit new to all this so let me know if anything changes or if you still can’t post, I’ll find out what I can

      • Barbarian@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Basically, during the short stints where lemmy.ml is actually able to function, it sends out all posts & comments. Those posts & comments are cached on every subscribed server.

        This means that sh.itjust.works can interact with [email protected], post, comment, vote, but none of it is synced back with lemmy.ml until it recovers again. We’re communicating on the cached version on sh.itjust.works right now.