Full HTTP request/response output would help us track this down. On Wed, Apr 8, 2009 at 03:20, Adrian <[email protected]> wrote: > > Hi, I'm been developing a client-side app that uses basic HTTP > Authentication into twitter.com. > > The problem is that when logging-in with a whitelisted account, the > 20,000 quota is correctly reflected in the remaining hits as displayed > on-site whilst using IE and FF, but in Chrome and Opera, the quota is > back to 100 when logging in with the same account. > > You can see here: > http://tr.im/iqLY > > Enter your username and password - immediately at top-right there will > be a number - the remaining hits. > It seems this quota is dependent on twitter detecting a whitelisted > account, which is determined by the browser. > > Furthermore, > http://twitter.com/account/rate_limit_status.json > http://twitter.com/account/rate_limit_status.xml > in the same browser, eg IE will display different results. Former > ~20000, latter 100 > > and across browser, sometimes the results for each are identical, ~100. >
-- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
