this post was submitted on 01 Jul 2023
208 points (99.5% liked)

Technology

16 readers
1 users here now

Talk about anything tech related!

founded 2 years ago
MODERATORS
208
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 18 points 2 years ago* (last edited 2 years ago) (2 children)

600 posts per day is damn nothing, yikes

[–] [email protected] 19 points 2 years ago (1 children)

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.

[–] [email protected] 14 points 2 years ago (2 children)

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

[–] [email protected] 12 points 2 years ago

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.

[–] [email protected] 2 points 2 years ago

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.