Hi, first of all thank you Matt for the update.
> In the case of non-anonymous rooms or if the recipient of the MUC archive has > the right to access the sender real JID at the time of the query, the archive > message will use extended message information in an <x/> element qualified by > the 'http://jabber.org/protocol/muc#user' namespace and containing an <item/> > child with a 'jid' attribute specifying the occupant's full JID, as defined > for non-anonymous room presence in Multi-User Chat (XEP-0045) [10]. This is still missing a bit on MUC archives having to sanitize (room) the <x> element so it can not be spoofed by the original sender. I believe this MUST happen for any muc archive and not just MUC archives where the <x> element is sent. Gruß Daniel 2017-02-19 22:55 GMT+01:00 XMPP Extensions Editor <[email protected]>: > Version 0.6 of XEP-0313 (Message Archive Management) has been released. > > Abstract: This document defines a protocol to query and control an archive of > messages stored on a server. > > Changelog: [See revision history] (dg, mw) > > Diff: https://xmpp.org/extensions/diff/api/xep/0313/diff/0.5.1/vs/0.6 > > URL: https://xmpp.org/extensions/xep-0313.html > > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
