Oops, my bad, I have a .curlrc in place that authenticate it. Unauthenticated it doesn't seem to be counting down. Alex: possible bug?
-Stuart 2009/2/8 Stuart <[email protected]>: > Here's a crazy thought... try it!! > > Here's what the rate_limit_status shows unauthenticated from my dev > server just now... > > stu...@dev:~$ curl http://twitter.com/account/rate_limit_status.xml > <?xml version="1.0" encoding="UTF-8"?> > <hash> > <hourly-limit type="integer">20000</hourly-limit> > <reset-time type="datetime">2009-02-08T11:03:45+00:00</reset-time> > <reset-time-in-seconds type="integer">1234091025</reset-time-in-seconds> > <remaining-hits type="integer">19425</remaining-hits> > </hash> > > -Stuart > > 2009/2/8 Jesse Stay <[email protected]>: >> I'm sorry for wasting your time, Abraham. I'll be more specific next time. >> That still doesn't answer my question though as to whether there is a >> method to get my used-up requests within the new 20k/hour rate limit. >> Alex? >> >> On Sun, Feb 8, 2009 at 1:11 AM, Abraham Williams <[email protected]> wrote: >>> >>> I've not tested in the 20k range but it counts into the 2k range. So you >>> should be fine. >>> >>> Also for future reference if you are looking for answer A don't ask >>> question B. Ask question A. The bit bit about working in the 20k range was a >>> key part of the original question and it was not included. >>> >>> On Sun, Feb 8, 2009 at 01:17, Jesse Stay <[email protected]> wrote: >>>> >>>> Does that apply to the 20,000 requests per hour limit? I thought that >>>> was more geared to non-whitelisted users. >>>> Jesse >>>> >>>> >>>> On Sat, Feb 7, 2009 at 11:44 PM, Abraham Williams <[email protected]> >>>> wrote: >>>>> >>>>> http://apiwiki.twitter.com/REST+API+Documentation#ratelimitstatus >>>>> >>>>> On Sun, Feb 8, 2009 at 00:23, Jesse Stay <[email protected]> wrote: >>>>>> >>>>>> Is there a way Twitter could provide the number of requests Twitter has >>>>>> detected an app has used in an hour in various requests? This will make >>>>>> it >>>>>> easier to determine how close we are to hitting that limit and throttle >>>>>> down >>>>>> if necessary. >>>>>> Thanks, >>>>>> Jesse >>>>> >>>>> >>>>> -- >>>>> | Abraham Williams | http://the.hackerconundrum.com >>>>> | Web608 | Community Evangelist | http://web608.org >>>>> | This email is: [] blogable [x] ask first [] private >>>> >>> >>> >>> >>> -- >>> | Abraham Williams | http://the.hackerconundrum.com >>> | Web608 | Community Evangelist | http://web608.org >>> | This email is: [] blogable [x] ask first [] private >> >> > > -- > http://stut.net/ > -- http://stut.net/
