[twitter-dev] Re: API Limits
It is odd that my app is held to a rate limit that is hidden from me. When I call the rate limit API, I get the rate for my IP address, which is meaningless when it comes to status updates. My only option is to keep sending status updates until I get a 403 error message back. I hope that won't earn me a blacklisting :-) Cheers, /Martin On Jul 15, 8:36 am, Bill Kocik wrote: > On Jul 15, 11:22 am, iUpdateStatus wrote: > > > As a general question related to this topic: For all the developers > > who are working on a solution that involves authenticated users, would > > it be more convenient to get removed from the whitelist (or never > > apply for it) and use the authenticated user's 150 requests/hour > > limit? > > For me, yes. When the user rate limit was 100, as few as 200 > simultaneous users have, collectively, the same rate limit as a > whitelisted IP. Now that the limit is 150, it only takes 133.3 > simultaneous users. > > If you anticipate having about 130 or more simultaneous users, > whitelisting can work against you, but it's not completely black and > white. If I have 50 really active users and 100 that aren't so active, > whitelisting might be in my favor, because it means I can spend more > requests on each of those 50 users than their 150/hr limit would > otherwise allow. > > It really depends on how many simultaneous authenticated users you > expect to have, what kind of users they are, and what kind of API > requests your application is making on their behalf. For my > application, whitelisting doesn't make sense. For yours it might.
[twitter-dev] Re: API Limits
On Jul 15, 11:22 am, iUpdateStatus wrote: > As a general question related to this topic: For all the developers > who are working on a solution that involves authenticated users, would > it be more convenient to get removed from the whitelist (or never > apply for it) and use the authenticated user's 150 requests/hour > limit? For me, yes. When the user rate limit was 100, as few as 200 simultaneous users have, collectively, the same rate limit as a whitelisted IP. Now that the limit is 150, it only takes 133.3 simultaneous users. If you anticipate having about 130 or more simultaneous users, whitelisting can work against you, but it's not completely black and white. If I have 50 really active users and 100 that aren't so active, whitelisting might be in my favor, because it means I can spend more requests on each of those 50 users than their 150/hr limit would otherwise allow. It really depends on how many simultaneous authenticated users you expect to have, what kind of users they are, and what kind of API requests your application is making on their behalf. For my application, whitelisting doesn't make sense. For yours it might.
[twitter-dev] Re: API Limits
I don't have a IP that is whitelisted. Only my twitter account is whitelisted. Thanks, Greg On Jul 15, 9:27 am, Abraham Williams <4bra...@gmail.com> wrote: > Are you getting this from an IP that is whitelisted? > > Abraham > > On Wed, Jul 15, 2009 at 08:20, Greg wrote: > > > Is anyone else getting 20,000 API calls when calling the > > rate_limit_status API? It doesnt matter who I authenticate with - it > > always shows 20,000 API calls for the user. Unless Twitter has given > > everyone 20,000 - I don't think that this is right. > > > Thanks, > > Greg > > -- > Abraham Williams | Community Evangelist |http://web608.org > Hacker |http://abrah.am|http://twitter.com/abraham > Project |http://fireeagle.labs.poseurtech.com > This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: API Limits
I am getting the 20,000 limit, but the requests are being made from a whitelisted IP. According to the documentation, whitelisted IP take precedence over authentication, so requests will count against your IP limit rather than the user's. As a general question related to this topic: For all the developers who are working on a solution that involves authenticated users, would it be more convenient to get removed from the whitelist (or never apply for it) and use the authenticated user's 150 requests/hour limit? On Jul 15, 8:20 am, Greg wrote: > Is anyone else getting 20,000 API calls when calling the > rate_limit_status API? It doesnt matter who I authenticate with - it > always shows 20,000 API calls for the user. Unless Twitter has given > everyone 20,000 - I don't think that this is right. > > Thanks, > Greg
[twitter-dev] Re: API Limits
Are you getting this from an IP that is whitelisted? Abraham On Wed, Jul 15, 2009 at 08:20, Greg wrote: > > Is anyone else getting 20,000 API calls when calling the > rate_limit_status API? It doesnt matter who I authenticate with - it > always shows 20,000 API calls for the user. Unless Twitter has given > everyone 20,000 - I don't think that this is right. > > Thanks, > Greg -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: API limits - what am I missing? Seeking clarity on API request limits.
> > I'd like to pull about 1950 statuses, all of my updates, in one API > connection. > Is my limit 200 per API request (requiring 10 API requests) OR is my limit > 1950 in one API request? You can get 200 statuses per requests. Therefore you will have to use 10 calls to retrieve 1950 statuses. Paging in this way is the most effective, server friendly way to do this. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 18, 2009 at 1:07 PM, Khyron wrote: > I see the 2 following statements made, in the following order within > moments > of each other at http://apiwiki.twitter.com/REST+API+Documentation. > > > Under "Pagination Limiting": > > "Clients may request up to 3,200 statuses via the page and count > parameters. Requests for more than the limit will result in a reply with a > status code of 200 and an empty result in the format requested." > > Under "Be Nice to the Servers": > > "If your application keeps a local archive that persists between sessions, > it's > okay to request an entire timeline up to 200 statuses." > > > So I can only request up to 200 statuses even though the limit using page > or count is 3200? What gives? > > I'd like to pull about 1950 statuses, all of my updates, in one API > connection. > Is my limit 200 per API request (requiring 10 API requests) OR is my limit > 1950 in one API request? Are there other parameters besides page and > count which are more server friendly, thus allowing larger requests? > > What am I missing? Can someone clarify please? Now that I figured out > how to do what I want to do, I want to make sure that I play by the rules > so that I don't get blacklisted for killing the servers. > > Thanks in advance yet again! > > -- > "You can choose your friends, you can choose the deals." - Equity Private > > AlphaGuy - http://alphaguy.blogspot.com > On Twitter - @khyron4eva > >
