* Thilo Molitor <[email protected]> [2019-02-17 14:03]: > Does anyone of you use XEP-0013 in your client other than for purging offline > messages when you support MAM?
To write down our discussion from the MUC: I think this is a bad idea for multiple reasons. 1. 0013 is just a workaround for a problem that should be solved by MAM instead (duplication between offline messages and the data from MAM). 2. 0013 is prone to race conditions between the deletion of the offline messages, the MAM query and the available presence, where messages will be duplicated in the best case and lost in the worst case. 3. Use of 0013 does not imply MAM. My suggestion for the specific problem of 0198 zombie extermination is the following, instead: Silently drop the messages from the 0198 queue if both of these conditions are met: - the account has a MAM policy of 'always' (not 'roster' or 'never') (*) - the specific session to be destroyed has performed a MAM query in the past (*) you should generally bounce messages from MUCs, as well as MUC-PMs. If the MAM policy is 'roster', you could of course silently drop messages from roster items (good luck matching those with roster changes though), but you probably should bounce messages from non-roster JIDs. We should also think about changing MAM to not deliver offline messages at all after a MAM query (with a similar rule set as above), or maybe to add an explicit client-controlled delete-offline-history flag to the MAM query. Georg
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
