[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
+1 to DMs being a stream, and splitting send/received not making much sense, neither globally nor in one contact context. I treat them as sort of a single meta-call in my app, consisting of two sub-calls, and this seems to be general behavior in all apps and also matches user model. J On Apr 23, 1:13 pm, "Orian Marx (@orian)" wrote: > Sure, yeah. But I would argue that DMs make more sense to be viewed by > default as a stream of back and forth messages vs a separate history > of sent and history of received. I would say it makes more sense to > offer it as one endpoint to be split client side rather than two > endpoints to be merged client side. Of course, the current situation > is they are split and I'm sure there is some historical reason for > that and I wouldn't expect it to be changed. But in terms of a new > endpoint specifically for retrieving a history of conversation with a > particular user I don't really see what the benefit would be of > serving it up split (to the consuming application). > > On Apr 23, 1:04 pm, John Meyer wrote: > > > > > On 4/23/2010 10:58 AM, Orian Marx (@orian) wrote: > > > > f having two endpoints for > > > sent / received DMs in the first place, as you end up needing to make > > > two calls and then sort everything (if you're trying to show a stream > > > of DM conversations). > > > But if you're not making them into a conversation it makes more sense > > (i.e. a history). > > > -- > > Subscription > > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
Sure, yeah. But I would argue that DMs make more sense to be viewed by default as a stream of back and forth messages vs a separate history of sent and history of received. I would say it makes more sense to offer it as one endpoint to be split client side rather than two endpoints to be merged client side. Of course, the current situation is they are split and I'm sure there is some historical reason for that and I wouldn't expect it to be changed. But in terms of a new endpoint specifically for retrieving a history of conversation with a particular user I don't really see what the benefit would be of serving it up split (to the consuming application). On Apr 23, 1:04 pm, John Meyer wrote: > On 4/23/2010 10:58 AM, Orian Marx (@orian) wrote: > > > f having two endpoints for > > sent / received DMs in the first place, as you end up needing to make > > two calls and then sort everything (if you're trying to show a stream > > of DM conversations). > > But if you're not making them into a conversation it makes more sense > (i.e. a history). > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
On 4/23/2010 10:58 AM, Orian Marx (@orian) wrote: f having two endpoints for sent / received DMs in the first place, as you end up needing to make two calls and then sort everything (if you're trying to show a stream of DM conversations). But if you're not making them into a conversation it makes more sense (i.e. a history). -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
I've actually never understood the value of having two endpoints for sent / received DMs in the first place, as you end up needing to make two calls and then sort everything (if you're trying to show a stream of DM conversations). On Apr 23, 11:57 am, John Meyer wrote: > On 4/23/2010 9:39 AM, Taylor Singletary wrote: > > > Hi Orian, > > > Definitely think it would be useful and I've added it to my bucket of > > useful API ideas. We're focused on a number of projects right now, but > > I'm definitely keeping track of good ideas like this one for when the > > team has some feature selection flexibility in the future. > > > Taylor Singletary > > Developer Advocate, Twitter > >http://twitter.com/episod > > Do we want one endpoint or two endpoints, one for all direct messages > sent to a particular account and one for all direct messages sent from a > particular user (maybe a filter on the current direct messages endpoint, > perhaps)? > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
Good to hear. I've got more coming... :) On Apr 23, 11:39 am, Taylor Singletary wrote: > Hi Orian, > > Definitely think it would be useful and I've added it to my bucket of useful > API ideas. We're focused on a number of projects right now, but I'm > definitely keeping track of good ideas like this one for when the team has > some feature selection flexibility in the future. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > On Fri, Apr 23, 2010 at 8:32 AM, Orian Marx (@orian) > wrote: > > > > > So no one else would find this useful? > > > On Apr 20, 12:34 pm, "Orian Marx (@orian)" > > wrote: > > > I think it would be incredibly helpful to have an endpoint where we > > > could request direct messages sent back and forth between an > > > authorized user and some other user. This would make it significantly > > > easier to allow users to move backward through conversations with a > > > single user. Right now the only alternative is potentially making lots > > > of calls to direct_messages and direct_messages/sent hoping to come > > > across dms specific to that one user. > > > > I imagine this endpoint would look like this: > > > > url:http://api.twitter.com/1/direct_messages/between.xml(json) > > > > parameters: > > > * user_id. Specifies the ID of the user whose private conversations > > > with the authenticated user should be returned. > > > * screen_name. Specifies the screen name of the user whose private > > > conversations with the authenticated user should be returned. > > > * since_id. Optional. Returns only direct messages with an ID > > > greater than (that is, more recent than) the specified ID. > > > * max_id. Optional. Returns only statuses with an ID less than (that > > > is, older than) or equal to the specified ID. > > > * count. Optional. Specifies the number of direct messages to > > > retrieve. May not be greater than 200. > > > * page. Optional. Specifies the page of direct messages to retrieve. > > > > It would also be helpful to have an endpoint that retrieved new dms > > > sent or received since some id, instead of having to make calls to two > > > endpoints as we currently do, but I imagine user streams probably > > > covers this need. > > > > @orian > > > > -- > > > Subscription settings: > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
On 4/23/2010 9:39 AM, Taylor Singletary wrote: Hi Orian, Definitely think it would be useful and I've added it to my bucket of useful API ideas. We're focused on a number of projects right now, but I'm definitely keeping track of good ideas like this one for when the team has some feature selection flexibility in the future. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod Do we want one endpoint or two endpoints, one for all direct messages sent to a particular account and one for all direct messages sent from a particular user (maybe a filter on the current direct messages endpoint, perhaps)? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
Hi Orian, Definitely think it would be useful and I've added it to my bucket of useful API ideas. We're focused on a number of projects right now, but I'm definitely keeping track of good ideas like this one for when the team has some feature selection flexibility in the future. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, Apr 23, 2010 at 8:32 AM, Orian Marx (@orian) wrote: > So no one else would find this useful? > > On Apr 20, 12:34 pm, "Orian Marx (@orian)" > wrote: > > I think it would be incredibly helpful to have an endpoint where we > > could request direct messages sent back and forth between an > > authorized user and some other user. This would make it significantly > > easier to allow users to move backward through conversations with a > > single user. Right now the only alternative is potentially making lots > > of calls to direct_messages and direct_messages/sent hoping to come > > across dms specific to that one user. > > > > I imagine this endpoint would look like this: > > > > url:http://api.twitter.com/1/direct_messages/between.xml(json) > > > > parameters: > > * user_id. Specifies the ID of the user whose private conversations > > with the authenticated user should be returned. > > * screen_name. Specifies the screen name of the user whose private > > conversations with the authenticated user should be returned. > > * since_id. Optional. Returns only direct messages with an ID > > greater than (that is, more recent than) the specified ID. > > * max_id. Optional. Returns only statuses with an ID less than (that > > is, older than) or equal to the specified ID. > > * count. Optional. Specifies the number of direct messages to > > retrieve. May not be greater than 200. > > * page. Optional. Specifies the page of direct messages to retrieve. > > > > It would also be helpful to have an endpoint that retrieved new dms > > sent or received since some id, instead of having to make calls to two > > endpoints as we currently do, but I imagine user streams probably > > covers this need. > > > > @orian > > > > -- > > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
So no one else would find this useful? On Apr 20, 12:34 pm, "Orian Marx (@orian)" wrote: > I think it would be incredibly helpful to have an endpoint where we > could request direct messages sent back and forth between an > authorized user and some other user. This would make it significantly > easier to allow users to move backward through conversations with a > single user. Right now the only alternative is potentially making lots > of calls to direct_messages and direct_messages/sent hoping to come > across dms specific to that one user. > > I imagine this endpoint would look like this: > > url:http://api.twitter.com/1/direct_messages/between.xml(json) > > parameters: > * user_id. Specifies the ID of the user whose private conversations > with the authenticated user should be returned. > * screen_name. Specifies the screen name of the user whose private > conversations with the authenticated user should be returned. > * since_id. Optional. Returns only direct messages with an ID > greater than (that is, more recent than) the specified ID. > * max_id. Optional. Returns only statuses with an ID less than (that > is, older than) or equal to the specified ID. > * count. Optional. Specifies the number of direct messages to > retrieve. May not be greater than 200. > * page. Optional. Specifies the page of direct messages to retrieve. > > It would also be helpful to have an endpoint that retrieved new dms > sent or received since some id, instead of having to make calls to two > endpoints as we currently do, but I imagine user streams probably > covers this need. > > @orian > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
