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?


On Jan 13, 9:40 am, Jason King <king_j...@hotmail.com> 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

Reply via email to