Authenticated requests aren't possible using the widgets really (well, not without getting pretty complex and at that point you're building something yourself).
Authenticated means I'm requesting data from Twitter and it knows that I'm @episod as opposed to just an anonymous user calling Twitter. To a certain degree, this is just the way that rate limiting works right now and you'll have to deal with it. Though if you've got some technical interest and a developer, you can find ways to mitigate the issue -- happy to walk through some of those options with you if you like. @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor Singletary On Mon, Jul 11, 2011 at 1:03 PM, twitterwidget <twitterwidget...@gmail.com>wrote: > Thanks Taylor for getting back to me. > > But can you tell me what is the difference between authenticated > request and unauthenticated request? > Is there any other better approach of using this widget or do we have > to just live with it? > > > > On Jul 11, 12:55 pm, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: > > Hi there, > > > > The widgets are rate limited the same as twitter.com and the API: a > single > > IP address is allowed up to 150 unauthenticated requests per hour against > > api.twitter.com and twitter.com. Search widgets are rate limited also by > IP > > address but with different limits. > > > > If you share an IP address with many users, you may exhaust the amount of > > requests your shared IP address can make to Twitter. In that case you > might > > see an empty/slow to update widget. Your end users might see a fully > > functional widget if their own perspectival rate limits have not been > > exhausted. > > > > If you're using a search widget instead, it's good to know that our > search > > index only maps a few days worth of tweets -- if there haven't been > tweets > > recently matching the queries in a search widget, it will also have no > > results to display. > > > > @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor > > Singletary > > > > On Mon, Jul 11, 2011 at 12:20 PM, twitterwidget > > <twitterwidget...@gmail.com>wrote: > > > > > > > > > > > > > > > > > Someone please help. > > > > > On Jul 8, 10:04 am, twitterwidget <twitterwidget...@gmail.com> wrote: > > > > Can someone please help me to understand how rate limiting works for > > > > twitter widget, either the profile or the list widget. I have gone > > > > through the rate limit faq herehttp:// > > > dev.twitter.com/pages/rate_limiting_faq > > > > which talks about authorized and unauthorized requests which is a bit > > > > confusing to me. > > > > > > I want to understand this because the widget goes blank on our site > > > > sometimes, which we don't want it to happen. > > > > > > Can you please help. > > > > > -- > > > Twitter developer documentation and resources: > https://dev.twitter.com/doc > > > API updates via Twitter:https://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >https://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >https://groups.google.com/forum/#!forum/twitter-development-talk > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
