The direct message API is a bit more basic than that in that it just provides a way act on individual messages and to page through the user's sent & received direct messages without any kind of advanced filtering techniques (aside from since_id and max_id support). Creating an in memory map and authoring your own filtration routines would be your best bet if you were interested in a feature like this.
@episod <http://twitter.com/episod> - Taylor Singletary On Thu, May 12, 2011 at 7:19 AM, galeyte <gaetan...@gmail.com> wrote: > ... > So i guess there's no other way ? > > On May 11, 5:58 pm, galeyte <gaetan...@gmail.com> wrote: > > Hi, > > > > I'm building a qml/js app. > > I'm now getting direct messages and i'm wondering if there's any way > > to get direct messages by sender screen names or id. > > IBy now i'm requesting /dirtect_messages.json and /direct_messages/ > > sent.json and merging the results together to build a tree and i would > > really appriciate another easiest way to do it. > > > > Thanks, > > -- > 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
