Thanks for your answer. One more: is the 250 MD limit increased if the application is whitelisted? Or does the whitelist concernt the rates only? Thanks
On Wed, May 12, 2010 at 5:15 PM, Taylor Singletary < taylorsinglet...@twitter.com> wrote: > Rate limits and limits on particular actions are different. We could do > better in providing a X-FeatureRateLimit header on tweets and DMs and the > such that have their own issuance limit -- but I can imagine potential > performance issues with that. > > Rate limits provide a ceiling on the amount of API calls you can make. > Their main purpose is to keep the entire platform running smoothly and to > not allow any one application to spoil the resource pool for its peers. > > Twitter, aside from the API itself, has limits on how many status updates > and DMs can be sent -- the API just respects the rules of Twitter here. If > you're concerned you might be hitting the upper limit, for now the best > thing to do would be to implement a counter in your application and queue > updates when your counter is full. > > A user may issue 1000 tweets per day and 250 DMs. > > Taylor Singletary > Developer Advocate, Twitter > http://twitter.com/episod > > > > On Wed, May 12, 2010 at 4:47 AM, alex <alex.urdea.fi...@gmail.com> wrote: > >> I'm confused: >> - here it says that there's a limit on direct messages >> >> URL: http://help.twitter.com/entries/15364 >> >> In the documentation page for this method you have : "API rate limited >> false": >> >> URL: >> http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-direct_messages new >> >> Here it says that "API methods that use HTTP POST to submit data to >> Twitter, such as statuses/update do not affect rate limits". I guess >> that this is a POST method that submits data and is not subject to >> limits? >> >> URL: http://apiwiki.twitter.com/Rate-limiting >> >> Which one is true? >> >> Thank you! >> > >
