LotusGuild/cinny
3
0
Fork 0
Code Issues 27 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

Opening a room silently marks every thread you don't follow as read, so the Threads panel's "Unread" filter never shows them #314

New Issue
Closed
opened 2026-10-05 01:26:04 -04:00 by jared · 0 comments
jared commented 2026-10-05 01:26:04 -04:00
Owner
Copy Link
Copy Source

markAsRead (src/app/utils/notifications.ts, the "Clear per-thread notification counts too" block) runs whenever you view a room. It sends a threaded receipt for the last reply of every unread thread. The only exceptions are threads you follow (#217) and the open thread.

Measured: two threads in a room. You've replied in "root FOLLOWED"; "root OTHER" you've never touched. You're elsewhere while Bob adds 2 replies to each. Then you open the room and the Threads panel:

  • "root FOLLOWED" shows unread (2), the Mark all read chip appears, and clicking it works (the chip goes away). ✔
  • "root OTHER" is already read and is absent from the Unread tab. Nothing in the room tells you it got 2 new replies, apart from the plain "3 replies" count.

So the "Unread" filter, the "unread replies" row label and "Mark all read" (#165) only ever work for followed threads. Opening the room, which you need to do to reach the panel, has already cleared every other thread. Before you open the room, the room-list dot does count those replies, so the room looks unread, you open it, see nothing new in the main timeline, and the dot is gone.

Options:

  • Leave unfollowed threads' counts alone when viewing the room, and stop counting them toward the room's unread dot or badge (the "room is unread" problem #217 worked around). The Threads panel can still show them as unread until you open the thread or press Mark all read.
  • Or keep the current behaviour but say so: e.g. a one-time hint in the Threads panel ("Threads you haven't replied to are marked read when you open the room"), and drop the "Unread" filter for unfollowed threads.

Verified in the same pass: the paste-as-code offer works with a real multi-line JS paste (chip, then Format as code sends <pre><code class="language-js"> with indentation intact). The composer toolbar show/hide setting works (hiding Location removes "Share location"). Operator-only searches other than from: show "Add a word to search for, or a from:@user.", as designed.

Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny 30e2dbcd, cinny-desktop 8f67ec7, element-call 3b0050e8.

`markAsRead` (`src/app/utils/notifications.ts`, the "Clear per-thread notification counts too" block) runs whenever you view a room. It sends a threaded receipt for the last reply of **every unread thread**. The only exceptions are threads you follow (#217) and the open thread. **Measured:** two threads in a room. You've replied in "root FOLLOWED"; "root OTHER" you've never touched. You're elsewhere while Bob adds 2 replies to each. Then you open the room and the Threads panel: - "root FOLLOWED" shows **unread (2)**, the **Mark all read** chip appears, and clicking it works (the chip goes away). ✔ - "root OTHER" is already read and is **absent from the Unread tab**. Nothing in the room tells you it got 2 new replies, apart from the plain "3 replies" count. So the "Unread" filter, the "unread replies" row label and "Mark all read" (#165) only ever work for followed threads. Opening the room, which you need to do to reach the panel, has already cleared every other thread. Before you open the room, the room-list dot does count those replies, so the room looks unread, you open it, see nothing new in the main timeline, and the dot is gone. **Options:** - Leave unfollowed threads' counts alone when viewing the room, and stop counting them toward the room's unread dot or badge (the "room is unread" problem #217 worked around). The Threads panel can still show them as unread until you open the thread or press Mark all read. - Or keep the current behaviour but say so: e.g. a one-time hint in the Threads panel ("Threads you haven't replied to are marked read when you open the room"), and drop the "Unread" filter for unfollowed threads. Verified in the same pass: the paste-as-code offer works with a real multi-line JS paste (chip, then **Format as code** sends `<pre><code class="language-js">` with indentation intact). The composer toolbar show/hide setting works (hiding Location removes "Share location"). Operator-only searches other than `from:` show "Add a word to search for, or a from:@user.", as designed. --- _Found in the October 2026 client audit (Playwright against a local Synapse + LiveKit stack, plus code reading). Code refs are at cinny `30e2dbcd`, cinny-desktop `8f67ec7`, element-call `3b0050e8`._
jared added the priority: lowuxarea: threads labels 2026-10-05 01:26:04 -04:00
jared closed this issue 2026-10-19 02:33:26 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
a11y
Accessibility: keyboard, screen reader, contrast, motion
 area: appearance
Client area: appearance
 area: auth-session
Client area: auth-session
 area: build-ci
Client area: build-ci
 area: calls
Client area: calls
 area: desktop
Client area: desktop
 area: media
Client area: media
 area: messaging
Client area: messaging
 area: mobile
Client area: mobile
 area: moderation
Client area: moderation
 area: navigation
Client area: navigation
 area: notifications
Client area: notifications
 area: settings
Client area: settings
 area: threads
Client area: threads
 bug
Something is not working
 dependencies
Third-party package versions and advisories
 docs
README / LOTUS_* docs wrong or missing
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 needs-human-review
performance
Re-render storms, leaks, heavy work on hot paths
 planning
priority: critical
Data loss, security hole, or crash on a main path
 priority: high
Broken feature or serious usability problem
 priority: low
Minor issue or polish
 priority: medium
Wrong behaviour in an edge case or notable degradation
 qa
Manual QA: shipped, needs a human in a real environment
 question
More information is needed
 research
security
XSS, unsafe URLs, data leaks, auth/session
 tech-debt
Code health, dead code, fragile patterns
 ux
Usability or visual inconsistency
 wontfix
This won't be fixed
No labels area: threads priority: low ux
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
cole (Cole Keller) jared (Jared Vititoe) nathan (Nathan Vititoe)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LotusGuild/cinny#314