I asked the same in the #twitterapi at freenode and they said i must read the terms of service. I did and i found with this:
If you send large numbers of unsolicited @replies or mentions in an attempt to spam a service or link; And If you send large numbers of duplicate @replies or mentions; With the last, they will be "duplicated" but with differents mentions. For example, if 4 people ask for films at Sunday, they will get the same answer. @userasking film1, film2 at location on Sunday. There will be a large number of @replies, but they all will be solicited by the user. So i think there will not problem about creating 4 accounts(@appname1,@appname2 etc etc) to respond to 4.000 users. If i'm wrong, please let me know. Thanks, Jorge. On 31 mayo, 15:50, James Gifford <[email protected]> wrote: > It's a twitter limitation. > > https://support.twitter.com/articles/15364-about-twitter-limits-updat... > > So yes, you have to create 4 accounts to send 4,000 tweets. > > Cheers, > James Giffordhttp://jamesrgifford.com > > > > > > > > On Mon, May 30, 2011 at 7:46 PM, tigreton <[email protected]> wrote: > > Hi, i was searching and can't figure how to update more than 1.000 > > tweets per day. It isn't spam, is for an application that i'm > > developing and it responds. For example: offers, films, restaurants... > > > Must i create for example 4 users to send 4.000 tweets? > > How "big" applications does? > > > Thanks, Jorge. > > > -- > > Twitter developer documentation and resources:https://dev.twitter.com/doc > > API updates via Twitter:https://twitter.com/twitterapi > > Issues/Enhancements > > Tracker:https://code.google.com/p/twitter-api/issues/list > > Change your membership to this > > group:https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
