/api/v1/conversations returns the wrong `last_status`
As an example of what I mean, see how my DMs view (using conversations) shows a public post at the top:
The last_status
field is on the wrong part of the tree. There is a tree of DMs in this thread, so it's correct to have it here, but the last_status
needs to be the last status in that DM tree, not the last status in the whole conversation.