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.
Omfg I just loaded Twitter for the first time in ages and did some casual scrolling, loading a few threads, standard stuff.
It took me 11 minutes to hit my daily cap. And that included the time I spent posting here to make fun of it.
And the UX when you hit it on reads is just that it says their own site is broken.
There is absolutely no way casual Twitter users will not hit these limits.
Reading your own tweets and replies counts against it. You can't even read your own notifications.
And of course it was all rolled out on a weekend so that some poor schmuck has to work the weekend to undo this idiocy.
@rodhilton
So does the app load an entire thread before showing the start tweet? Surely they should page the queries.
Have you reading it in a browser rather than the app? Any difference?
Another mechanism I thought of was that maybe it checks every account you follow so if you follow more than 800 , it hits the limit.
Rod Hilton
ExcelAnalytics