From a3dc32643c33282f474568f2100779f93a111deb Mon Sep 17 00:00:00 2001 From: Kevin Smith Date: Fri, 8 Mar 2019 14:32:37 +0000 Subject: [PATCH] Clarify correcting a message multiple times --- xep-0308.xml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/xep-0308.xml b/xep-0308.xml index 92a7cb74..d76dda84 100644 --- a/xep-0308.xml +++ b/xep-0308.xml @@ -21,6 +21,12 @@ message-correct &ksmith; + + 1.1 + 2019-03-08 + kis +

Clear up confusion about subsequent corrections and ids (it's the payloads getting replaced, not the message identity).

 + 1.0 2013-04-08 @@ -98,6 +104,7 @@

A single message may be corrected multiple times by subsequent edits.

A correction MUST only be allowed when both the original message and correction are received from the same full-JID.

While it's not possible to prevent this protocol from being used in such a way, it is not intended that it provides a way to continue expanding a previous message indefinitely and clients, in as much as it is sensible, should present use of this extension only for correction rather than for providing a continuous stream, for which &xep0301; can be used instead.

+

If the same message is to be corrected several times, the id of the original message is used in each case (e.g. If a message of id 1 is corrected by a message of id 2, a subsequent correction should correct 1, not 2).

Correction MUST only be used to change the details of a stanza (e.g. the message body) and not to change the nature of the stanza (e.g. correction MUST NOT be used to turn a chat message into a pubsub notification)

While it is possible to use this protocol to correct messages older than the most recent received from a full JID, such use is out of scope for this document and support for this SHOULD NOT be assumed without further negotiation.