3 Jul
2026
3 Jul
'26
2:15 p.m.
This message constitutes notice of a Last Call for comments on
XEP-0424.
Title: Message Retraction
Abstract:
This specification defines a method for indicating that a message
should be retracted.
URL: https://xmpp.org/extensions/xep-0424.html
This Last Call begins today and shall end at the close of business on
2026-07-20.
Please consider the following questions during this Last Call and send
your feedback to the standards(a)xmpp.org discussion list:
1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?
2. Does the specification solve the problem stated in the introduction
and requirements?
3. Do you plan to implement this specification in your code? If not,
why not?
4. Do you have any security concerns related to this specification?
5. Is the specification accurate and clearly written?
Your feedback is appreciated!
8 Jul
8 Jul
11:28 a.m.
On 7/3/26 14:15, Daniel Gultsch wrote:
This message constitutes notice of a Last Call for
comments on
XEP-0424.
Title: Message Retraction
Abstract:
This specification defines a method for indicating that a message
should be retracted.
URL:https://xmpp.org/extensions/xep-0424.html
This Last Call begins today and shall end at the close of business on
2026-07-20.
Please consider the following questions during this Last Call and send
your feedback to thestandards(a)xmpp.org discussion list:
Disclosure, I'm one of the authors of the XEP.
1. Is this specification needed to fill gaps in the
XMPP protocol
stack or to clarify an existing protocol?
Yes. Even if retractions cannot be guaranteed in an open, federated
network, they do still indicate intent.
And in closed deployments they can be fully implemented and enforced.
2. Does the specification solve the problem stated in
the introduction
and requirements?
Yes
3. Do you plan to implement this specification in your
code? If not,
why not?
I've implemented it in Converse.
4. Do you have any security concerns related to this
specification?
Nothing beyond what's documented already.
5. Is the specification accurate and clearly written?
Yes.
25 Aug
25 Aug
11:38 a.m.
A quick reminder that this Last Call is running. We saw very little
feedback but council would like to vote on that soon. Please provide
your feedback even if brief.
12:57 p.m.
1. Is this specification needed to fill gaps in the
XMPP protocol
stack or to clarify an existing protocol?
No
2. Does the specification solve the problem stated in
the introduction
and requirements?
Yes
3. Do you plan to implement this specification in your
code? If not,
why not?
No. Message correction suffices and is more flexible.
4. Do you have any security concerns related to this
specification?
No
5. Is the specification accurate and clearly written?
Yes
2:17 p.m.
On Fri, 3 Jul 2026 at 08:16, Daniel Gultsch <daniel(a)gultsch.de> wrote:
This message constitutes notice of a Last Call for
comments on
XEP-0424.
Title: Message Retraction
Abstract:
This specification defines a method for indicating that a message
should be retracted.
URL: https://xmpp.org/extensions/xep-0424.html
This Last Call begins today and shall end at the close of business on
2026-07-20.
Please consider the following questions during this Last Call and send
your feedback to the standards(a)xmpp.org discussion list:
1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?
Yes. Though I would very likely implement the client UX by showing the
original message in strikethrough, rather than actually removing it, I
think the clear semantic is better than LMC performing the same edit.
2. Does the specification solve the problem stated in
the introduction
and requirements?
Seems to.
3. Do you plan to implement this specification in your
code? If not,
why not?
I have no immediate plans, but would implement it if I saw it in use, or if
users wanted it.
4. Do you have any security concerns related to this
specification?
Nope
5. Is the specification accurate and clearly written?
Yup.
Your feedback is appreciated!
_______________________________________________
Standards mailing list -- standards(a)xmpp.org
To unsubscribe send an email to standards-leave(a)xmpp.org
0
days inactive
53
days old
4 comments
4 participants
participants (4)
-
Daniel Gultsch -
Dave Cridland -
JC Brand -
Stephen Paul Weber