search

microdotblog / issues

42 stars 0 forks source link

Feature: Make Conversation Thread JSON Feed public and linked from individual comment permalinks #144

Open EdwardHinkle opened 5 years ago

EdwardHinkle commented 5 years ago

If I'm in my reader, and I see a reply by smokey that I find interesting (https://micro.blog/smokey/3695363) I might want to "follow" that conversation in my reader.

The first thing I checked as the JSON API of that conversation: https://micro.blog/posts/conversation?id=3695363 which I believe would provide a JSON Feed of the conversation, so any new posts in reply would end up in my reader. This, however, requires a token which is very difficult in readers currently (although would be a useful option for AutoAuth https://github.com/sknebel/AutoAuth/issues/10).

The other thing is, without programming a bunch of logic into my reader, there is no way to know the conversation feed url for this post. It would be great, if this feed was public (since it contains public posts anyway) and was linked to using link rel-alt so that the original post url (https://micro.blog/smokey/3695363) being entered into a "subscribe" field could detect the conversation's JSON Feed and allow me to subscribe.

manton commented 5 years ago

Thanks. I don't see why the conversation feeds couldn't be public.

sardisson commented 5 years ago

This came up again recently in a conversation, and I realized the “reason” (or a reason) the Conversation feeds need auth is so that the posts can be filtered according to a person’s Blocked Users list.