Fetching convos via MastoAPI

• Conversations now store which statuses they need to display instead of attempting to find statuses by statusnet_conversation_id (which mastoapi doesn't have)

Since MastoAPI doesn't support convesration id, we can't use current flow, and to be honest it's kinda slow.

Old conversation flow:

• fetch relevant statuses
• show all statuses that we know of that have same statusnet_conversation_id, this will update when new statuses are fetched This essentially O(n) since it's basically searching entire allStatuses for which statuses have needed convo id, if you have 4000+ statuses in memory this will get slow, but this allows dynamic update to conversations

New conversation flow:

• fetch relevant statuses (MastoAPI works slightly different, providing "above" and "below" lists instead of one list, doesn't contain status)
• temporarily store which statuses we should display from response data
• display all relevant statuses by getting them from faster allStatusesObjects This will not automatically update unfortunately, but I think better mechanism could be implemented there.