[twitter-dev] Re: Consumer Key and Secret Bug

2011-06-06 Thread iDeviceDesigns
On Jun 5, 1:22 pm, Tom van der Woerdt i...@tvdw.eu wrote: Well, using more than 350 requests per hour most certainly gets you a permanent block... Tom On 6/5/11 7:53 PM, iDeviceDesigns wrote: Would you mind clearing that up a little? 350 request per hour? I have been reading about

Re: [twitter-dev] Re: Consumer Key and Secret Bug

2011-06-06 Thread Tom van der Woerdt
API requests. Loading a page from https://api.twitter.com/1/ counts as 1 request. Of course, it goes per user per application, so the number of users isn't really relevant for iPhone applications. http://dev.twitter.com/pages/rate-limiting Tom On 6/5/11 10:39 PM, iDeviceDesigns wrote: On

[twitter-dev] Re: Consumer Key and Secret Bug

2011-06-05 Thread iDeviceDesigns
Dear iDeviceDesigns,         As you don't mention which route you are using, I can only make a guess.         I make almost every query to Twitter using the maximum count from iOS (200 tweets w/ user info and entities). On startup I also go get the most recent 800+ tweets. My access

Re: [twitter-dev] Re: Consumer Key and Secret Bug

2011-06-05 Thread Tom van der Woerdt
Well, using more than 350 requests per hour most certainly gets you a permanent block... Tom On 6/5/11 7:53 PM, iDeviceDesigns wrote: Dear iDeviceDesigns, As you don't mention which route you are using, I can only make a guess. I make almost every query to Twitter