rate_limit_status

[rhysmeister]

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. It seems to happen for a couple of times before
stopping. Is this known behavior?

Thanks,

Rhys

[Mike]

I've had similar troubles. I haven't been able to log in via API for
a few days, but was unaware that there may be a connection to checking
my rate_limit_status. I was under the impression that using a web
browser did not affect my reset time.

http://twitter.com/mike_white

The no API thing is really bumming me out.

[Ed Finkler]

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 Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron

[Ed Finkler]

The web site does not affect API limits. Your account may have another
issue if it's been blocked for this long.

--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron

[Mike]

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;

http://getsatisfaction.com/twitter/topics/apis_over_used_so_no_twirl_paused_for_5_min_but_it_has_been_paused_for_3_days?utm_medium=widget&utm_source=widget_twitter

But with no resolution so far.

[rhysmeister]

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://funkatron.com

> AIM: funka7ron
> ICQ: 3922133
> Skype: funka7ron
>
> On Thu, Dec 18, 2008 at 10:53 AM, rhysmeister
>

[rhysmeister]

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 time indicates when your block will be lifted, so
> having it be 1 hour after you hit the limit seems sensible.
>
> --

> Ed Finklerhttp://funkatron.com

> AIM: funka7ron
> ICQ: 3922133
> Skype: funka7ron
>
> On Thu, Dec 18, 2008 at 10:53 AM, rhysmeister
>

[Ed Finkler]

Oh, I see now. So it changes each time you *check*, not just each time
you hit 100. Yes, that doesn't sound right.

--
Ed Finkler

http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron

[Alex Payne]

Yeah, I think we've got a bug here. Hold tight, I'll look into it today.

--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

[rhysmeister]

Cool, thanks guys.

[rhysmeister]

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.

[Alex Payne]

Yes, I think it's a bug in the underlying rate limiting code. It'll
be exposed anywhere rate limiting is applied.

[Mike]

Alex, this seems to have been resolved for me about 30 minutes ago.
It still wasn't working when I first tried this morning, but at one
point i refreshed the m.twitter.com page on my phone and it returned
the page in HTML code. After that, the API limit was reset. I don't
know if that's related but I thought it was interesting...

Mike

[Mike]

Oh, and also when the m.twitter.com page did load again, it returned
the full site instead of the mobile one. Even though the "m" was
still in the address bar and i refreshed a couple times.

Thanks

[Mike]

oops. its broken again :(

-
<hash>
<reset-time type="datetime">2008-12-19T17:31:40+00:00</reset-time>
<remaining-hits type="integer">0</remaining-hits>
<hourly-limit type="integer">100</hourly-limit>
<reset-time-in-seconds type="integer">1229707900</reset-time-in-
seconds>
</hash>

And i only accessed through API once about 2 hours ago.

[Alex Payne]

Thanks for the reports.