On 2018-12-07 10:27, Daniel Gultsch wrote:
[..] However it would be nice to also figure out by looking at the JID if that message might be a reflection or a message from ourself.
Isn't this case covered by the inclusion of the <submission-id/> as per example 30 (XEP-0369) and the prose just above it?
The messages sent to participants have a different message id to the originally submitted message. This does not impact most recipients, but it does not allow the message originator to correlate the message with the submitted message. To address this the MIX channel MUST include an additional <submission-id> element in the <mix> element of the message copy going back to the originator's bare JID. The <submission-id> element holds the original id provided by the sender. This enables the originator to correlate the received message with the message submitted.
Besides correlating for the sender (the actual resource that sent it), it *also* allows your other resources to see that it was a message from your account. I assume this will also be stored as such in the user's own MAM archive.
For retrieval from the MAM archive of the channel itself, you'd still need to recognize your own Stable Participant ID, but that seems like a bit of an edge case.
I think it would be useful if on join the MIX channel could communicate our participant ID back to us and then PAM could put it in the roster as a child of the MIX annotation.
Example 18 (XEP-0369) shows that the join response includes the `id` attribute to hold the Stable Participant ID. A similar `id` attribute on the roster child should suffice:
<item jid='[email protected]'> <channel xmlns='urn:xmpp:mix:roster:0' id='123456'/> </item> -- ralphm _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
