I believe once all the hits for an authenticated user are used up Twitter will *not* start taking from the IPs allocated pool. I have not tested this though and could be wrong.
Actually rereading the last email looks like I am wrong. On Tue, Mar 24, 2009 at 16:06, bbc <beier...@gmail.com> wrote: > > Thanks for the quick answer. One more question, our service > (HootSuite.com) allow users to check their friends timelines, replies, > DMs... since all of these are authenticated requests, what we've been > assuming (and it seems have been working that way) was that, the first > 100 requests uses the user's limit, and if it goes over 100, it'll > start using our web server's limit. Is this actually the way Twitter > API is supposed to work? and in the future as well? > > Thanks again! > > On Mar 24, 12:27 pm, Doug Williams <d...@twitter.com> wrote: > > Rate limiting is IP specific. Therefore, you should find that you have > 20000 > > calls per individual IP. > > > > Thanks, > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw > > > > > > > > On Tue, Mar 24, 2009 at 3:15 PM, bbc <beier...@gmail.com> wrote: > > > > > Hi, right now our website needs multiple web servers, so we went ahead > > > and requested whitelisting for multiple IPs. But my question is, is > > > that 20000 limit per IP or it's aggregated per website even if it runs > > > on multiple servers (IPs). Thanks in advance- Hide quoted text - > > > > - Show quoted text - -- Abraham Williams | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from: Madison WI United States.
