Hi, Philipp H. pointed out an interesting issue today: MUC-PMs are sent by a MUC to all joined client full-JIDs, so if you are joined to a MUC with two devices, your account will see two copies of the messages. Your MAM archive is also going to store two copies of them, with different MAM-IDs, which makes later deduplication rather complicated (you can't rely on them having a message ID or an origin-id, and the timestamp might vary a bit).
Do we want MUC-PMs stored in MAM at all? And if yes, how can we prevent multiple copies from being stored? (Please ignore for a moment the synchronization problems that arise if you respond to MUC-PM copies before joining the respective MUC). Another nice corner case are messages to my own JID. Servers will send a "sent" Carbon Copy of them to all your other clients, then reflect the message to the "most available" client and send a Carbon Copy to all others. Each client ends up with two copies of each message, and the MAM archive probably as well. Does this make sense? Georg -- || http://op-co.de ++ GCS d--(++) s: a C+++ UL+++ !P L+++ !E W+++ N ++ || gpg: 0x962FD2DE || o? K- w---() O M V? PS+ PE-- Y++ PGP+ t+ 5 R+ || || Ge0rG: euIRCnet || X(+++) tv+ b+(++) DI+++ D- G e++++ h- r++ y? || ++ IRCnet OFTC OPN ||_________________________________________________||
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
