MSC3306: Counting unread messages #3306
Conversation
KitsuneRal
changed the title
turt2live
added
kind:maintenance
| with `action` set to `notify`. There's merit therefore providing a common | ||
| "notable events" criterion, both for homeservers to calculate the unread count | ||
| uniformly but also for clients so that they could provide more accurate numbers | ||
| when it's possible and/or even customise the calculation algorithm to | ||
| users' liking. |
There was a problem hiding this comment.
Shouldn't we rather be fixing the pushrules to match the reality returned by homeservers? Hardcoding a room count algorithm sounds bad. I have specific keyword mentions set on rooms, etc. I expect the notification count to reflect that, not some arbitrary, homeserver specific algorithm. Can you describe in which way the count currently calculated by homeservers and your algorithm differ from what would be calculated by following the push rules?
There was a problem hiding this comment.
Or am I confused and you meant unread counts (not notification counts), which have an algorithm specified here: #2654 ?
There was a problem hiding this comment.
I did mean an unread count - however, as the MSC mentions, Synapse returns it under the name of notification_count, which is quite confusing since the number of notifications is different. And yes, I should have searched for prior art... Closing this, and will contribute to #2654 instead.
KitsuneRal
added
obsolete
RenderedSee #2654 instead.