Replies & threads

Every post on Zeeker is the root of its own thread. Replies are first-class posts that link back to a parent.

Reply mechanics

• Any post can be replied to by any signed-in user (subject to community rules and blocks).
• After a reply is saved, the thread total updates immediately without requiring a refresh.
• A reply is itself a post — it can be reposted, quoted, reacted to, saved, and replied to.
• There is no hard nesting limit, but the UI collapses long parent chains at 12 ancestors. Beyond that, a "Show parent chain" link expands inline.
• Reactions and reposts on a reply do not count toward the root post — each node has its own metrics.

The reply composer shows context from the exact post being replied to: its readable text, title, or link. Replies to a nested comment keep that comment's context rather than substituting the original root post. For an automatically linked page discussion whose root card is hidden in an Embed, the composer says Replying to this page and uses the available page title or link context. It does not show an empty parent preview or invent an author for the page.

Thread view

Opening any post (/p/<post-id>) shows the thread view:

1. Parent chain — every ancestor of the focused post, rendered as compact cards.
2. Focused post — the one the URL points to, rendered full-size.
3. Activity filters — All, Replies, References, and Related switch between the discussion and its relationship activity.
4. Replies — direct children appear in the community's configured default order, with their nested conversation context below them.

The parent chain is loaded in one request — there's no scroll-to-reveal back through history.

The first reply page is bounded and cached separately for the exact post, reader, access scope, and selected sort. Load more replies (or infinite loading where an Embed is configured for it) follows the server's opaque continuation. Trending, Popular, and Recent are ordered by the server before pagination, so loading another page never re-sorts or reshuffles replies already on screen.

The All filter uses one initial activity loader beneath the Replies heading. References and Related sections do not reserve empty space or show their own loaders there; each appears only when it has content. Their dedicated filters still provide the appropriate empty and loading states. Relationship pagination is deferred to those dedicated filters, avoiding concurrent background page loads while a reader is in All.

Reaction mood highlights

When a post has at least six direct replies, the thread can gently distinguish up to two replies whose reactions show a clear mood:

• One strongly positive reply may receive a bright green surface tint.
• One strongly negative reply may receive a soft red surface tint.
• A reply qualifies only after receiving at least three reactions from that mood and those reactions account for at least 60% of all its reactions. Likes, loves, and laughs are positive; sad and angry are negative; wow is neutral.

After the reply remains in the viewport for half a second, the tint fades across its full surface, including the top edge. It remains in place after that first reveal, respects reduced-motion preferences, and uses adjusted colors in dark mode. Selection uses the reaction totals already included with the reply list, so scrolling does not make another network request. Embed replies use the same full-surface highlight through the button tray; nested replies below the selected reply remain neutral.

Sorting

Reply lists can be sorted by:

• Trending — a recency-weighted score over reaction and reply activity.
• Popular — highest reaction total first.
• Recent — strict reverse-chronological order.

The Trending / Popular / Recent control is available in both All and Replies. A community can configure the initial choice; the thread resolves that setting before mounting the first-level reply cards, so the list does not briefly appear in one order and then reshuffle. If no community default is available, Trending is used.

Mentions

@username in a reply notifies the mentioned user. Mentions are clickable and open the profile.

Reply-only feeds

A user's profile has a Replies tab that shows all their replies in reverse-chronological order, each one rendered with one ancestor for context.

Reply privacy

The visibility of a reply inherits from the root post:

• A reply to a public post is public.
• A reply to a followers-only post is visible only to followers of the original author (not the replier).
• A reply to a community-only post is visible only to members of that community.

Quoting in a thread

If you quote a post from inside a thread, your quote becomes a new top-level post on your timeline. It is not silently added as a reply in the original thread — to comment in-thread, use Reply.

After you post a reference from the open post's References activity, Zeeker keeps that thread open, refreshes the activity, and brings the new reference into view. A reference to a nested card opens that card's reference surface; an embed without reference activity opens the created reference so it cannot disappear from view. If a community moderates new posts, the pending reference is visible to its author and community staff while it awaits approval; other readers see it only after approval.

Deletions inside a thread

When a post in the middle of a chain is deleted, the chain stays intact — the deleted node renders as a [deleted] placeholder so replies below remain readable.

Embed thread parity

Threads created via the embed widget live in the same posts table and are reachable at zeeker.com/p/<post-id>. A widget-originated thread is identical to a native one; the widget just provides the surface to participate from a third-party site.