From d0f3a49b08cdc95c11ccb5f5dd530bbf1dceb11d Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Tue, 2 Jan 2018 10:12:12 +0000 Subject: [PATCH] Allow server to limit retract timeframe --- xep-0369.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/xep-0369.xml b/xep-0369.xml index 160bc984..9e116c88 100644 --- a/xep-0369.xml +++ b/xep-0369.xml @@ -47,6 +47,7 @@ Joining Channel Clarification, Coming online clarification, Going offline JID error, + Allow servers to limit retract time frame,

@@ -1745,7 +1746,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa

- A MIX channel MAY support message retraction, where the sender of a messages or an authorized administrator deletes a message. If this is done the original message MAY be replaced by a tombstone. The protocol to request retraction does this by adding to the message a <retract> element qualified by the 'urn:xmpp:mix:1' namespace. The <retract> element MUST include an <id> attribute that holds the id of the original message. A message and it's retraction shown in the following example. + A MIX channel MAY support message retraction, where the sender of a messages or an authorized administrator deletes a message. A MIX channel MAY limit the time frame in which a message is allowed to be retracted, for example to prevent retraction of very old messages. If this is done the original message MAY be replaced by a tombstone. The protocol to request retraction does this by adding to the message a <retract> element qualified by the 'urn:xmpp:mix:1' namespace. The <retract> element MUST include an <id> attribute that holds the id of the original message. A message and it's retraction shown in the following example.