lol you won't even be able to read viral tweet threads or the replies. The people paying to have their replies boosted are going to looooove this.

The best part is that all those "the site functions fine after layoffs!" morons won't realize that it's precisely because of those cuts that the service can no longer handle read traffic and they have to do this.

And the best part is that tracking this still requires write traffic for read status, so he's traded cheap reads for expensive writes.

Imagine how stupid you have to be to take your web site which traffics in popular posts driving engagement, and disincentivize 99% of your users from loading the most popular posts with the most interest around them because it will eat their daily allotment of reads if they do.

@rodhilton

In my opinion he had to due to losing Google cloud services

@ElonMusk my guess is during Google cloud payment negotiations he threatened to increase the price of Firehose API access that Google uses to search index public tweets, and someone on the call either threatened to or straight-up prototyped doing it via scraping so he did this to win the argument.

Pure self-immolation.