From 07342d5fbac4685db610df887dc831d3355e8852 Mon Sep 17 00:00:00 2001 From: Matthew Wild Date: Wed, 15 Apr 2020 12:55:48 +0100 Subject: [PATCH] XEP-0333: Add notes about usage within MUCs --- xep-0333.xml | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) diff --git a/xep-0333.xml b/xep-0333.xml index 86582e12..16fee66f 100644 --- a/xep-0333.xml +++ b/xep-0333.xml @@ -30,6 +30,12 @@ im@spencermacdonald.com im@spencermacdonald.com + + 0.4 + 2020-04-15 + mw + Add notes about usage within MUCs. + 0.3 2017-09-11 @@ -236,6 +242,51 @@

Chat Markers MAY be used alongside Chat States.

 + +

Markers may be used within a MUC to indicate read status of each occupant.

+

Within the context of a MUC messages are relayed through the MUC's own JID. In a + MUC that preserves the 'id' attribute chosen by the sender of the message this + 'id' attribute cannot be considered unique, as it may be unintentionally or + even maliciously reused by another MUC occupant.

+ +

Therefore, if a MUC announces support for &xep0359; then clients MUST always use + the MUC-assigned id for Chat Markers. The id will be contained in a <stanza-id> + element inserted into the stanza with a 'by' attribute matching the MUC's own JID.

+ +

As per XEP-0359 security considerations, clients MUST only trust a <stanza-id> + element with a 'by' attribute that matches the MUC's own JID, and MUST ignore any such + element in MUCs that do not announce XEP-0359 support.

+ + + + Act IV, Scene I + Thrice the brinded cat hath mew'd. + + + +]]> + + + + + Act IV, Scene I + + +]]> + + +