Files
StarPunk/docs/design/v2.20.2/2026-11-13-backfeed-reply-threads.md
T
PhilandClaude Opus 5.5 bf6e0fdc0b fix: backfeed whole reply threads and nest them (v2.20.2)
Backfeed only read first-level replies (Threads /replies, GoToSocial
direct replies, Bluesky depth 1) and skipped the owner's own replies, so
conversations under crossposts lost everything after the first reply.

- Threads /conversation, all GoToSocial descendants, Bluesky depth 10
- backfeed.thread_members keeps others' replies to our copy and any reply
  (ours included) to a kept reply; own replies are stored as notified
- Migration 026: webmentions.parent_remote_id; replies render nested as
  comments of comments

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 20:43:30 -07:00

2.1 KiB

v2.20.2: Backfeed whole reply threads

Why

https://starpunk.thesatelliteoflove.com/note/20261110191424 showed one reply (curiouskatej, via Threads). The Threads conversation had three:

curiouskatej: "It keeps coming up on music compilations…"     (kept)
  └ philskents: "That is terrifying..."                       (missed)
      └ curiouskatej: "To be fair it's just as bad as…"       (missed)

Each client read only the first level of replies: Threads /{id}/replies, GoToSocial descendants with in_reply_to_id == our id, and Bluesky getPostThread at depth 1. All of them also dropped the owner's own replies, which lost one side of the conversation.

Changes

Area Change
backfeed.thread_members(posts, root) Decides which replies to keep, and what each answers. Kept: others' replies to our copy, plus any reply (ours too) to a kept reply. Our own replies to our copy are the thread continuing, so they and their replies are left out, as before
Response.parent_id, .own The silo id of the reply this one answers (None for our copy itself), and whether we wrote it
Threads /{id}/conversation (every depth, newest first) with replied_to in the fields
GoToSocial All public descendants from /context
Bluesky getPostThread depth BLUESKY_THREAD_DEPTH (10), walked recursively; blocked or deleted posts drop their subtree
Migration 026 webmentions.parent_remote_id
backfeed.store Stores the parent; own replies are stored as already notified
webmention_queries.reply_threads Nests replies under their parent (same origin and remote id). A reply whose parent isn't shown goes to the top level
Templates/CSS responses.reply renders children in .webmention-thread, indented with a side rule, as u-comment h-cite inside the parent's h-cite

The heading still counts every reply ("3 Replies"), and so does the count line under the note.

Existing crossposts get their threads at their next scheduled check. The check schedule slows with the note's age (ADR-073), and notes past the cutoff aren't checked.