[Feature Request] Subscribe to feed for conversation
[Feature Request] Subscribe to feed for conversation
| Issue ID: | 2841 |
| Issue Category: | feature |
| Component: | core |
| Priority: | normal |
| Status: | active |
| Assigned: | brion |
| Version: | 0.9 |
| Keywords: | follow conversation |
A feature where you could subscribe to a feed for a conversation would be very good for conversations like https://identi.ca/conversation/55760715 which is essentially the comments section of a blog post.
Updates
#1
+1
Being able to subscribe to a conversation feed would be useful in some contexts, but usually I want all notices from a conversation to appear in my timeline -- ie add notices from conversation participants that I don't subscribe to.
Idle speculation: would addressing this issue create base for fixing splintered conversations across sites -- http://status.net/open-source/issues/2231 ?
#2
+1
1) I think there should be a way to follow any specific conversation (by its numeric id).
2) I also think that normally the person who started a conversation should be automatically subscribed to it.
3) Even further, some people could consider useful if a person who replies to a conversation will be automatically subscribed to it, as well.
4) I'm sure that such behavior (items 2 and 3) should be customizable on per user basis. (That is, every user should have a possibility to switch off behavior 2 and/or 3.)
5) There should be a way to unsubscribe from (stop following) a conversation.
6) There should also be a way for user to get a list of conversation numbers he/her subscribed to at the moment.
7) (And yes, I agree with @mlinksva, and items 1-6 are about user's timeline.)
But RSS/ATOM feeds for conversation is also the must, I think.
#3
Another thought on the subject came to my head.
I still don't have a suggestion of this issue -- maybe someone else has or will have.
Normally when I see a dent in my timeline I can instantly say why it is in my timeline (I see a name of either a group or a person I subscribed to. But with dents that are a part of a conversation it would not be so easy). This is a thing that should be thought of when (if) implementing the feature.
(Please, keep in mind, at least, web and xmpp users.)
You can also subscribe to the
RSS feed for updates to this issue.