zlacker

>>ZacnyL+(OP)
It's not a self ddos if twitter isn't going down. You can see in the video twitter is properly handling the load and is returning HTTP 429 when the client is sending too many requests. Hitting the rate limiter or requesting a post is light weight. It's not like it's spamming login requests which require a lot of resources due to key stretching.

>>charci+sA
The theory here is that this JavaScript bug caused the huge increase in requests which is why Twitter introduced strict limits on how many tweets users could access.

So the result wasn't an outage, it was a radical reduction in functionality.

I think that still qualifies as a self-ddos.