Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I work a good deal with the Twitter API (albeit with Python rather than Ruby), and as far as I know, you're out of luck here -- there's really no way around these rate limits for the API. </p> <p>You are not the only one who's unhappy about this development. I, as well as numerous other developers, have commented on this very issue <a href="https://dev.twitter.com/discussions/10644#comment-21949" rel="nofollow">here</a> -- given that the folks at Twitter have made no indication that these limits are going to change, it's probably safe to assume they're here to stay. </p> <p>With the exception of paying a third party data provider who might have all this data scraped, you're basically stuck with the 15 calls per fifteen minutes.</p> <p>On the other hand, if as you said, you're looking for an approximate answer, you might get away with taking a (statistically significant) sample of the followers of the original account. You didn't indicate how many followers there are for the original account, so I can't tell you the number of accounts you'd need to sample, but clearly there's no reason to pull in this data for all of the followers, assuming that the original account you're looking to analyze has a sufficiently large number of followers.</p> <p>I suppose that, in a pinch, you might be able to use multiple IP addresses and Twitter accounts to speed up this job, but there's a decent amount of groundwork you'd have to lay to do that, and it runs against the spirit if not the letter if Twitter's terms of service.</p> <p>I'm with you though -- 15 calls per 15 minutes for friends/followers data is no good. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload