For researchers and other consumers of Twitter's Public API, you will want to read this carefully: blog.twitter.com/developer/en_u
#bigdata #datascience #twitterapi
Conversation
Replying to
I'm confused by this; 100k requests per app/endpoint seems to be above the current rate limits from the docs already?
2
1
I don't think there was an app-level limit before, only a per app and user token rate limit, which meant you can use any N user tokens to get N*(1500 results per 15m). Now, it's 100k total results per day per *app*, regardless of user tokens. :(
1
2
Good point -- that's a pretty huge punch in the gut for applications using a lot of user auths.
1
1
ugh, maybe they can use some of the recovered compute cycles to figure out how to display threaded replies. yeah - this might well kill any timeline reader w more than a few K users. (kill==push to premium api)
1
1
I'd have no problem going to a premium API if their pricing structure wasn't so convoluted. If they offered a decent premium API for a hundred or whatever a month, I'm sure they could get plenty of takers -- but some of the pricing is just way too high.
totally agree, it's insane. sort of think it's inaccessible by design. The long tail of devs/startups don't turn the revenue dial. plus, support shit-show. fun browsing twittercommunity.com for a glimpse of that chaos.
1
1
It feels like we go through the same bullshit cycles. Young company gets VC -- introduces API so developers can help build the company with awesome tools. Company grows very large -- company gives the middle finger to devs and then neuters the API.
1
1
Show replies