Also, the 'reset-time' is increasing with every request. My reset time below was taken at 7:57 UTC:
<?xml version="1.0" encoding="UTF-8"?> <hash> <remaining-hits type="integer">20000</remaining-hits> <hourly-limit type="integer">20000</hourly-limit> <reset-time-in-seconds type="integer">1249981041</reset-time-in- seconds> <reset-time type="datetime">2009-08-11T08:57:21+00:00</reset-time> </hash> And this one at 7:58 UTC: <?xml version="1.0" encoding="UTF-8"?> <hash> <remaining-hits type="integer">20000</remaining-hits> <reset-time type="datetime">2009-08-11T08:58:30+00:00</reset-time> <hourly-limit type="integer">20000</hourly-limit> <reset-time-in-seconds type="integer">1249981110</reset-time-in- seconds> </hash> On Aug 11, 8:55 am, CaMason <[email protected]> wrote: > FYI, my whitelisting counts have been a bit flaky since the DDoS. > > On most of my whilelisted IPs, I'm sometimes seeing the "remaining" > count decreasing, and sometimes not. In-fact, my logs show it didn't > decrease for a good chunk of yesterday. > > There have probably been some temporary adjustments at Twitter's end, > so I wouldn't assume that the current whitelist results are the norm. > > -Craig > > On Aug 11, 8:23 am, Robert Fishel <[email protected]> wrote: > > > > > While this may be true I think it's a fringe case and not what we're > > trying to get at here (although it could explain conflicting test > > results....) > > > To summarize what we're looking for clarification on: > > (example) > > My server has 1 whitelisted IP and 1000 users. > > It operates for 1 hour. > > Each user makes an equal number of requests. > > > Is the limit 20 requests per user (= 20k per hour per ip) > > or > > Is the limit 20k per user (=20k per hour per user) > > > The only reason I'm kind of harping on this is that for the new app > > I'm developing the latter would save me a lot of heartache and quite a > > bit of money. > > > Cheers, > > > Bob > > > On Tue, Aug 11, 2009 at 1:54 AM, TFT Media<[email protected]> wrote: > > > > I believe sometimes the IP address can be user-based, even for white- > > > listed IPs. E.G., if the user himself has a whitelisted IP. > > > > On Aug 10, 7:57 pm, Dewald Pretorius <[email protected]> wrote: > > >> Jim, > > > >> I don't know exactly what you're looking at and how you get to that > > >> answer. > > > >> My system is making thousands of GET calls per hour, and I can see how > > >> X-RateLimit-Remaining is decrementing regardless of which Twitter user > > >> credentials are used. > > > >> So, on my side I am seeing solid evidence that the rate limit is per > > >> IP address only and not per user. > > > >> Dewald > > > >> On Aug 10, 11:26 pm, "jim.renkel" <[email protected]> wrote: > > > >> > Hmmm! We seem to have conflicting evidence here! > > > >> > I just (again) verified that twxlate.com is getting 20k requests per > > >> > hour per user. > > > >> > How long ago was it that Alex and other API team members made the > > >> > recommendation that you mentioned? Is it possible that twitter changed > > >> > policy since then? > > > >> > Either way, I agree that we now need a very clear affirmation from > > >> > twitter as to the policy. > > > >> > I sure hope I don't have to eat my words! :-) > > > >> > Jim > > > >> > On Aug 10, 9:08 pm, Dewald Pretorius <[email protected]> wrote: > > > >> > > On Aug 10, 11:02 pm, "jim.renkel" <[email protected]> wrote: > > > >> > > > My logic is now: "Ifratelimiting is not peruser, then all users of > > >> > > > anIPaddress will share one pool of20krequests per hour. If a site > > >> > > > has a 1,000 users at one time, then eachuserwill get an average of > > >> > > > 20 requests per hour. This is clearly not enough to do much useful. > > > >> > > Jim, > > > >> > > That is why Alex and other API team members have recommended in the > > >> > > past that you get and use additional white-listedIPaddresses, when > > >> > > 20,000 requests per hour perIPaddress is not sufficient to service > > >> > > youruserbase. > > > >> > > At TweetLater I employ several white-listedIPaddresses to cover the > > >> > > needs of my users. > > > >> > > Dewald
