Seed’s comment threading currently feels closer to Twitter/X-style replies than to a structured conversation space. This creates friction when trying to follow a discussion.

In a Twitter-style thread, each reply can feel like an isolated object. The conversation becomes fragmented across nested replies, links, and individual comment views. This may work for public microblogging, but it is not ideal for collaborative discussion around documents.

When I open a comment or reply, I often cannot easily understand:

What is the full conversation?

What message started the thread?

Which comments are direct replies?

Which replies are part of the same discussion?

What happened before this comment?

What is the latest activity?

Where should I reply?

Am I replying to the thread or accidentally starting a new branch?

This makes it difficult to build shared context.

A good conversation view should feel more like a single readable discussion, not a chain of disconnected reply objects.

The current threading UX creates several problems:

Conversations feel fragmented.

It is hard to understand the full context.

Replies can feel disconnected from the main discussion.

Users may not know where to reply.

Threads become difficult to scan.

The conversation does not feel like one shared space.

Important conclusions get buried inside reply chains.

This is another reason users fall back to Discord or Slack. Those tools make the active conversation feel continuous. You can open a thread and read it from top to bottom. Seed should preserve its document-native advantage, but the discussion itself needs to feel easier to follow.

The problem is not simply that Seed supports threaded replies. The problem is that the UX emphasizes individual comment/reply objects more than the overall conversation.

Seed needs a clearer discussion-level experience where the thread root, all replies, latest activity, and reply box are presented together as one coherent conversation.