FA-75894 / Chat ordering and read receipts / Member archive

Count unread messages for a conversation badge: own author casefold · case 04

Messages sent from the user's other client, which spells the handle with different casing, count as unread.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

messages are {seq, author, kind, thread, broadcast}. A message counts when seq > marker, the author differs from me (user handles compare case-insensitively), kind is exactly "user", and it is top level (thread is None) or a thread reply that is broadcast to the channel or belongs to a followed thread (a thread root may have seq 0). Badge: "" for 0, the count up to 99, "99+" above 99.

Why this case matters

Unread badges are the main signal of pending conversation work; miscounts either nag or hide messages.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
own message from another client casing	`{"badge": "2", "count": 2}`	`{"badge": "1", "count": 1}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.