[twitter-dev] Rate Limit

[twitterwidget]

Can someone please help me to understand how rate limiting works for
twitter widget, either the profile or the list widget. I have gone
through the rate limit faq here http://dev.twitter.com/pages/rate_limiting_faq
which talks about authorized and unauthorized requests which is a bit
confusing to me.

I want to understand this because the widget goes blank on our site
sometimes, which we don't want it to happen.

Can you please help.

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Rate limit exceeded. Clients may not make more than 150 requests per hour

[Correa Denzil]

Please read the Rate Limiting documentation carefully. You need to make
OAuth requests to increase your rate to 350 per hour.

Whitelisting is no longer permitted.

--Regards,
Denzil



On Mon, Jul 4, 2011 at 6:05 PM, Tushar  wrote:

> I am new to twitter API.
> I am retrieving  the tweets of a particular user. It was working
> yesterday but some how from morning I am getting this errror:-
> "Rate limit exceeded. Clients may not make more than 150 requests per
> hour
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Rate limit exceeded. Clients may not make more than 150 requests per hour

[Tushar]

Hi,
I am new to twitter API.
I am retrieving  the tweets of a particular user. It was working
yesterday but some how from morning I am getting this errror:-
"Rate limit exceeded. Clients may not make more than 150 requests per
hour"

I have searched for this error I found that I have exceeded the limit
of number of request. Can anyone tell me how to get rid of this
problem?

 Also, I found that whitelisting the my IP will solve the problem, How
could I whitelist my IP?

Thanks,
Tushar

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Rate limit status keeps decreasing

[Tom van der Woerdt]

"My script is on a web site with a dedicated IP address."

You'll find that for outgoing traffic the server will pick the standard 
IP address, not the one used by the website.


Try authenticating the requests, it helps. Alternatively, use code to 
use the right IP address.


Tom


On 5/28/11 10:51 AM, Jeffski wrote:

My rate limit status keeps decreasing to 0 even though as far as I can
tell I am only making 24 requests per hour.

I have a simple PHP web page that calls this 24 times per hour using
CURL:
http://api.twitter.com/1/statuses/user_timeline.json?count=1&screen_name={user_name_here}

Responses are cached and logged so a) I shouldn't go over the limit
and b) I can track exactly when the calls are made and confirm my PHP
script is only making 24 requests per hour.

For some reason the rate limit status decreases to 0 after about half
an hour.

Any ideas what I can be doing wrong or if the rate limit can be
decreased by something else other than my script. My script is on a
web site with a dedicated IP address.



--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Rate limit status keeps decreasing

[Jeffski]

My rate limit status keeps decreasing to 0 even though as far as I can
tell I am only making 24 requests per hour.

I have a simple PHP web page that calls this 24 times per hour using
CURL:
http://api.twitter.com/1/statuses/user_timeline.json?count=1&screen_name={user_name_here}

Responses are cached and logged so a) I shouldn't go over the limit
and b) I can track exactly when the calls are made and confirm my PHP
script is only making 24 requests per hour.

For some reason the rate limit status decreases to 0 after about half
an hour.

Any ideas what I can be doing wrong or if the rate limit can be
decreased by something else other than my script. My script is on a
web site with a dedicated IP address.

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Rate limit HTTP responses

[hax0rsteve]

Thanks Taylor, that's the info I need :)

hax0rsteve



On 21 Mar 2011, at 18:57, Taylor Singletary wrote:

> Hi there Steve,
> 
> As you've noticed, Search API rate limiting is applied and handled quite 
> differently from the rest of the REST API. In the case of Search, when 
> everything is operating under typical conditions, a Retry-After HTTP header 
> will be sent to you (not an X-Retry-Header)  -- the value of that header will 
> contain an integer indicating the number of seconds to wait until issuing 
> additional search API requests.
> 
> Taylor
> 
> On Sun, Mar 20, 2011 at 10:43 AM, hax0rsteve  wrote:
> 
> 
> Hi all,
> 
> A question w/r/t HTTP responses when rate limiting is applied, which I'm 
> hoping
> some kind soul will answer before I start hammering away at the API in 
> careless
> experimentation :
> 
> 420 Enhance Your Calm
> 
> I understand from the docs that when this status code is returned, a 
> "Retry-After"
> header will be returned in my http response, does this take the same format as
> the other rate headers e.g. :
> 
> X-RateLimit-Limit: 350
> X-RateLimit-Remaining: 350
> X-RateLimit-Reset: 1277485629
> 
> so the Retry-After header will be  "X-Retry-After:"  ?  Or is it some other 
> format ?
> 
> Obviously I could find out by jamming a huge number of search requests at the 
> API,
> but it would be nice to know what to look for beforehand so that I can tell 
> when to stop :)
> 
> Thank you kindly.
> 
> 
> hax0rsteve
> 
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk
> 
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate limit HTTP responses

[Taylor Singletary]

Hi there Steve,

As you've noticed, Search API rate limiting is applied and handled quite
differently from the rest of the REST API. In the case of Search, when
everything is operating under typical conditions, a Retry-After HTTP header
will be sent to you (not an X-Retry-Header)  -- the value of that header
will contain an integer indicating the number of seconds to wait until
issuing additional search API requests.

Taylor

On Sun, Mar 20, 2011 at 10:43 AM, hax0rsteve wrote:

>
>
> Hi all,
>
> A question w/r/t HTTP responses when rate limiting is applied, which I'm
> hoping
> some kind soul will answer before I start hammering away at the API in
> careless
> experimentation :
>
> 420 Enhance Your Calm
>
> I understand from the docs that when this status code is returned, a
> "Retry-After"
> header will be returned in my http response, does this take the same format
> as
> the other rate headers e.g. :
>
> X-RateLimit-Limit: 350
> X-RateLimit-Remaining: 350
> X-RateLimit-Reset: 1277485629
>
> so the Retry-After header will be  "X-Retry-After:"  ?  Or is it some other
> format ?
>
> Obviously I could find out by jamming a huge number of search requests at
> the API,
> but it would be nice to know what to look for beforehand so that I can tell
> when to stop :)
>
> Thank you kindly.
>
>
> hax0rsteve
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate limit HTTP responses

[hax0rsteve]

No one ? 

On 20 Mar 2011, at 17:43, hax0rsteve wrote:

> 
> 
> Hi all,
> 
> A question w/r/t HTTP responses when rate limiting is applied, which I'm 
> hoping
> some kind soul will answer before I start hammering away at the API in 
> careless
> experimentation :
> 
> 420 Enhance Your Calm
> 
> I understand from the docs that when this status code is returned, a 
> "Retry-After"
> header will be returned in my http response, does this take the same format as
> the other rate headers e.g. :
> 
> X-RateLimit-Limit: 350
> X-RateLimit-Remaining: 350
> X-RateLimit-Reset: 1277485629
> 
> so the Retry-After header will be  "X-Retry-After:"  ?  Or is it some other 
> format ?
> 
> Obviously I could find out by jamming a huge number of search requests at the 
> API,
> but it would be nice to know what to look for beforehand so that I can tell 
> when to stop :)
> 
> Thank you kindly.
> 
> 
> hax0rsteve
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Rate limit HTTP responses

[hax0rsteve]

Hi all,

A question w/r/t HTTP responses when rate limiting is applied, which I'm hoping
some kind soul will answer before I start hammering away at the API in careless
experimentation :

420 Enhance Your Calm

I understand from the docs that when this status code is returned, a 
"Retry-After"
header will be returned in my http response, does this take the same format as
the other rate headers e.g. :

X-RateLimit-Limit: 350
X-RateLimit-Remaining: 350
X-RateLimit-Reset: 1277485629

so the Retry-After header will be  "X-Retry-After:"  ?  Or is it some other 
format ?

Obviously I could find out by jamming a huge number of search requests at the 
API,
but it would be nice to know what to look for beforehand so that I can tell 
when to stop :)

Thank you kindly.


hax0rsteve

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate Limit problem even with 20k calls?

[Matt Harris]

Hey Hugo,

The rate limit you refer to is for the REST API only.
The Search API, which it looks like your using, has it's own rate limiting
system external to the REST API.

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris


On Wed, Mar 9, 2011 at 2:38 PM, Hugo W  wrote:

> Hey guys,
>
> Does Twitter have changed how limit calls are applied on the API?
>
> I have 20k calls per hour, but when i do a simple search call, i get
> { ["error"]=> string(46) "You have been rate limited. Enhance your
> calm." }, and yes, i still get 10k calls left to use.
>
> Any clues? Is this any king of bug?
>
> Ty
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Rate Limit problem even with 20k calls?

[Hugo W]

Hey guys,

Does Twitter have changed how limit calls are applied on the API?

I have 20k calls per hour, but when i do a simple search call, i get
{ ["error"]=> string(46) "You have been rate limited. Enhance your
calm." }, and yes, i still get 10k calls left to use.

Any clues? Is this any king of bug?

Ty

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate limit

[Adam Green]

If you are logging every tag ever found in your search results, and
then trying to search for them continuously, you need to change your
model. Twitter will no longer allow that type of access. They have
made this clear through words and actions. You should focus on
tracking the tags that are used most often. It is a power curve. In
every set of words I have studied, 100-200 tags get 80% of the
traffic. Streaming allows you to track 400 words. Limit yourself to
400 of the most used tags. Any other expectation is unreasonable.

On Mon, Feb 28, 2011 at 12:43 AM, manaf pm  wrote:
> I have a website which grabs tweets from twitter.com within 20 minutes
> interval per day. I h ave stored thousands of hashtags in my database
> and search is occurring against these hash tags and user names. Right
> now there I need around 65000 search requests to be happened per day.
> Here comes the rate limit problem. As a result I am not getting
> desired search results for a long time. How can I over come this? Any
> replies are welcome and will be helpful to me.
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk
>



-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Rate limit

[manaf pm]

I have a website which grabs tweets from twitter.com within 20 minutes
interval per day. I h ave stored thousands of hashtags in my database
and search is occurring against these hash tags and user names. Right
now there I need around 65000 search requests to be happened per day.
Here comes the rate limit problem. As a result I am not getting
desired search results for a long time. How can I over come this? Any
replies are welcome and will be helpful to me.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate limit on streaming api since last week?

[Tom van der Woerdt]

IF you get limited, you will get a notice about it in the stream.

Tom


On 2/22/11 5:38 PM, PanMan wrote:

Hi!
Last week I did some tests by getting some tweets from the streaming
API by  filter with a few high-trafic keywords.
Last week we were getting between 10 and 20 tweets per second.
This week we are 'only' getting about 4 a second. At this moment I can
see at least about 10/second new results on search.twitter.com
We haven't changed the keywords we look for.
Is the streaming API on filter still limited? And did something change
last week in the number of results send out?
Thanks!
PanMan.



--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Rate limit on streaming api since last week?

[PanMan]

Hi!
Last week I did some tests by getting some tweets from the streaming
API by  filter with a few high-trafic keywords.
Last week we were getting between 10 and 20 tweets per second.
This week we are 'only' getting about 4 a second. At this moment I can
see at least about 10/second new results on search.twitter.com
We haven't changed the keywords we look for.
Is the streaming API on filter still limited? And did something change
last week in the number of results send out?
Thanks!
PanMan.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Rate limit over 3G

[lbstephane]

Hi,

I'm currently dev an iPhone App displaying a twitter timeline.

So I use this :

http://api.twitter.com/1/statuses/user_timeline.json?screen_name=MyUserTimeLine=20

It works fine with wifi but with 3G or Edge, got a message : Rate
limit exceeded. Clients may not make more than 150 requests per hour.

What can I do ? May I have to register this app or something like
this ?

Thanks for your help.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate limit for streaming api (tracking keyword)

[John Kalucki]

http://dev.twitter.com/pages/streaming_api_concepts#filter-limiting
http://dev.twitter.com/pages/streaming_api_concepts#parsing-responses


On Thu, Oct 28, 2010 at 9:55 PM, Thiago Esteves wrote:

> Hi,
>
> I am developing an application that needs to track a keyword on
> twitter, that keyword is a hashtag, the frequency of that keyword is
> not high, but the application needs to stay listening and don't stop
> never. What is the rate limit Twitter apply for this case? Could not
> find it on twitter devel pages.
>
> Thanks
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate limit for streaming api (tracking keyword)

[Tom van der Woerdt]

There is no real limit on the stream API, because it is an open connection that 
stays open. As long as you don't connect/disconnect too often, you will not hit 
any limits.

Tom


On Oct 29, 2010, at 6:55 AM, Thiago Esteves  wrote:

> Hi,
> 
> I am developing an application that needs to track a keyword on
> twitter, that keyword is a hashtag, the frequency of that keyword is
> not high, but the application needs to stay listening and don't stop
> never. What is the rate limit Twitter apply for this case? Could not
> find it on twitter devel pages.
> 
> Thanks
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Rate limit for streaming api (tracking keyword)

[Thiago Esteves]

Hi,

I am developing an application that needs to track a keyword on
twitter, that keyword is a hashtag, the frequency of that keyword is
not high, but the application needs to stay listening and don't stop
never. What is the rate limit Twitter apply for this case? Could not
find it on twitter devel pages.

Thanks

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate limit not getting reset

[Slate Smith]

Every set of calls I log my rate limit api calls remaining [ $App- 
>APICallsRemaining;] for later tracking ...


On Oct 20, 2010, at 2:08 PM, Josh wrote:


I keep having troubles with an application I'm developing that uses
the Twitter API.  I'm getting errors stating that I'm over my rate
limit, but it's been more than an hour since I last made a call.

My status does say 0 left of 150, but the last time I made a call was
a couple hours ago.

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Rate limit not getting reset

[Josh]

I keep having troubles with an application I'm developing that uses
the Twitter API.  I'm getting errors stating that I'm over my rate
limit, but it's been more than an hour since I last made a call.

My status does say 0 left of 150, but the last time I made a call was
a couple hours ago.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Rate Limit Remaining makes no sense

[DaveH]

See if this chain of calls and the ratelimit remaining make any
sense...

API callReturned Ratelimit Remaining
Verify Credentials  188
Followers IDs181
Direct Messages   171

The request to verify credentials established that I have 188 calls
left. Since I have been testing this is OK, my max is 350.
The request for followers returned 1 follower and Twitter reduced the
ratelimit by 7.
The request for 10 direct messages, returned ZERO, and my ratelimit is
reduced by 10.

While I was typing this note, I did not perform any API calls. Then,
to see what happens with the calls, I execute the above sequence
again, and this is what I see.

API callReturned Ratelimit Remaining
Verify Credentials  71
Followers IDs52
Direct Messages   39

Now, I would have expected that my application would have had 171
remaining when I ran it again, not 71. It is also strange that it is
100 off. Then the difference between the other API calls is bigger
than the last time I ran to code.

It seems that the rate limit is a bit capricious. I understand that
Twitter says they will reduce based on load, but this is behavior is a
bit strange. This makes no sense to me. Anyone have an idea why the
rate limit would jump around so much?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Rate Limit Decrement

[kme]

I have some questions regarding the message on http://countdowntooauth.com/

"...starting on August 16th, the rate limits on basic authentication
will be reduced by roughly 10 calls/hour/day ending on August 31st."

Does this mean each user can login/post 150 times per hour on 8/16 and
then 140 times per hour on 8/15? or does the rate limit decrease each
hour, starting at 12:00 AM on 8/16 with the rate being 0 per hour at
3:00 PM, starting over on 8/17 at 12:00 AM.

I appreciate any help w/ regard to this!

Re: [twitter-dev] Rate limit on Oauth resources and Request token Expiration

[Matt Harris]

Hi Worth,

The OAuth endpoints are not rate limited despite the documentation saying it
is. We are aware of the documentation being wrong in this regard and have an
updated version in the queue to go out. The request tokens are short lived.
I don't have the exact lifetime to hand but I would recommend they are used
in the /authorize call within a couple of minutes of being received. The
tokens you get back from /access_token are permanent and will only stop
working if the user removes your application from their account or you
regenerate your keys and don't update the client.

Hope that helps,
Matt

On Thu, Jul 8, 2010 at 2:03 PM, Worth  wrote:

> Is Twitter going to start rate limiting the oauth resources or is
> dev.twitter.com is still being worked on?
> http://dev.twitter.com/doc/post/oauth/request_token
>
> Also what is the request token expiration time limit before they
> expire or does it vary for some reason?
>
> thanks,
> -Worth
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Rate limit on Oauth resources and Request token Expiration

[Worth]

Is Twitter going to start rate limiting the oauth resources or is
dev.twitter.com is still being worked on?
http://dev.twitter.com/doc/post/oauth/request_token

Also what is the request token expiration time limit before they
expire or does it vary for some reason?

thanks,
-Worth

Re: [twitter-dev] Rate limit exceeded. Clients may not make more than 75 requests per hour.

[M. Edward (Ed) Borasky]

Quoting goodtest :


We make only about 20-25 requests per hour. We didnt have any problems
until today morning. And all of a sudden I am seeing "Rate limit
exceeded. Clients may not make more than 75 requests per hour."

This is Zimbra Collaboration Suite's Social Zimlet.



I am also seeing tweets from friends that Tweetdeck is running into  
problems. I don't have Tweetdeck, so I can't confirm it. Perfect storm?

[twitter-dev] Rate limit exceeded. Clients may not make more than 75 requests per hour.

[goodtest]

We make only about 20-25 requests per hour. We didnt have any problems
until today morning. And all of a sudden I am seeing "Rate limit
exceeded. Clients may not make more than 75 requests per hour."

This is Zimbra Collaboration Suite's Social Zimlet.

[twitter-dev] Rate Limit Update

[themattharris]

Hey everyone,

We announced last week that we would be dynamically changing rate
limits and many of you noticed we have been doing that. There are many
techniques we've used and improvements we will continue to make to
deal with our capacity issues. Reducing the API rate-limit is not the
first or only method we use and is one we try to avoid if possible.
However, it is also one of the more effective ways to reduce load and
ensure that the Twitter service remains available to the greatest
number of users.

To ensure we can maintain service we're lowering the default rate
limit to 175.

Even with this lowered default limit we will still have times when we
need to dynamically change the allowed requests. Today is one of those
days where that has been required. In these situations you can stay up
to date by visiting http://status.twitter.com and following
@twitterapi.

We're all in the same boat here, Twitter uses the API for it's own
services so we also feel these reduced limits. All the Twitter for
mobile devices and mobile sites are being affected by this change. But
we need to do this to ensure the site and API stay available to as
wide an audience as possible. We don't want to be delivering service
failures to everyone.

We know there are still some questions around the dynamic rate
limiting and we have put together an FAQ at 
http://dev.twitter.com/pages/rate_limiting_faq
which we hope answers them.

Thank you for your patience.

Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Rate limit reduction to 75?

[SM]

I have an OAuth app (http://mowglii.com/itsy) and I'm getting errors
saying I'm limited to 75 requests per hour. Huh?

Re: [twitter-dev] Rate limit question (again/followup) 20k user or ip?

[Zac Bowling]

Whitelisted users get 20k API requests when they are authenticated no matter 
the IP.  

For whitelisted IPs, get 20k requests per hour for unathenticated calls. 

I don't know what happens in the overlap for authenticated calls from 
whitelisted IPs off the top of my head. 


Zac Bowling
@zbowling


On Aug 9, 2009, at 10:17 PM, Bob Fishel wrote:

> 
> Since we have a lot of devs monitoring this now I'd like to bring back
> the discussion that we were having before this whole mess started.
> 
> Is the intention of Twitter to allow (for whitelisted IP's) 20k
> requests per hour per USER or 20k requests per hour per IP.
> 
> I don't want to seem to be beating a dead horse and Chad has confirmed
> this but it still seems like there's quite a bit on contention.
> 
> Thanks
> 
> -Bob

[twitter-dev] Rate limit vs followings limit?

[PapaGummy]

I'm writing a little app and I need to know how to get followers limit
so I display a warning message and user won't get banned

For some reason I thought Rate limit is Followings limit
but discovereg yesterday it is not true
http://api.twitter.com/1/account/rate_limit_status.xml

What's the call I need to make to see how many Followings limit user
has/I have?

Thanks

Re: [twitter-dev] Rate limit status with authentication credentials for authenticated user account.

[Rushikesh Bhanage]

   Yes Mr. Williams I should not use this method if it is so, then what
is the way out to deal with my problem. OK I will go with OAuth but I don't
understand how to implement it in my app. Because in my code, I am using
this url to get remaining hits "
http://twitter.com/account/rate_limit_status.xml";. What I want is , I have
two accounts X and Y(both authenticated), I should get X's and Y's remaining
hits separately with this url or OAuth. As per Twitter I can't use
username/password method after June. Then option remains is OAuth. Will
Oauth give me separate hits of both A/cs through coding without using
customized window? If yes, then how ?
 We are going to white-list these a/cs if it worked on current api
requests. So please guide me in this problem.

 waiting for reply eagerly,
Thank you very much in advance.


On Thu, Apr 29, 2010 at 11:48 PM, Abraham Williams <4bra...@gmail.com>wrote:

> http://dev.twitter.com/doc/get/account/rate_limit_status
>
> You should avoid
> using username/password to authenticate as you will just have to update the
> code in June when BasicAuth is removed.
>
> Abraham
>
>
> On Thu, Apr 29, 2010 at 03:58, Rushikesh Bhanage 
> wrote:
>
>> Hi there,
>>
>>We are developing an app in which we need little of your help. may I
>> know how to get rate-limit status if we provide authentication credentials
>> of an authenticated user. is it possible if we provide user name and
>> password manually through code instead of twitter OAuth. If it is, how can
>> we do that?
>>
>>
>>
>> waiting for reply eagerly,
>> Thank you very much in advance.
>>
>>
>
>
> --
> Abraham Williams | Developer for hire | http://abrah.am
> @abraham | http://projects.abrah.am | http://blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.
>

Re: [twitter-dev] Rate limit status with authentication credentials for authenticated user account.

[Abraham Williams]

http://dev.twitter.com/doc/get/account/rate_limit_status

You should avoid
using username/password to authenticate as you will just have to update the
code in June when BasicAuth is removed.

Abraham

On Thu, Apr 29, 2010 at 03:58, Rushikesh Bhanage wrote:

> Hi there,
>
>We are developing an app in which we need little of your help. may I
> know how to get rate-limit status if we provide authentication credentials
> of an authenticated user. is it possible if we provide user name and
> password manually through code instead of twitter OAuth. If it is, how can
> we do that?
>
>
>
> waiting for reply eagerly,
> Thank you very much in advance.
>
>


-- 
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.

[twitter-dev] Rate limit status with authentication credentials for authenticated user account.

[Rushikesh Bhanage]

Hi there,

   We are developing an app in which we need little of your help. may I know
how to get rate-limit status if we provide authentication credentials of an
authenticated user. is it possible if we provide user name and password
manually through code instead of twitter OAuth. If it is, how can we do
that?



waiting for reply eagerly,
Thank you very much in advance.

[twitter-dev] Rate Limit Error Messages?

[briantroy]

I just started getting rate limit errors from the Search API. I have
not come anywhere near the limit for my whitelisted IP address (as a
note, I count every hit on the api and keep totals in memcache so I
can check my status).

I've stopped all processes for the time being.

The IP address in question is: 174.129.117.107

It is (one of several) whitelisted under my username "briantroy".


Please advise ASAP.

Brian Roy

602.325.3393
brian@justsignal.com

Re: [twitter-dev] Rate Limit Problem

[Scott Wilcox]

Hi,

Are you sure thats not the user you're requesting being suspended rather that 
you?

Have you checked your HTTP response to see how many API calls you have left?

Scott.

On 22 Feb 2010, at 13:23, jtrigsby wrote:

> Greetings gang,
> 
> I'm running into a problem that I suspect is rate limit related.
> 
> I have an hourly job scheduled to fetch details of my followers.
> 
> The first call checks the rate_limit and calculates the max number of
> getUser calls to make this hour. For example, if my remaining calls is
> 149, it will make 49 calls.
> 
> After about 15 calls each time, I get the following message:
> 
> Uncaught exception 'TwitterException' with message 'User has been
> suspended.'
> 
> ( I get the uncaught exception part) but any thoughts on what's going
> on here?
> 
> Thanks in advance.
> 



smime.p7s
Description: S/MIME cryptographic signature

[twitter-dev] Rate Limit Problem

[jtrigsby]

Greetings gang,

I'm running into a problem that I suspect is rate limit related.

I have an hourly job scheduled to fetch details of my followers.

The first call checks the rate_limit and calculates the max number of
getUser calls to make this hour. For example, if my remaining calls is
149, it will make 49 calls.

After about 15 calls each time, I get the following message:

Uncaught exception 'TwitterException' with message 'User has been
suspended.'

( I get the uncaught exception part) but any thoughts on what's going
on here?

Thanks in advance.

[twitter-dev] Rate limit HTTP response

[EastSideDev]

Prior to doing a rate-limit API, I always get the
http://twitter.com/account/rate_limit_status.xml (using my
credentials). Every once in a while, I get an HTTP response code of 0
(even though the previous call may have told that I still have more
than 19,000 calls left. My workaround is is do..while loop, with a
break of 10 loops.

Any suggestions?

Re: [twitter-dev] Rate limit bumped to 350 for OAuth REST?

[Marcel Molina]

If you are using the api.twitter.com endpoint and signing your request with
OAuth, you automatically get this higher rate limit. It's currently at 350
but we are planning on gradually ramping it up to a higher level. This was
announced on this mailing list around the original announcement happened at
the Le Web conference in early December.

On Mon, Jan 25, 2010 at 9:25 AM, Jaanus  wrote:

> I am experimenting with some clients. In the last few days, I'm
> seeing:
>
> X-Ratelimit-Limit: 350
>
> AFAIK this hasn't been announced/acknowledged anywhere, so not sure
> exactly what's going on, just wanted to shout out here. I am only
> using OAuth and "normal" REST. I don't know if/how this affects Basic
> Auth and search API-s.
>



-- 
Marcel Molina
Twitter Platform Team
http://twitter.com/noradio

[twitter-dev] rate limit: plz reply as soon as possible : urgent

[viv]

I am frequently hitting rate limit. i know it happens when you do
more
than 150 search API call in a hour
int a[] =twitter.getFriendsIDs("xyz").getIDs();
int b[][] = new int[a.length][]
for(int i=0;i

Re: [twitter-dev] Rate Limit & New API Features

[John Kalucki]

There are several projects in the pipeline to help with rate limiting
issues.

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.


On Tue, Dec 8, 2009 at 6:24 AM, Nik Fletcher  wrote:

> Hi Twitter API folks,
>
> Over the last few months, there's been some big new features to the
> API to match the Twitter.com feature set. Whilst that's awesome for
> third-party developers and users alike, the rate limit has remained
> the same. Looking back over the documentation, the last increase was
> in June of this year, from 100 requests per 60 minute window to 150
> requests - long before the lists or retweet features became available.
>
> Whilst I'm *fully* aware that we (as a developer community) can
> minimise the number of calls to the API, with new features being added
> - and the related query-chaining that may be needed to provide folks
> with an experience such as they're used to on the Twitter Web site
> with the bells and whistles - are there any plans to increase the rate
> limit for applications?
>
> I should just add: this is in no way a whiny post at the rate limiting
> that's currently in effect. We're not hearing of Socialite hitting the
> rate limit a great deal (as we're deliberately refreshing Lists every
> third refresh to preserve API calls) - I'm just posting to see what
> the Twitter API team's thoughts are :)
>
> Cheers,
>
> Nik
>
> ---
> Nik Fletcher
> Support / QA Manager
> Realmac Software
>

[twitter-dev] Rate Limit & New API Features

[Nik Fletcher]

Hi Twitter API folks,

Over the last few months, there's been some big new features to the
API to match the Twitter.com feature set. Whilst that's awesome for
third-party developers and users alike, the rate limit has remained
the same. Looking back over the documentation, the last increase was
in June of this year, from 100 requests per 60 minute window to 150
requests - long before the lists or retweet features became available.

Whilst I'm *fully* aware that we (as a developer community) can
minimise the number of calls to the API, with new features being added
- and the related query-chaining that may be needed to provide folks
with an experience such as they're used to on the Twitter Web site
with the bells and whistles - are there any plans to increase the rate
limit for applications?

I should just add: this is in no way a whiny post at the rate limiting
that's currently in effect. We're not hearing of Socialite hitting the
rate limit a great deal (as we're deliberately refreshing Lists every
third refresh to preserve API calls) - I'm just posting to see what
the Twitter API team's thoughts are :)

Cheers,

Nik

---
Nik Fletcher
Support / QA Manager
Realmac Software

Re: [twitter-dev] Rate Limit & Whitelisting Change

[Michael Steuer]

Youre seeing rate limit errors for unauthenticated calls from that ip  
address, or when you authenticated calls for a user that's not  
whitelisted?




On Nov 23, 2009, at 10:30 AM, Stas  wrote:


We have received whitelisting approval from Twitter, but seems it is
applicable to the @name and the IP.
Given that we still get "rate limit" errors, should we just whitelist
the IP?

If so, what is the process of changing the whitelisting options?

Thank you,
-Stas

[twitter-dev] Rate Limit & Whitelisting Change

[Stas]

We have received whitelisting approval from Twitter, but seems it is
applicable to the @name and the IP.
Given that we still get "rate limit" errors, should we just whitelist
the IP?

If so, what is the process of changing the whitelisting options?

Thank you,
-Stas

[twitter-dev] Rate limit for Yahoo pipe

[Abava]

I'am trying to get data from Twitter via Yahoo pipe. Is there any rate
limit for pipes? As far I understand IP in requests are from Yahoo

[twitter-dev] Rate Limit: Two accounts on single machine or the limit for the IP of machine with those accounts? - thats the question!

[Atul Kulkarni]

Hi All,

I have a small question,

if I run two different scripts authorized with two different accounts
(whitelisted) from the same machine (IP whitelisted), will the rate limit of
the machine which i thnk will be reached be counted (given that I am using
same machine for the both the requests) or the rate limit for the two
different accounts with authorization be used? I don't want them to fight
against eachother for rate, hence the question.

-- 
Regards,
Atul Kulkarni
www.d.umn.edu/~kulka053

[twitter-dev] rate limit error on status/show only

[twittme_mobi]

Hi All,

I am hitting the following url:
/statuses/show/4843243649.xml

And i get:
Rate limit exceeded. Clients may not make more than 150 requests per
hour.

Note that before and after that i can hit any other url without
problems with the same user - so i am
logged in my application and everything works fine until i hit this
url, after i get the error i could continue
with other functionality with no problemsstrange huh?

Thanks.

[twitter-dev] Rate limit response code(s)

[jmathai]

Why are 400, 403 and 503 valid response codes to signify that a call
is being rate limited?  Was there a dart board involved?

   * 400 Bad Request: The request was invalid.  An accompanying error
message will explain why. This is the status code will be returned
during rate limiting.
   * 403 Forbidden: The request is understood, but it has been
refused.  An accompanying error message will explain why. This code is
used when requests are being denied due to update limits.
   * 503 Service Unavailable: The Twitter servers are up, but
overloaded with requests. Try again later. The search and trend
methods use this to indicate when you are being rate limited.

http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors

[twitter-dev] Rate Limit Weirdness?

[Waldron Faulkner]

Strange events w/ Rate Limit requests.

I'm calling the API from my whitelisted IP and getting results that
are all over the map. It's almost as if Twitter is load-balancing my
requests to two different environments, each of which is keeping its
own count of my rate limits. So my app chugs along happily thinking it
has plenty of limits and shouldn't need to check for a while, and then
wham, I'm getting 404's and Rate Limit exceptions.

Check this output from one of my apps:

Rate lims for acct: 7727
Rate lims for acct: 2002
2009-09-03 02:12:04 AM: Processed 1000 tasks (∞ / min)
Rate lims for acct: 1136
2009-09-03 02:12:25 AM: Processed 2000 tasks (∞ / min)
Rate lims for acct: 7052
2009-09-03 02:12:46 AM: Processed 3000 tasks (3000 / min)

Notice how the rate lim requests bounce from the 7K to the 1K range

Then, a few seconds later, I get a ton of 404, and finally an over-the-
rate-lims response.

This only happens from my whitelisted IP. I'm running the same app
from home (account whitelisted but not the ip) and it runs without
this problem.

What's up??

[twitter-dev] Rate Limit Change?

[Waldron Faulkner]

Getting same response to my rate limit requests (http://twitter.com/
account/rate_limit_status.format), for both Account and IP.

I think I missed something. I used to have two different, independent
numbers for my account and IP rate limits (including different reset
times). That is, I would have 20K account calls, plus 20K IP calls,
each hour.

This changed recently (within past 2 weeks?). Now, both numbers are
reduced by 1 hit, whether I hit an account or api limited. My request
returns same result, whether I'm logged in or not... although the XML
isn't in the same order, so it's definitely still two different apps.

Did I miss something? Is this a policy change, because the wiki
doesn't reflect it.

Thanks,

- Waldron

[twitter-dev] Rate limit question (again/followup) 20k user or ip?

[Bob Fishel]

Since we have a lot of devs monitoring this now I'd like to bring back
the discussion that we were having before this whole mess started.

Is the intention of Twitter to allow (for whitelisted IP's) 20k
requests per hour per USER or 20k requests per hour per IP.

I don't want to seem to be beating a dead horse and Chad has confirmed
this but it still seems like there's quite a bit on contention.

Thanks

-Bob

[twitter-dev] rate limit status API not working!

[echeyde]

hi, since yesterday when the DOS attack happened, this
http://twitter.com/account/rate_limit_status.json API call  returns an
empty response. This stops my site, that is Twitter IP white listed,
since I use this API for self-throttling.


Is there any resolution planned?


Thank
Echeyde

[twitter-dev] rate limit has reverted from 20000 to 150 for my IPs...

[chinaski007]

UGH!  All of my whitelisted IPs have reverted from 20k/hour limit to a
150/hour limit.

Anyone else??

What the heck?!

[twitter-dev] Rate Limit reporting

[Justin]

I feel a bit silly asking this in the time of OAuth - but I'm not
quite there yet...

So how to return the rate limit for a given user?
Looking at the api documentation I presume you need to authenticate
(log in)

The obvious way to do this is via GET with:
http://username:passw...@twitter.com/account/rate_limit_status.xml
I've also tried base64'ing the username:password as suggested here:
http://en.wikipedia.org/wiki/Basic_access_authentication
http://base64(User:Pass)@twitter.com/account/rate_limit_status.xml

However, every time I try I'm returned with the rate limit for the IP
address and not the user.

I know I'm missing something (a few sandwiches from the picnic
probably)  - could someone enlighten me?

Many thanks

[twitter-dev] Rate Limit on Unfollows?

[Jesse Stay]

Is it true that there is now a rate limit on number of unfollows per day?
One of my users said that your support rep is telling them they risk
suspension if they go over 500 unfollows a day.  Might be worth an
announcement if that is the case so we can share that with our users...

If I can suggest against this, or perhaps another solution (or an exception
for certain cases), one of the services I offer is the ability to remove all
of your friends at once.  This is something Loic Lemeur and others have
done, and I think some times some people just want to start over.  With a
500/day limit it may be near impossible for some people to remove all their
friends at once.

A better solution to kill spam, as I mentioned before, is to remove the
follow limits and ratios on people that are already following an individual
before that individual follows them, and increase the limits (I think 200
per day would be fine) for people trying to follow those that aren't already
following them.  I would leave out the unfollow limits due to the reasons
specified, and they would be unnecessary with the limit rules I mentioned.

Jesse

[twitter-dev] rate limit problem

[ballan]

Hey all,

I am re-creating a feed that that will be displayed in a custom
widget. However, the rate limit is being reached almost right away,
even though this is currently in development, and only a handful of
people would be looking at this.

I have implemented the following steps to avoid this:

1. Check the account/rate_limit_status
2. If remaining hits are less then 5, return true, otherwise false
(for limitExceeded)
3. If false, proceed to show feed
4. If true, show custom error feed showing rate limit error (no calls
to the API are made)
5. Caching is on both page level and the feed

Caching aside, remaining-hits should never be less then 5. However, it
continues to drop, at about a rate of 4 per refresh. Calls to account/
rate_limit_status are supposedly unlimited, but it seems to be the
only thing causing the rate-limit to drop. Could this be a bug?

Thanks!

[twitter-dev] Rate Limit Issue?

[DuBose Cole]

I was wondering if anyone else has encountered problems with the rate
limit while whitelisted. I recieved whitelisting authorization for my
app development, but my rate still shows up as 100 per hour. After
running into this problem and reading about some database issues a
while back, I applied again, got accepted and have encountered the
same issue. I'm making authenticated calls in my code using my white
listed id (@dubosecole). I'm using basic authorization and not OAuth,
are there any other steps anyone can suggest?

I'm using it for network visualization/message transmission analysis
rates in a relatively simple vba package and this rate limit issue is
seriously slowing down development.

Any help anyone can provide would be appreciated.

Thanks,

DuBose

[twitter-dev] rate-limit and whitelisting

[Lien Tran]

Apologies if this question seems like it's obvious or has already been
answered but I read through several posts on this topic as well as the
API documentation and I'm still confused.

The documentation states: "The default rate limit for calls to the
REST API is 100 requests per hour. The REST API does account- and IP-
based rate limiting. Authenticated API calls are charged to the
authenticating user's limit while unauthenticated API calls are
deducted from the calling IP address' allotment."

QUESTION 1: Does this mean that if my user is signed up with multiple
Twitter applications, then the total number of requests that those
applications can make on behalf of my user is 100?  That is, the 100
rate limit is split across all the applications?

The documentation also states "we offer whitelisting which will raise
an accout or IP address' rate limit to 2 requests per hour".

QUESTION 2: If I have a application server with several hundred
thousand users, and I have my IP address whitelisted, does this mean I
can make only 2 requests per hour for all users that are
registered with my server?  If so, then I'm not sure how whitelisting
will help me here.  Am I better off with just relying on the account
rate limit of 100?


Thanks,
Lien

[twitter-dev] Rate limit status's "remaining_hits" element scope

[Dimebrain]

I just realized I don't know whether the remaining_hits element
returned for /account/rate_limit_status is a static number from the
beginning of the current hour, or if it is the remaining hits on a
rolling sixty minute cycle. Does anyone know?

[twitter-dev] Rate Limit hit, cannot follow using PHP or Curl. but only when Getting, not Posting

[Marco Kotrotsos (incredicorp.com)]

Hi everyone.

I have requested whitelisting 2 times, and got response twice, but
still I see in my headers that i'm limited to 100 requests...Anyway,
heres the strange part

when i'm doing

curl -u xuser:xpass http://twitter.com/friendships/create/ndotnanda.xml

I am getting a error saying "rate limit exceeded"
when checking my header I see, X-RateLimit Limit 100 and Remaining: 0

Ok, so maybe it didn't propagate through the servers yet, no
problem..the curl was wrong anyways I should have POSTed

so I do

curl -u xuser:xpass http://twitter.com/friendships/create/ndotnanda.xml
-d ""

Now, it goes OK. I am now following that user. But, what about the
rate limit I got when GET'ing?

Anyone have any idea? The rate limit (HTTP error 400) thing, could
that as well be a bad request and not rate limit perse? But what about
the headers then?

Hope someone can shed some light on this, thank you very much
kind regards,
Marco Kotrotsos

[twitter-dev] Rate limit status with OAuth

[Joshua Perry]

Is anyone else having issues getting the rate limit stats when using 
OAuth?  It seems to just be returning 100 remaining and an hour until 
reset at every request.

Josh

[twitter-dev] Rate limit for tweets

[Kelly Jones]

I know /rate_limit_status.json tells me how many API calls I have
left, but what tells me how many tweets I have left?

I once had lots of API calls left, but when I tweeted "foo" (via the API),
the tweet didn't go through and I kept getting back data on my last
successful tweet (ie, the one immediately before "foo").

-- 
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.

[twitter-dev] Rate limit on querying RSS. Per user or all together?

[Kenefick]

Is the 100 request rate limit per IP address 100 per each user or 100
queries per address , even if it's 100 different users ?

[twitter-dev] Rate limit with since_id parameter

[Josh Perry]

I wonder if it might be an acceptable compromise for twitter to not
count certain requests against an authenticated user.  These request
should theoretically not be much if any more expensive in CPU or
bandwidth than the rate limit check itself.

I propose that any request with a since_id that does not return any
results not apply to the 100 request/hour limit.

A request like this would result in a very quick indexed primary key
lookup in the datasource being used to store the data.  Also, in the
case that no new items existed there would be no data returned to use
datasource server bandwidth and it would not use any more bandwidth on
the webserver than a 400 rate limit exceeded message.

Perhaps these request should still be rate limited, but with higher
caps.  This would allow developers to provide nearly real-time updates
in our clients without necessitating something extreme like
implementing some Firehose based distribution system.

Between trying to keep friend-statuses, user-statuses, @replies,
direct messages sent, direct messages received, the following list,
and the followers list all somewhat in sync puts a pretty heavy burden
on the 100 request/hour limit.  Especially considering the case where
someone has a multiple clients on a laptop, work desktop, home
desktop, and/or iPhone puts developers in a bit of a predicament.

Josh

[twitter-dev] Rate limit exceeded for whitelisted app after inactivity.

[CrewXp]

Hey, we requested to be whitelisted about a month or two ago and it
seemed like everything worked fine after we were added, but school
ended for the semester here at our university, so the program's use
stopped. School is back in session, so we have faculty using the
program again, and are starting to see the Rate limit exceeded for our
app.

Is there a period where we are removed from the whitelist if the
application isn't in use for a while?