Does that mean if @account has a whitelisted app, 5000 messages/day can be sent through that app, but each app user (say @user_of_account) only gets 250/day?
If so, is the 100 DM/hour limit the same for both @account and @user_of_account, or is there a different hourly limit for @account? -Mo On May 12, 9:25 am, Abraham Williams <[email protected]> wrote: > I read Doug's email as any account that is specifically whitelisted has 5k > DM and that DMs are not effected by IP whitelisting. > > Abraham > > > > On Wed, May 12, 2010 at 09:21, Mo <[email protected]> wrote: > > Hi Taylor, > > > This is different than what Doug Williams stated in this post - > >http://bit.ly/cLVv1Q > > > "Whitelisted users have a direct messaging limit of 5K messages per > > day." > > > What I'm still not clear on, though, is how "user" is being defined. > > Is the user the app owner or the someone using the app? Also, is 5K > > DMs a day stated by Doug correct or is it 250 DMs? > > > Apparently Alex and I posted essentially the same request 5 minutes > > apart. Answering to either this message or to my other post would be > > much appreciated. > > > -Mo > >http://www.pay4tweet.com > > > On May 12, 8:39 am, Taylor Singletary <[email protected]> > > wrote: > > > Hi Alex, > > > > Whitelisting only effects API call rate limiting -- so the answer to your > > > question is "no." > > > > T > > > > On Wed, May 12, 2010 at 8:35 AM, alex urdea <[email protected] > > >wrote: > > > > > 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 < > > > > [email protected]> 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 <[email protected]> > > 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! > > -- > Abraham Williams | Developer for hire |http://abrah.am > @abraham |http://projects.abrah.am|http://blog.abrah.am > This email is: [ ] shareable [x] ask first [ ] private.
