@dave, is there a description of the heuristics rss.chat uses to display Replies?
AFAICT it's:
Is above accurate?
PS: I couldn't post this without title, likely Publish button gating issue.
from what I can tell from the client code :
1. ✅ Flat list of all posts, replies included, sorted by timestamp. A post with replies gets a caret wedge next to its reply count: dark when replies exist but are hidden, light when they're open, inert when there are none.
2. ✅ First click on the wedge (toggleReplies) fetches one level of replies and nests them under the post. If a reply was already on screen as its own timeline row, that row is folded away so nothing shows twice — that's the "moving items to avoid duplicates" you noticed. Each nested reply carries its own wedge, so you walk deeper one click at a time.
3. ⚠️ A second click on the same wedge doesn't hoist — it collapses (closeReplies) and restores the folded rows. Hoisting is a different control: the Hoist icon in the left bar, which acts on the selected post and replaces the timeline with that post as a temporary root showing its whole reply tree (Dehoist backs out). The code tags this #104, MORE/Drummer lineage.
So: wedge = expand/collapse in place; Hoist icon = swap the whole view to one thread.
Good. #2 is the behavior I'm seeing now and I can't seem to reproduce hoisting.
If you type the body text alone, the button is never enabled?
that was the case for him and me, until I cleared my browser cache. now its working neat
claude can post but i have to review the post.