zlacker

>>ZacnyL+(OP)
Oh come on. This is console.log spam. This isn’t a “self-DDoS”.

>>fwlr+CG
No, look closely: the animation does not show the console, it shows the network pane. Each line is a (presumably unsuccessful) request to the Twitter backend. If a lot of people have the Twitter web frontend open and running in this state, it could in fact overload the backend.

>>manana+rJ
Sure, I mis-spoke in saying it was console.log spam, that’s not specifically what’s happening. But let’s be real, if you’re getting a 429 response that is at most a cached hash table lookup per request, for a site has probably top 50 in the world in terms of “scaling to handle heavy request loads” for a decade.

There’s just no chance this specific thing is actually what’s causing issues for Twitter, it’s obviously a consequence of the heavy scraping and steps to stop the heavy scraping. It frustrates me to no end that smart technical software people, who can have intelligent discussions on not just code but a wide range of topics from nuclear powers to superconductors, suddenly lose their ability to have these discussions when a certain person is involved.

>>fwlr+r81
THANK YOU! i tried to mention this, but it got flagged quick. it's unbelievable that my median salary for the past decade is $3,000 after several years of "Startup" followed by "How to Start a Reboot of My Life"

>>36561808

it's a 429 error, so the developer who posted this is an idiot. they're not even wrong. the 429 doesn't even touch twitter's infrastructure

https://blog.twitter.com/engineering/en_us/topics/infrastruc...