With forewarning about a huge influx of users, you know Lemmy.ml will go down. Even if people go to https://join-lemmy.org/instances and disperse among the great instances there, the servers will go down.

Ruqqus had this issue too. Every time there was a mass exodus from Reddit, Ruqqus would go down, and hardly reap the rewards.

Even if it’s not sustainable, just for one month, I’d like to see Lemmy.ml drastically boost their server power. If we can raise money as a community, what kind of server could we get for 100$? 500$? 1,000$?

  • Leigh@lemmy.ml
    link
    fedilink
    arrow-up
    8
    ·
    2 years ago

    You could configure something like a Cloudflare worker to throw up a page directing users elsewhere whenever healthchecks failed.

    • nutomic@lemmy.mlM
      link
      fedilink
      arrow-up
      20
      arrow-down
      2
      ·
      2 years ago

      Then cloudflare would be able to spy on all the traffic so thats not an option.

      • Leigh@lemmy.ml
        link
        fedilink
        arrow-up
        13
        arrow-down
        6
        ·
        2 years ago

        spy on all the traffic

        That’s…not how things work. Everyone has their philosophical opinions so I won’t attempt to argue the point, but if you want to handle scale and distribution, you’re going to have to start thinking differently, otherwise you’re going to fail when load starts to really increase.

        • TheAnonymouseJoker@lemmy.ml
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          2 years ago

          Cloudflare spies via decrypting any and all SSL traffic. They are a MITM company, and they started off originally as Project Honeypot, read about it. No, this is not philosophical or conspiratorial, this is reality.

      • wagesof@links.wageoffsite.com
        link
        fedilink
        arrow-up
        3
        ·
        2 years ago

        You could run an interstitial proxy yourself with a little health checking. The server itself doesn’t die, just the webapp/db. nginx could be stuck on there (if it’s not already there) with a temp redirect if the site is timing out.