If there is any sort of novel scraping going on, and their only response is to shut down the site for all the accounts, their engineering capabilities have been pretty much zeroed out, and it's a massive indictment of the leadership decisions.
Plus, at this point believing anything that Musk says is extremely foolish. If this was something that was meant to believed, it would have been posted by somebody with more credibility in the organization who actually has something to lose by lying. That person is literally anyone except for Musk.
It's really hard for me to believe that a uniform 600 tweets read per _day_ limit for almost _all_ accounts is the best tool they have to mitigate a scraping attack. They likely have great insight into the risk profiles of each account based on age, size, past engagement. This is an incredibly coarse banhammer -- very close to just turning off the servers, IMO. Reasonable if it lasted for an hour, debatable if it lasts for a day, idiotic if it lasts longer.
Would love to see the inside story, hopefully it gets leaked/reported at some point.
> Lest anyone doubt that Twitter was idiotic enough to release code that would cause a race condition and result in its own users executing a DDOS attack on it, here's the network console readout from Firefox showing all the network requests blasting away.
Edit: looks like they fixed that issue with a login screen and no 10 requests per second issue. rats