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
> It's not a self ddos

Maybe not

> if twitter isn't going down

I disagree. Ddos is a type of attack, not the result of an attack. If they're hitting their services way too many times in a distributed fashion, it's a ddos regardless of how it was handled.

Similarly, would you say this[0] wasn't a ddos because it was mitigated? I think not.

[0] https://blog.cloudflare.com/26m-rps-ddos/

>>hn9272+rX
Self ddos is more fuzzy because there is no intent. If I wget all pages from a site's site map is that a dos? If it was architecture to handle that kind If load the site would be unaffected and if wasn't it could potentially cause availability problems. If after starting my download script I noticed the server couldn't handle my requests then I would recognize I am dosing them.

>>charci+R41
> more fuzzy because there is no intent

I agree. DoS is an attack, so without intent it is fuzzy. But I think it is pretty descriptive, so it's okay. I know exactly what self-ddos means instantly (flooding your own service, without malicious intent).

I think it's kind of a limitation with English or the term ddos. If it really is only used it for intent to attack, it becomes less useful of a word IMO.