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 <john.l.me...@gmail.com> 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
