[decide] Threads: opening a room marks every thread in it read — chip/list unread badges never survive a room visit #217

New Issue

2026-09-18T21:31:31-04:00

jared commented

2026-09-18 21:31:31 -04:00

From the #165 audit. utils/notifications.ts markAsRead (fired by RoomTimeline whenever the room is at the bottom and focused) also sends a threaded receipt for every thread with unread replies. Result: a reply in a thread you participate in lights the chip / Threads-list badge only until you glance at the room — then it is gone, even though you never opened the thread.

Discord and Slack keep thread unreads until the thread itself is opened; the room-level receipt was added so the room dot does not stay lit forever. Options: (a) keep room-level clearing (current), (b) clear threads only when the thread panel/list is opened and subtract muted/unread threads from the room dot differently, (c) middle ground: room visit clears non-participating threads only. Product call — your pick, then it is a small change.

Side effect today: two identical receipts per reply (panel + room-level), harmless.

From the #165 audit. `utils/notifications.ts` `markAsRead` (fired by RoomTimeline whenever the room is at the bottom and focused) also sends a threaded receipt for every thread with unread replies. Result: a reply in a thread you participate in lights the chip / Threads-list badge only until you glance at the room — then it is gone, even though you never opened the thread. Discord and Slack keep thread unreads until the thread itself is opened; the room-level receipt was added so the room dot does not stay lit forever. Options: (a) keep room-level clearing (current), (b) clear threads only when the thread panel/list is opened and subtract muted/unread threads from the room dot differently, (c) middle ground: room visit clears *non-participating* threads only. Product call — your pick, then it is a small change. Side effect today: two identical receipts per reply (panel + room-level), harmless.

jared added this to the Features 2026-Q4 milestone 2026-09-18 21:31:31 -04:00

jared added the priority: medium ux area: threads planning labels 2026-09-18 21:31:31 -04:00

jared referenced this issue

2026-09-18 21:31:32 -04:00

[deep dive] Threads: full UI/UX audit + "mark all threads read" #165

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/cinny#217