14 Oct
2025
14 Oct
'25
6:26 a.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
2025-10-28.
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!
14 Oct
14 Oct
6:30 a.m.
Hi
during Last Call council had some feedback that was addressed but then
it never got added to the agenda again.
With my editor hat on I’m extending the Last Call to two weeks from now.
cheers
Daniel
On Tue, Oct 14, 2025 at 12:26 PM 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
2025-10-28.
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!
7:50 a.m.
Hello all,
1. Is this specification needed to fill gaps in the
XMPP protocol
stack or to clarify an existing protocol?
Yes.
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 implemented it in slidge-based gateways (not tombstones though), and
it works just fine with clients that support it AFAICT.
4. Do you have any security concerns related to this
specification?
No.
5. Is the specification accurate and clearly written?
Yes.
As with all other message-referencing XEPs, understanding the
differences between different IDs in different contexts (1:1 or groups)
can be overwhelming for implementers. But I just re-read XEP-0424 and I
think it is clear enough in here though.
Regards,
-- Nicolas
29
days inactive
29
days old
2 comments
2 participants
participants (2)
-
Daniel Gultsch -
Nicolas Cedilnik