Twitter had some issues with incorrect rate limits over the past few days [1].
I believe they've resolved those issues now, so if you're still having the issue you've described, visit the connections page [2] to see if any app using OAuth may be accessing your account. If not, change your password [3], which would prevent any Basic Auth apps (that you've previously given your credentials to) from accessing your account and using up some of your requests. 1. http://status.twitter.com/post/777268689/incorrect-rate-limiting and http://status.twitter.com/post/781763549/investigating-rate-limit-exceeded-issues 2. https://twitter.com/account/connections 3. https://twitter.com/account/password On Jul 7, 11:59 am, founder <foun...@pege.org> wrote: > Just started to integrate twitter into my own CMS written in Perl. > > I use a very old Perl version, because only this old version is > compatible to use MSIE as GUI. > > To use the API, Perl engages a download program by a batch file. > > Just right now, I only test with > thehttp://api.twitter.com/1/account/rate_limit_status.xml > > No other call is used. But from start to start, there are less hits > remaining in the rate limit, > Up to 10 less when I wait some minutes. > > I have no idea what consumes my rate limit > > I already closed Twitter in all browsers, but still the same effect. > > Any idea what could use up my rate limit?
