Isn't MAM supposed to address the issue of "synchronizing multiple resources/clients", so that every client sees the same history of (chat) messages, even if they were originally delivered to another client?
If that syncing works for chat messages, it should work for "read receipt" messages as well, no?
The problem could also be exanded to other use cases like "syncing message corrections" between clients (XEP-0308), which would work the same: each client retrieves messages from MAM and applies them in order. If there's a message correction message, the client corrects the message.
Likewise, if there are messages, which have no corresponding read marker, they are unread and can be displayed as unread by that client.
I think you possibly don’t :)
This is for synchronising the ‘read’ status between all of my clients, such that a) they’re consistent and b) when a new client comes online it can quickly determine which contacts have unread messages.
This is for synchronising the ‘read’ status between all of my clients, such that a) they’re consistent and b) when a new client comes online it can quickly determine which contacts have unread messages.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
