Hi,
Before basic authentication was deprecated, I used to query rate_limit
(http://api.twitter.com//1/account/rate_limit_status.xml) from the
command line directly with curl or wget .
How can I do this now?
I do have OAuth working from within my app, but I need a quick way to
check my limit.
Hi ,
I have implemented OAuth rate limit status which calls the
http://api.twitter.com/1/account/rate_limit_status.xml and it always
returns 350 as remaining hits. Even though I make many calls it
returns remaining hits as 350. Why it is not reducing.
Please help.
Thanks,
Rejeev
--
To
My program sends is using rate_limit_status.xml to get the number of
remaining hits until the account limit is exceeded. My problem is that
it always seems to return the same value: 150. Even once I have
already hit the limit the service continues to show 150 hits left. I
am thinking that it is
As far as i know thats correct.
blogtoilet.com
On Sep 26, 7:36 am, Patrick pkollit...@gmail.com wrote:
Hi there,
this might be obvious to everybody working longer with the API but to
me its a bit unclear:
If I call rate_limit_status from a script that I registered
athttp://twitter.com
Hi there,
this might be obvious to everybody working longer with the API but to
me its a bit unclear:
If I call rate_limit_status from a script that I registered at
http://twitter.com/oauth and using OAuth I get 2 API calls per
hour as as base for my requests.
If I call rate_limit_status
I think pretty much everyone is getting a lot of 503's right now.
Interestingly I'm not seeing many from the site, only the API right
now.
On Aug 24, 9:40 pm, Joseph Cheek jos...@cheek.com wrote:
Am I safe in assuming that if account/rate_limit_status is returning
503, it means
I always heard IP whitelisting was taking precedence to account rate
limits.
What you're describing sounds like the normal behaviour to me.
Arnaud.
On Jul 10, 6:06 am, alan_b ala...@gmail.com wrote:
I'm making a account/rate_limit_status call using OAuth authenticated
with a non-whitelisted
I'm making a account/rate_limit_status call using OAuth authenticated
with a non-whitelisted user, and the server that making the call is
whitelisted. The call always returned the IP-based rate limit
information, not the authenticated user info.
Please try it here with a non-whitelisted account
Hi there,
The most common cause of X-RateLimit-Remaining not matching a
call to rate_limit_status is that you're not authenticated when
calling rate_limit_status but you are when making the call with the
different header. This is usually caused by libraries that require a
401
.
request.Headers[Authorization] = your base64 encoded
username:password here;
On Apr 30, 12:17 pm, Matt Sanford m...@twitter.com wrote:
Hi there,
The most common cause of X-RateLimit-Remaining not matching a
call to rate_limit_status is that you're not authenticated when
calling
Hi.
Is it only I that such a phenomenon occurs though remaining-hits of
returning information seems not to be correct, and to differ from
information that returns by the X-RateLimit-Remaining header about API
of rate-limit-status? With this, I am embarrassed because it consumes
API though there
. jeremy.d.mul...@gmail.com wrote:
I must be doing something wrong. If I call rate_limit_status with
CURL, I can see 2 different counts, depending on if I pass my
credentials or not. If I do the same thing from a .NET application, I
always get the non-authenticated (IP address limit) results.
I know
I made an issue for this, when authenticated via OAuth requests to
rate_limit_status seems to return the IP specific rate-limit status and
not the users.
http://code.google.com/p/twitter-api/issues/detail?id=376
Please star it if you are using OAuth and you show or use the rate-limit.
Cool, thanks James.
I must be doing something wrong. If I call rate_limit_status with
CURL, I can see 2 different counts, depending on if I pass my
credentials or not. If I do the same thing from a .NET application, I
always get the non-authenticated (IP address limit) results.
I know setting the WebClient
:
This doesn't seem limited to rate_limit_status. I've just tried using
the status replies method and got a (400) Bad Request. at 18:55 and my
reset time is now bumped up to 2008-12-18T19:55:23+00:00.
On Dec 18, 6:48 pm, rhysmeister therhysmeis...@hotmail.com wrote:
Cool, thanks guys
, rhysmeister therhysmeis...@hotmail.com
wrote:
This doesn't seem limited to rate_limit_status. I've just tried using
the status replies method and got a (400) Bad Request. at 18:55 and my
reset time is now bumped up to 2008-12-18T19:55:23+00:00.
On Dec 18, 6:48 pm, rhysmeister
limiting code. It'll
be exposed anywhere rate limiting is applied.
On Thu, Dec 18, 2008 at 11:05, rhysmeister therhysmeis...@hotmail.com
wrote:
This doesn't seem limited to rate_limit_status. I've just tried using
the status replies method and got a (400) Bad Request. at 18:55 and my
HI,
I've recently noticed that calls to the rate_limit_status seem to
extend my reset time by exactly one hour after I have hit the 100
request limit. For example if I hit my 100 limit at 4:00 PM then the
reset time is 5:00PM. If I check this at 4:45PM it then states the
reset time is 5:45PM
On Dec 18, 10:53 am, rhysmeister therhysmeis...@hotmail.com wrote:
HI,
I've recently noticed that calls to the rate_limit_status seem to
extend my reset time by exactly one hour after I have hit the 100
request limit. For example if I hit my 100 limit at 4:00 PM then the
reset time is 5
, rhysmeister therhysmeis...@hotmail.com wrote:
HI,
I've recently noticed that calls to the rate_limit_status seem to
extend my reset time by exactly one hour after I have hit the 100
request limit. For example if I hit my 100 limit at 4:00 PM then the
reset time is 5:00PM. If I check this at 4:45PM
On Dec 18, 11:07 am, Ed Finkler funkat...@gmail.com wrote:
The web site does not affect API limits. Your account may have another
issue if it's been blocked for this long.
--
That's what I was afraid of. I've been tracking it over here;
Yes, but why keep incrementing this time when the rate_limit_status
has been called?
On Dec 18, 4:07 pm, Ed Finkler funkat...@gmail.com wrote:
I believe the reset time indicates when your block will be lifted, so
having it be 1 hour after you hit the limit seems sensible.
--
Ed Finklerhttp
Definitely something funny going on.
Around 16:30 this afternoon rate_limit_status was reporting that my
reset time was 17:15. When querying this at 17:26 the reset time was
reported as 2008-12-18T18:26:04+00:00.
On Dec 18, 4:07 pm, Ed Finkler funkat...@gmail.com wrote:
I believe the reset
something funny going on.
Around 16:30 this afternoon rate_limit_status was reporting that my
reset time was 17:15. When querying this at 17:26 the reset time was
reported as 2008-12-18T18:26:04+00:00.
On Dec 18, 4:07 pm, Ed Finkler funkat...@gmail.com wrote:
I believe the reset time indicates when
25 matches
Mail list logo
