• Whirlybird@aussie.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    But no one knows when that repeated call was added to twitter - it could have been there for years. Like I said, it also likely just gets caught by cloudflare etc when it’s doing that, meaning it’s not going to overwhelm anything.

    You’re saying that they did a release, realised it was going to DDOS itself, so then rate limited accounts in another release rather than simply roll back the broken release or fix the call? That doesn’t make any sense.

    • HeavyDogFeet@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      They didn’t realise it was going to DDOS itself, it was in the process of hammering their servers and they rate limited accounts because they didn’t know what was happening. It was still making excessive calls when they were rate limiting.

      It makes no sense because the things they’re doing aren’t the actions of a competent team with a knowledgeable tech lead.

      I think I’ve made my point pretty clear by now. If you’d still like to believe they’re not useless, go for gold, but the facts doesn’t support that.

      • Whirlybird@aussie.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        That’s 100% guessing based on nothing more than your wild speculation. You have no facts to support it.

          • Whirlybird@aussie.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            I’m not the one making claims, you are. You’ve got nothing to support those claims.

            As a developer myself I’m 99.9% sure what you’re claiming didn’t happen because it makes no sense from a dev standpoint.