An easier way of thinking about this is, 12 followed tweets with 50 replies each, 600 limit reached.
Do that in 10 idle times throughout your day (lots of people do more, like, say, Elon), and you hit even the verified limit.
Twitter with 600 tweets a day is clearly unusable. That’s one large thread, and you’ll scroll past most of it anyway.
That sounds like a miserable user experience in general, what compels you to seek out that experience?
This sounds more like unresolved personal grudges rather than an issue with the platform itself and the masses that use it. If you have a problem with the 600 tweet limit you can pay $8.
Everyone seems to forget that Twitter was bleeding money under the previous leadership. Unlimited free shit has its practical limits.
This isn’t theoretical; look at any high-traffic tweet (well, you can’t now; it’s broken. But if it comes back.) The top replies these days are virtually guaranteed to be nonsense.
Again I must ask, have you actually used the bloody website? It’s hard to imagine a regular user not being aware of this; it’s hard to miss.
Interesting Tweet Entirely Unrelated Recommended Blue Checkmark Tweet x 20 Related Replies x 20 Entirely Unrelated Recommended Blue Checkmark Tweet x 20 And so on.
The sea of bullshit to me is the huge chunks of Entirely Unrelated Recommended Blue Checkmark Tweets that are thrown into the reply chains.
If you for instance open the @elonmusk tweet announcing this, it will load dozens if not hundreds of replies, and those will all be counted against your quota. Do that a few times and you’re done in a few minutes.
I got rate limited after a few minutes of normal use. (Like most users I don’t have Twitter blue.)
Are you kidding? 6,000 tweets is literally like 10 minutes of scrolling through twitter. You're assuming each tweet to be worthy of being read. They aren't. You scroll through hundreds of them to find good threads.
When you make the good faith assumption that people are actually reading through the content, the numbers start to seem a bit more rational.
The good faith assumption here is that Twitter only counts tweets read but does that mean the client reads the tweet or the user? The server delivered them all the same, whether a human reads it or not. So does delivery of the tweet by loading it onto the device count or some nebulous amount of time spent lingering on the tweet?
> "I'm certain I scroll at least 100 tweets/minute."
Many Twitter users, including literally the person you are in conversation with, scroll through dozens/hundreds of tweets a minute.
Not sure if you're actually used Twitter before, but many tweets are only a line or two of text, and it doesn't take more than a second to process them.
Additionally, if you're quickly scrolling through replies or someone's history to try to find something, it can render hundreds of tweets in a matter of seconds.
I leave it running in a window while I do other things, and check in a few times a day. Thanks to Twitter product "development", the feed now auto-refreshes itself when you get back to it.