For articles, this should be a fairly simple reader view. For microblog posts I would like this to become more of a “conversation” view.
There are a couple ways I would like to do this. One is if the jf2 has the reply to url unfurled, show those details. If not, use X-ray to try unfurling a reply live when you open the view.
Check if there are any embedded replies/likes in the jf2 (right now, I don’t think any Microsub servers even support this).
Once I cache posts from the channels into CoreData, I should be able to query for any posts that are in any timelines and are replies to this post’s URL. That would allow you to see how different friends throughout your channels are responding to each other in this conversation view of a post.
Currently the best possible option would be potentially using Xray against the current post url, and seeing if there are any replies/likes/etc on the current post’s url. I could pull in that data temporarily on the conversation page load.
The conversation view will take a lot of visual cues from Tweetbot’s conversation/detail view
For articles, this should be a fairly simple reader view. For microblog posts I would like this to become more of a “conversation” view.
There are a couple ways I would like to do this. One is if the jf2 has the reply to url unfurled, show those details. If not, use X-ray to try unfurling a reply live when you open the view.
Check if there are any embedded replies/likes in the jf2 (right now, I don’t think any Microsub servers even support this).
Once I cache posts from the channels into CoreData, I should be able to query for any posts that are in any timelines and are replies to this post’s URL. That would allow you to see how different friends throughout your channels are responding to each other in this conversation view of a post.
Currently the best possible option would be potentially using Xray against the current post url, and seeing if there are any replies/likes/etc on the current post’s url. I could pull in that data temporarily on the conversation page load.
The conversation view will take a lot of visual cues from Tweetbot’s conversation/detail view