From 0d6c8cc0c594dded04a7a40e6bdb01575559e837 Mon Sep 17 00:00:00 2001 From: JC Brand Date: Sun, 19 Feb 2023 09:10:22 +0100 Subject: [PATCH] XEP-0424: Remove dependency on XEP-0422 'Message Fastening' --- xep-0424.xml | 31 +++++++++++++++++-------------- 1 file changed, 17 insertions(+), 14 deletions(-) diff --git a/xep-0424.xml b/xep-0424.xml index 9fb71c043..d0b39f3bc 100644 --- a/xep-0424.xml +++ b/xep-0424.xml @@ -20,13 +20,18 @@ XMPP IM XEP-0313 XEP-0421 - XEP-0422 message-retract &lance; &jcbrand; + + 1.0.0 + 2023-02-19 + jcb + Remove the dependency on XEP-0422 Message Fastening + 0.3.0 2020-05-17 @@ -86,8 +91,8 @@

Due to the federated and extensible nature of XMPP it's not possible to remove a message with full certainty and a retraction can only be considered an unenforceable request for such removal. Clients which don't support message retraction are not obligated to enforce the request and people could have seen or copied the message contents already.

-

If a client implements message retractions, it MUST specify the 'urn:xmpp:message-retract:0' feature in its service discovery information features as specified in &xep0030; and the Entity Capabilities profile specified in &xep0115;.

-

Similarly, a server that is aware of message retractions and will therefore ensure that they're archived for later retrieval (e.g.via &xep0313;), MUST also advertise the 'urn:xmpp:message-retract:0' feature.

+

If a client implements message retractions, it MUST specify the 'urn:xmpp:message-retract:1' feature in its service discovery information features as specified in &xep0030; and the Entity Capabilities profile specified in &xep0115;.

+

Similarly, a server that is aware of message retractions and will therefore ensure that they're archived for later retrieval (e.g.via &xep0313;), MUST also advertise the 'urn:xmpp:message-retract:1' feature.

... - + ... ]]> @@ -120,9 +125,7 @@ - - - + This person attempted to retract a previous message, but it's unsupported by your client. @@ -136,7 +139,7 @@

It might be desirable to remove the retracted message from a &xep0313; service, while still recording the fact that it once existed, in order to aid clients in synchronizing their archives. To do this, the archiving service MAY replace the retracted message contents with a 'tombstone'.

-

A service which supports tombstones MUST advertise the 'urn:xmpp:message-retract:0#tombstone' feature in its Service Discovery responses.

+

A service which supports tombstones MUST advertise the 'urn:xmpp:message-retract:1#tombstone' feature in its Service Discovery responses.

... - + ... ]]> @@ -167,7 +170,7 @@ - + @@ -195,9 +198,9 @@ -

The ®ISTRAR; includes 'urn:xmpp:message-retract:0' in its registry of protocol namespaces (see &NAMESPACES;).

+

The ®ISTRAR; includes 'urn:xmpp:message-retract:1' in its registry of protocol namespaces (see &NAMESPACES;).

    -
  • urn:xmpp:message-retract:0
    • +
  • urn:xmpp:message-retract:1
 @@ -210,8 +213,8 @@