I too am still worried about the DM limits. If I understand the User API correctly. - The user stream means that an unlimited number of DMs can be received as there is no rate limit on receiving (consuming) of data. - The application would send DMs via the REST API and therefore is limited to sending 250 DMs per day.
For my application this is still a problem as my target is social learning and part of that is DMs to send/receive responses to test questions and such--things that need to be private. Conversations between learners are tweeted. So the design changes we need to make are: - Consuming information (Tweets, retweets, and DMs) is done via the user stream API - Sending tweets and DMs is still done by the REST API. It is going to take some time to get my head wrapped around this. Until the announcement yesterday I was not paying attention to the streams as they did not fit all that well with my application. Now I see that it is important to create an application that uses both as the app is both the consumer of users activity (DMs) and originator (DMs and tweets). On Feb 11, 8:31 am, Trevor Dean <[email protected]> wrote: > Thanks Taylor. I posted a question to the group yesterday but it might have > gotten lost amongst all the other posts about not whitelisting anymore. > With our service we rely on sending DM's and we will most likely require to > have more of our clients whitelisted. What is will be the future of DM > limits and going about getting those rates increased? > > Trevor. > > On Fri, Feb 11, 2011 at 11:11 AM, Taylor Singletary < > > > > > > > > [email protected]> wrote: > > Hi Trevor, > > > Write operations in the Twitter API are always done via the REST API. The > > Streaming APIs are for consumption of data. > > > @episod <http://twitter.com/episod> - Taylor Singletary - Twitter > > Developer Advocate > > > On Fri, Feb 11, 2011 at 7:52 AM, Trevor Dean <[email protected]> wrote: > > >> I can't seem to find any documentation that shows how to go about sending > >> a DM using the new user stream api. I have been through all of the > >> documentation on dev.twitter.com. Can someone point me in the right > >> direction? > > >> Thanks, > > >> Trevor > > >> -- > >> 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 -- 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
