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 <dpr...@gmail.com> 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" <james.ren...@gmail.com> 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 <dpr...@gmail.com> wrote:
>
> > > On Aug 10, 11:02 pm, "jim.renkel" <james.ren...@gmail.com> 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

Reply via email to