Matrix: a message cannot be marked unread again #194

Closed
opened 2026-09-11 22:26:03 -04:00 by Salastil · 1 comment
Owner

No m.marked_unread (nor the older com.famedly.marked_unread).

Reading a room is one-way here: once seen, it is read. Every other client in the
ecosystem lets somebody mark a room unread deliberately, as a note to come back to it,
and that mark is account data so it follows them between clients. moho neither sets it
nor honours one set elsewhere, so a room flagged on the phone looks read here.

No `m.marked_unread` (nor the older `com.famedly.marked_unread`). Reading a room is one-way here: once seen, it is read. Every other client in the ecosystem lets somebody mark a room unread deliberately, as a note to come back to it, and that mark is account data so it follows them between clients. moho neither sets it nor honours one set elsewhere, so a room flagged on the phone looks read here.
Salastil added the featurelow priority labels 2026-09-11 22:26:03 -04:00
Author
Owner

Finished — https://git.salastil.com/Salastil/nobilis/commit/03e8bc8, https://git.salastil.com/Salastil/moho/commit/ab250d1

Both spellings read (m.marked_unread and the older com.famedly.marked_unread), stable one written. An absent key is treated as "no opinion" rather than false, so a stale mark is never silently overwritten. Shown as a dot rather than a count, since a deliberately-unread room has no number to show.

Finished — https://git.salastil.com/Salastil/nobilis/commit/03e8bc8, https://git.salastil.com/Salastil/moho/commit/ab250d1 Both spellings read (`m.marked_unread` and the older `com.famedly.marked_unread`), stable one written. An absent key is treated as "no opinion" rather than false, so a stale mark is never silently overwritten. Shown as a dot rather than a count, since a deliberately-unread room has no number to show.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Salastil/moho#194