Inbox does not update unread counter correctly when not marking all messages as read about mongooseim HOT 2 CLOSED

I don't think we are going to implement this behaviour. While it's technically possible to implement, the implementation would be supper inefficient:

• the key problem is that chat marker message provides only message id to the server, not the number of message.
• Inbox module tracks only the last message in the conversation (so it knows its id), and it can easily reset the counter in this case.
• Otherwise, it requires making complex queries to MAM tables to understand the actual counter shift that corresponds to the random message id.

From another side, the client application knows the exact adjustment for the unread counter. So client app can easily tell it to the server via IQ.

from mongooseim.

Hi @DenysGonchar, thanks for the explanation!

from mongooseim.