I see that other developers are concerned about the future of getting your DM limits increased but I haven't seen a response yet that addresses this. Will there still be a way, on a case by case basis of course where we can request increases for DM limits?
Thanks, Trevor On Fri, Feb 11, 2011 at 1:25 PM, Adam Green <[email protected]> wrote: > Be aware that the streaming API does not deliver everything you are > tracking. In theory it delivers everything up to 1% of the total flow > of tweets. In practice, I find that it delivers about 95% of the > tweets that match your keywords or users. This is fine when sampling, > which is what I generally use it for, but will cause much anguish if > you assume you will get everything sent by people you are following. I > have to admit that I have only found this issue with the streaming > API, but I'm betting that the user streams are based on the same > underlying code. > > My solution to the missing values from the streaming API is to collect > everything I can from streaming, then use the REST API to backfill > data I might not have received. If you run the backfill every hour, > you only have to go back to the last set of good tweets, adding > anything you missed. > > On Fri, Feb 11, 2011 at 1:10 PM, DaveH <[email protected]> wrote: > > 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 > > > > > > -- > Adam Green > Twitter API Consultant and Trainer > http://140dev.com > @140dev > > -- > 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
