Frontend API: `talk:unread:updated` value limitations

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

A problem

Notification level

Notification level should be considered when counting unreads.
For example, muted conversations (with Notifications: off) should be excluded.

Mentions vs direct message in one to one

mentionsDirect only includes direct mentions in group conversations.

But any message in one_to_one or one_to_one_former also should be counted as a direct mention in the unread count.

Messages and mentions

Problems:

• No way to count mentions withing a group conversation respecting "mentions only" notification level. Number of mentions = number of conversations with mentions.
• Unread messages count is slow to update on the frontend

Proposal

I'm unsure what we should provide.

Option 1: provide the simplified list of conversations so the client/apps can compute any required value

Option 2: provide predefined meaningful values:

• unmuted conversations
• conversations including muted
• messages from unmuted conversations
  • including "only mentions" and "all notifications" setting
• all messages

Talk app

Talk app version: 21.1.0

Start by reviewing the talk:unread:updated frontend API and the notification-level behavior described in the issue. Clarify how muted conversations, mentions, one-to-one messages, and unread messages should be represented before identifying the relevant Talk API and client entry points. Done means the value semantics are agreed and the frontend can obtain the required unread counts efficiently.