Please note: Bumping is highly discouraged. Bumping after 122 minutes is *really* highly discouraged. -Chad
On Fri, Oct 9, 2009 at 7:10 PM, Charles <[email protected]> wrote: > > Bump > > On Oct 9, 4:08 pm, Charles <[email protected]> wrote: >> I recently received email that confirmed my whitelisting status. I >> have several IPs whitelisted, as well as the account. From a shell on >> one of the whitelisted servers, I make a couple requests and then try: >> >> curlhttp://twitter.com/account/rate_limit_status.xml >> >> <?xml version="1.0" encoding="UTF-8"?> >> <hash> >> <hourly-limit type="integer">150</hourly-limit> >> <reset-time-in-seconds type="integer">1255123230</reset-time-in- >> seconds> >> <reset-time type="datetime">2009-10-09T21:20:30+00:00</reset-time> >> <remaining-hits type="integer">147</remaining-hits> >> </hash> >> >> If, on the other hand, I try: >> >> curl -u username:passwordhttp://twitter.com/account/rate_limit_status.xml >> >> <hash> >> <remaining-hits type="integer">19999</remaining-hits> >> <reset-time type="datetime">2009-10-09T21:57:09+00:00</reset-time> >> <hourly-limit type="integer">20000</hourly-limit> >> <reset-time-in-seconds type="integer">1255125429</reset-time-in- >> seconds> >> </hash> >> >> I was under the impression I did not have to auth if I was making >> calls from the API? Also: if I use my application's oauth >> credentials to generate an oauth_request and use the oauth URL, I am >> still getting the lower rate limit. Is this normal behavior? >
