The same IP-based rate limits that apply on Twitter.com apply with @Anywhere integrations. Your web browser is essentially the client with @Anywhere, not the originating site, so if you're on a shared network that Twitter would see as a single IP address and there's a lot of accessing of @Anywhere content on that IP address, you'll likely run into rate limiting of some kind. We're looking at ways in the short term to make this more flexible without compromising the point of rate limiting.
Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Mon, Apr 19, 2010 at 7:54 PM, Albert Stein <astei...@gmail.com> wrote: > Ok, really need some feedback from Twitter here... > > Some of my customers (and me) are getting the follow buttons - and > then after a few page refreshes, we get the button that says xyz is > not found and then another refresh and we get nothing at all. We are > showing 10-15 follow buttons on a page. > > So are we hitting the api limits? There is no talk on the anywhere > documentation that it uses limits so I am unsure. > > Thanks for any help. > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
