Orian, You should definitely plan on working within 350/hr for the forseeable future. FWIW, we have watched #newtwitter usage and an average session uses between 80-120 rq/hr.
Hope that helps clarify. Best, Ryan -- Ryan Sarver @rsarver <http://twitter.com/rsarver> On Thu, Feb 10, 2011 at 6:17 PM, Orian Marx (@orian) <or...@orianmarx.com>wrote: > Ryan et al, thanks for the update on this. Shall we also take this to mean > 350 is the definitive cap on rate limits for the foreseeable future? This > certainly seems to be implied but since the spirit of this update seems to > be to remove ambiguity, I think a clear statement that Twitter is no longer > planning on gradually increasing rate limits, as has been stated many times > in the past, would be appreciated. > > -- > 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
