[twitter-dev] Easy there, Turbo. Too many requests recently. Enhance your calm. - User streams limit?

2010-11-19 Thread ben
Hi, we're working on a Twitter client, using user streams API. Since
yesterday I found out that for certain accounts, whenever we try to
connect using user streams, we get the following error: Easy there,
Turbo. Too many requests recently. Enhance your calm.. And ever since
this happened, the account itself seems to have been banned from
connecting to user streams--even when I open up Tweetdeck, it doesn't
deliver user streams anymore, but instead seems to poll the server
once in a while using REST. We haven't done anything abnormal. Has
anyone experienced the same problem? And could you enlighten me on how
to go about solving this problem? Thanks!

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


Re: [twitter-dev] Easy there, Turbo. Too many requests recently. Enhance your calm. - User streams limit?

2010-11-19 Thread Taylor Singletary
Hi Ben,

Can you tell us a bit more about how you were using user streams?

Are you opening up multiple simultaneous connections to User Streams from
the same IP and/or same user account? If so, how many? What client library
are you using? Are you doing a lot of disconnecting and reconnecting
in succession?

Thanks,
Taylor


On Fri, Nov 19, 2010 at 10:38 AM, ben ben.sad...@gmail.com wrote:

 Hi, we're working on a Twitter client, using user streams API. Since
 yesterday I found out that for certain accounts, whenever we try to
 connect using user streams, we get the following error: Easy there,
 Turbo. Too many requests recently. Enhance your calm.. And ever since
 this happened, the account itself seems to have been banned from
 connecting to user streams--even when I open up Tweetdeck, it doesn't
 deliver user streams anymore, but instead seems to poll the server
 once in a while using REST. We haven't done anything abnormal. Has
 anyone experienced the same problem? And could you enlighten me on how
 to go about solving this problem? Thanks!

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk