Conversation
Notices
-
@kevingranade That is indeed how I worked around the problem :)
-
Oh, good.
-
It'd be interesting to hear what you think about the ordering. We do it reverse-chron, like other API calls.
-
Considered building a tree structure, or having it in some other tree-ish order, but this just made sense.
-
@kevingranade I do this for !statusthread, but max_id doesn't seem to work for conversations, e.g. http://identi.ca/url/53835332
-
Can you post an issue here? http://status.net/open-source/issues
-