You are viewing a single thread.
View all comments View context
19 points

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.

permalink
report
parent
reply
14 points

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

permalink
report
parent
reply
12 points

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.

permalink
report
parent
reply
2 points

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.

permalink
report
parent
reply

Technology

!tech@lemmy.fmhy.ml

Create post

Talk about anything tech related!

Community stats

  • 1

    Monthly active users

  • 58

    Posts

  • 550

    Comments