Note: The comment link in the post seems broken from LW. Maybe that's a GreaterWrong specific link syntax, but LW uses hashtags with comment ids, instead of a /comments/<commentId> syntax.
Yep, API wise this should be relatively straightforward, though it will require doing some database mutations, so it might take us a bit longer than usual. In particular, we don't know from just looking at a comment whether the post it was posted to was on the frontpage, or in meta, or anywhere else, so we will have to add some additional metadata there.
Note: The comment link in the post seems broken from LW. Maybe that’s a GreaterWrong specific link syntax, but LW uses hashtags with comment ids, instead of a
/comments/<commentId>syntax.
Ah yes, sorry; /comments/<commentId> is the GW URL pattern for individual-comment-thread permalinks (like on old LW).
Yep, API wise this should be relatively straightforward, though it will require doing some database mutations, so it might take us a bit longer than usual. In particular, we don’t know from just looking at a comment whether the post it was posted to was on the frontpage, or in meta, or anywhere else, so we will have to add some additional metadata there.
Ah, I see, thanks. Well, whenever you are able to get to it, this would definitely be appreciated!
Actually I like and use the mixed comment feed.
I'd like an, "ancient comment feed" for any posts older than a year. So that those can get some. Responsive activity.
I would not be against separate feeds as well, so long as we don't lose the mixed feed.
(Inspired by discussions like this one, but also a thing that I’ve thought for a while would be a good idea.)
Currently, there’s a single “recent comments” feed, which includes comments posted to any post—frontpage, Meta, personal blogs, Alignment Forum… even drafts! (The last of which, I assume, is merely a bug.)
It would be cool if there were multiple comments feeds, one for each view, viz.:
It’s probably a lot of work for you guys to implement a UI for this, so I can totally understand it not being priority, but would it be possible to implement this feature in the backend and expose it in the API?