I am currently getting “502 Bad Gateway” errors when trying to load it. Plus from everything i could tell federation was hours behind.

  • BrainisfineIthink@lemmy.one
    link
    fedilink
    arrow-up
    17
    ·
    1 年前

    People should REALLY stop joining Lemmy.ml, and users with an account on their instance should consider starting a new one on another instance. Every post they issue boils down to them essentially pleading for people to stop joining their instance and go basically anywhere else. Like, they’re not saying that to be assholes they’re saying it because they can’t keep up and are stressing the fuck out. Help em out!

      • BrainisfineIthink@lemmy.one
        link
        fedilink
        arrow-up
        3
        ·
        1 年前

        I may have to do that myself soon with my beehaw account. They had way fewer users when I joined, but you can almost FEEL the server stress using that instance the last two days. They’re getting absolutely crushed by the hug of love.

          • BrainisfineIthink@lemmy.one
            link
            fedilink
            arrow-up
            3
            ·
            1 年前

            They’ve gotten it significantly more stable the past couple days, but I do love my lemmy.one account. It feels like this instance flies way under the radar - probs because it’s not a specific community/vibe like beehaw, and because you can’t make your own communities here. Makes it extremely handy for people like me that just want a reliable instance to host their every day account.

    • NataliePortland@thegarden.land
      link
      fedilink
      arrow-up
      5
      ·
      1 年前

      We launched a lovely little instance today called thegarden.land : a garden bed where all are welcome to grow roots and thrive. Come join our instance and ease the burden on the bigger ones. Plus we’re giving away free flower seeds! It’s a win-win

  • canpolat@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 年前

    I believe that’s due to problems that occurred when upgrading to version 0.18.0. Hopefully they will be back soon.