Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Desktop: live threaded reply renders as a top-level channel row until channel switch

Open
  • Is something wrong?
#7,705 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
desktop

Research direction

Start with useLiveChannelUpdates in desktop/src/features/channels/useLiveChannelUpdates.ts, then compare its merge path with useChannelSubscription in desktop/src/features/messages/hooks.ts and buildMainTimelineEntries in desktop/src/features/messages/lib/threadPanel.ts. Reproduce the live threaded-reply steps and trace the final render path; done means non-broadcast replies appear only in the thread panel and remain absent from the main timeline after live delivery.

Written by the indexing model from the issue text.

Description

Filed from Leo Wandersleb's account by his Buzz agent (Bob) on his behalf; Fable 5.1 helped authoring this issue.

Summary

When a threaded reply arrives live (relay push) in the channel the user is currently viewing, Desktop renders it twice: once in the thread panel (correct) and once as a full top-level row in the channel timeline, under the NEW divider. The root message's thread summary row updates correctly at the same time (1 reply · last reply just now), so the same event is counted as a reply and rendered as a channel row simultaneously.

The extra channel row disappears as soon as the user switches to another channel and back. Reloading history never reproduces it. It is purely a live-arrival artifact.

Observed on Buzz Desktop v0.5.23 (Linux, .deb, "You're on the latest version"), replying agent on buzz-acp/buzz-cli, but the reply event is an ordinary human-shaped kind 9.

What the relay holds (verified)

Raw REQ for all kinds in the channel since the root shows exactly one content event for the reply:

  • kind 9, tags: ["h", <channel>], ["e", <root-id>, "", "reply"], ["p", <root-author>]
  • no broadcast tag
  • identical tag shape to the human replies in the same thread

So this is not a second event and not an "also send to channel" reply.

Rendering tell

In the duplicated channel row the @Name mention renders as plain text; in the thread-panel copy the same mention renders as a mention chip. The two copies are produced by different render paths.

Where I looked (main at 4ab4f7860, identical at desktop-v0.5.23 / b9392d9d7)

  • buildMainTimelineEntries (desktop/src/features/messages/lib/threadPanel.ts) keeps parentId == null || isBroadcastReply(...) only. Unchanged since April. By this filter the reply cannot become a main-timeline entry.
  • useChannelSubscription appendMessage (desktop/src/features/messages/hooks.ts) routes replies to threadRepliesKey(channelId, rootId) and returns early unless broadcast. Correct.
  • useLiveChannelUpdates (desktop/src/features/channels/useLiveChannelUpdates.ts, ~L340) merges every live event, including threaded replies, into the flat channelMessagesKey(channelId) cache via mergeTimelineCacheMessages, with no parentId check. This is the only live path that puts the reply into the channel's message list.
  • On channel switch, projectChannelWindowMessages re-flattens the window store over channelMessagesKey. The window store never received the reply (the subscription path excluded it), so the row vanishes. That matches the observed behaviour exactly.

I could not find the final hop that turns the cached reply into a rendered top-level row (the memoised filter above should drop it), so the duplicate may come from a component I did not read. The useLiveChannelUpdates merge is the strongest suspect and is inconsistent with the subscription path either way.

Repro

  1. Open channel A in Desktop and keep it in view.
  2. From another client, post a top-level message in A, then a threaded reply to it (buzz messages send --reply-to <root> works).
  3. The reply appears in the thread panel and as a new top-level row in A's timeline under NEW.
  4. Switch to channel B and back to A: the extra row is gone.

Expected

A threaded reply without broadcast=1 never renders as a main-timeline row, live or from history.

Filed from Leo Wandersleb's account by his Buzz agent (Bob) on his behalf; Fable 5.1 helped authoring this issue.

Dominant language
Rust
Stars
35.3k
Forks
4.7k
Avg merge
2d 15h
Merged PRs (30d)
175

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from block/buzz

All issues in block/buzz

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.