There are some API methods that don't have the concept of an unauthenticated
user -- these "public-only" resources will not consider OAuth credentials
when calculating the rate limit. We are looking to make the application of
rate limiting across resources, regardless of whether the resource expect
Thanks for the reply, Igor...
Yes it should be. The problem is that the headers are giving me the limit
150 rather than the expected 350 after OAuth.
Any ideas why this is the case?
Thanks again.
On Mon, Nov 29, 2010 at 8:17 PM, Igor Kharin wrote:
> All rate limited methods responses include
All rate limited methods responses include X-Ratelimit-Remaining and
X-Ratelimit-Limit HTTP-headers, use them or
http://dev.twitter.com/doc/get/account/rate_limit_status
On Fri, Nov 26, 2010 at 1:55 PM, m36tb6ll wrote:
>
> Hi! I am a newbie in the field and am working on my first twitter web
> ap
it's 150 requests for flat file data per hour and 350 oauthenticated calls per
hour ... unless you use a proxy. :P
On Nov 26, 2010, at 2:55 AM, m36tb6ll wrote:
>
> Hi! I am a newbie in the field and am working on my first twitter web
> app. I have created a variable loop timer using rate_limit_
Hi! I am a newbie in the field and am working on my first twitter web
app. I have created a variable loop timer using rate_limit_status
which works well in maximizing the usage of the twitter API without
going over the hourly limits.
Now that I have incorporated OAuth, I was expecting to see the