Hi Josh, Thank you for getting back to me. If I was to provide a widget myself and make API calls, I would certainly be above the 20000 calls per hour (5.5tps). I would therefore have to implement a caching layer.
Added complexity comes from the fact that there are several instances of the web site, for example in North America and Europe. This makes it dificult to determine the number of API calls made during any given hour. The twitter widget looks like it provides a nice solution as no authenticated api calls are introduced, and requests come from the end user's browser. I want to be a good citizen, so it would be good to be able to eliminate the widget from my investigation or use it with confidence. Thank you Jason King On Jan 13, 2:11 pm, joshnesbitt <[email protected]> wrote: > Hi Jason, > > As far as im aware the widget does not actually get rate limited, i'm > sure i read somewhere that this was not included in the normal rate > limit (but don't quote me on that). > > The best way is to use an effecting caching technique. If you cache > the content every x minutes you should be covered if a certain page > was to get hammered. > > What is the context of your application and have you considered white > listing if you really need to be using the API for every request? > > Regards, > Josh > > On Jan 13, 9:40 am, Jason King <[email protected]> wrote: > > > Hi, > > > I am investigating options for showing a twitter widget on a website. > > I am considering using the Twitter provided Profile Widget (http:// > > twitter.com/goodies/widget_profile). > > > I wanted to clarify what rate limiting policy (if any) applies to this > > widget? > > > From reading the documentation, the widget does not make authenticated > > calls, and therefore a client IP limit would be applied. As the call > > to twitter is made via javascript from the client browser, the limit > > would then be placed on the client IP (150 calls per hour). > > > The widget will show for various twitter users who register with my > > site (i.e. they say what their twitter name is and on their public > > page, the twitter widget will show their last couple of tweets). The > > render rate will be much higher than 150 per hour in total, but for an > > individual browser should be much less. > > > Finally, what happens when a large number of clients (browsers) are > > behind a proxy such as at a university or large company? > > > Thank you > > Jason
