Especially considering the way twitter counts a “view” is if the tweet shows up in your app’s viewport, at all. So simply scrolling through the timeline consumes “views” - you could run up against this limit in 10-15 minutes of scrolling.
This is what I was wondering. I don’t use Twitter so 600 sounds like a lot but I was wondering how much it actually was. Someone else said they blew through it in like 15 minutes
15 minutes if you actually read the tweets, but when this “reading limit” is actually “impression limit”, and Twitter counts an impression as a tweet just loading on your feed (I didn’t know this). About 2 minutes of continuous scrolling gets you rate limited.
Especially considering the way twitter counts a “view” is if the tweet shows up in your app’s viewport, at all. So simply scrolling through the timeline consumes “views” - you could run up against this limit in 10-15 minutes of scrolling.
It’s incredibly stupid.
This is what I was wondering. I don’t use Twitter so 600 sounds like a lot but I was wondering how much it actually was. Someone else said they blew through it in like 15 minutes
15 minutes if you actually read the tweets, but when this “reading limit” is actually “impression limit”, and Twitter counts an impression as a tweet just loading on your feed (I didn’t know this). About 2 minutes of continuous scrolling gets you rate limited.
And sounds like it’s implemented in a api-request=view way. I’m not sure how much requests the JS makes per view but im sure it’s more than one.