5 ms·

If you authorize the requests, you'll get a boost of the individual user's available requests after you run out of whitelist API requests for your IP (20000 + (

by timdorr 17y ago

If you authorize the requests, you'll get a boost of the individual user's available requests after you run out of whitelist API requests for your IP (20000 + (users * 150)). Also, make sure you're using the api.twitter.com/1/ URL format, as they're going to be upping the rate limit for users to 1000 "soon" (it was announced at Le Web 1.75 months ago...). Also, that only applies to OAuth, so you should get on that boat soon. They're deprecating basic auth this summer.

dangrossman 17y ago
For many accounts with more followers than they follow, there are more than 150 profiles I need to download. Someone just passed me an account with 6000 followers he's not following back. That's 6k API calls. I thought at first of using the 'followers' timeline' request to get 100 at a time, but the profile information it gives for each follower is abbreviated. I need other information, so I have to make a separate API call for each and every profile I want. Using up someone's entire API usage in a flash while they need it for the rest of the hour to run their Twitter client isn't gonna fly. The best I can do right now is make 20k authorized requests from my whitelisted account, and 20k unauthorized requests from my whitelisted IP. I just built in some status checking on the homepage so it won't let more people add themselves to the queue when it's already overloaded for the hour.
- timdorr 17y ago
  That's actually longstanding API request: http://code.google.com/p/twitter-api/issues/detail?id=1078&sort=-stars&colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component http://code.google.com/p/twitter-api/issues/detail?id=1078&#... It's one I would benefit from for my app as well. One thing to do is to cache the user information locally so that when they're requested again, you don't have to make an API call. For your app, I would think spammy users wouldn't change profile details all that often.
- arikfr 17y ago
  AFAIK, Twitter's API rate limit is per IP + per user (i.e. you can do X api requests per user on each machine). Also, on a whitelisted IP you get 20K requests per user. There was a long discussion about that a few months ago on the dev mailing list, whether this by purpose or mistake. Back then, the official response was that it's by purpose, but verify if that's true. If it is, you have plenty of API calls you can do per user.
  - dangrossman 17y ago
    It does seem to be. In this case, I have added reason to implement OAuth!

by timdorr 17y ago

dangrossman 17y ago

For many accounts with more followers than they follow, there are more than 150 profiles I need to download. Someone just passed me an account with 6000 followers he's not following back. That's 6k API calls. I thought at first of using the 'followers' timeline' request to get 100 at a time, but the profile information it gives for each follower is abbreviated. I need other information, so I have to make a separate API call for each and every profile I want. Using up someone's entire API usage in a flash while they need it for the rest of the hour to run their Twitter client isn't gonna fly. The best I can do right now is make 20k authorized requests from my whitelisted account, and 20k unauthorized requests from my whitelisted IP. I just built in some status checking on the homepage so it won't let more people add themselves to the queue when it's already overloaded for the hour.

timdorr 17y ago
That's actually longstanding API request: http://code.google.com/p/twitter-api/issues/detail?id=1078&sort=-stars&colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component http://code.google.com/p/twitter-api/issues/detail?id=1078&#... It's one I would benefit from for my app as well. One thing to do is to cache the user information locally so that when they're requested again, you don't have to make an API call. For your app, I would think spammy users wouldn't change profile details all that often.
arikfr 17y ago
AFAIK, Twitter's API rate limit is per IP + per user (i.e. you can do X api requests per user on each machine). Also, on a whitelisted IP you get 20K requests per user. There was a long discussion about that a few months ago on the dev mailing list, whether this by purpose or mistake. Back then, the official response was that it's by purpose, but verify if that's true. If it is, you have plenty of API calls you can do per user.
- dangrossman 17y ago
  It does seem to be. In this case, I have added reason to implement OAuth!