Version 1.0.1 of XEP-0388 (Extensible SASL Profile) has been released.
Abstract:
This document describes a replacement for the SASL profile documented
in RFC 6120 which allows for greater extensibility.
Changelog:
Fixed typos (md)
URL: https://xmpp.org/extensions/xep-0388.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, April 23
2024 at 16:00 UTC in xmpp:council@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* STABLE: XEP-0334 (Message Processing Hints)
* STABLE: XEP-0333 (Displayed Markers)
4) Items for voting
a) Issue Last Call on 'XEP-0421: Anonymous unique occupant identifiers for MUCs'
5) Pending votes
Marvin on
* XEP-0388: Fix typo (PR) (Expires today)
* Move 'XEP-0398 (User Avatar to vCard-Based Avatars Conversion)' to stable
* Issue Last Call on 'XEP-0440: SASL Channel-Binding Type Capability'
See the spreadsheet of Doom:
https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa…
6) Date of Next
7) AOB
8) Close
Version 1.0.0 of XEP-0334 (Message Processing Hints) has been
released.
Abstract:
This document defines a way to include hints to entities routing or
receiving a message.
Changelog:
Accept as Stable as per Council Vote from 2024-04-17 (XEP Editor (dg))
URL: https://xmpp.org/extensions/xep-0334.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Version 1.0.0 of XEP-0333 (Displayed Markers) has been released.
Abstract:
This specification introduces a method to let the sender, or multiple
participants in a group chat, know that a client has displayed
messages up to a certain point.
Changelog:
Accept as Stable as per Council Vote from 2024-04-17. (XEP Editor
(dg))
URL: https://xmpp.org/extensions/xep-0333.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Hi,
Some feedback while trying to implement these XEPs
XEP-0424
1)
The schema mentions
<xs:attribute name='by' type='xs:string' use='optional'/>
But the XEP does not mention the attribute, what is the purpose?
2)
> When replacing the original message with a tombstone, the original contents (i.e. the <body/> and any related elements which might leak information about the original message) get replaced with a <retracted/> element which MUST include an 'id' attribute referring to the original message
Why does the element MUST have an id attribute? its a element inside the <message> which already has the id, or in case of groupchat its inside a mam wrapper which has a stanza id, in all cases its perfectly clear that the retracted element belongs to the actual message wrapping it, maybe im missing something obvious here but i dont see a need for this id attribute at all.
Example 7
> For messages of type 'groupchat', the stanza's Unique and Stable Stanza IDs (XEP-0359) <https://xmpp.org/extensions/xep-0359.html> [4 <https://xmpp.org/extensions/xep-0424.html#nt-idm41385450875712>] 'origin ID' MUST NOT be used for retractions
Example mentions origin-id in groupchat context
<message type="groupchat" from="romeo(a)montague.example" to="lord(a)capulet.example" id="wrong-recipient-1">
<retracted stamp='2019-09-20T23:09:32Z' xmlns='urn:xmpp:message-retract:1' id='origin-id-1'/>
</message>
XEP-0425
1)
> A Message Archive Management (XEP-0313) <https://xmpp.org/extensions/xep-0313.html> [6 <https://xmpp.org/extensions/xep-0425.html#nt-idm34711750431632>] service MAY replace the contents of a message, that was retracted due to moderation, with a 'tombstone' similar to the one described in Message Retraction (XEP-0424) <https://xmpp.org/extensions/xep-0424.html> [5 <https://xmpp.org/extensions/xep-0425.html#nt-idm34711750445088>].
How similiar? The tombstone text does not mention seemingly important MUST rules from XEP 0424
For example
> Some clients may have been offline while the retraction was issued. The archiving service therefore MUST store the retraction message, regardless of whether the original message is deleted or replaced with a tombstone.
the above mentioned MUST rule about the id attribute in the <retracted> element, seems to be not important anymore in moderation, at least the id attribute is not found anymore in the tombstone.
Im not saying we need to copy text 1:1 between the XEPs, but should the XEP not go into more detail what exactly the differences are, and what exactly from 0424 applies?
Thanks
Regards
Philipp
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, April 16
2024 at 16:00 UTC in xmpp:council@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
Minor updates to XEP-0444 (Message Reactions) and XEP-0440 (Channel Binding)
4) Items for voting
a) Move 'LAST CALL: XEP-0398 (User Avatar to vCard-Based Avatars
Conversion)' to stable
b) Issue Last Call on 'XEP-0440: SASL Channel-Binding Type Capability'
5) Pending votes
Marvin on
* Move 'XEP-0334 (Message Processing Hints)' to stable
* Move 'XEP-0333 (Displayed Markers)' to stable
* XEP-0388: Fix typo (PR)
See the spreadsheet of Doom:
https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa…
6) Date of Next
7) AOB
8) Close
Version 0.2.1 of XEP-0444 (Message Reactions) has been released.
Abstract:
This specification defines a way for adding reactions to a message.
Changelog:
fix grammar and spelling (wb)
URL: https://xmpp.org/extensions/xep-0444.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Version 0.4.1 of XEP-0440 (SASL Channel-Binding Type Capability) has
been released.
Abstract:
This specification allows servers to annouce their supported SASL
channel-binding types to clients.
Changelog:
Recommend the usage of tls-exporter over tls-server-end-point
(fs)
URL: https://xmpp.org/extensions/xep-0440.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Good morning Council Members,
the next XMPP Council Meeting will take place today on, Tuesday, April
9 2024 at 16:00 UTC in xmpp:council@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
* STABLE: XEP-0386 (Bind 2)
* STABLE: XEP-0388 (Extensible SASL Profile)
* UPDATED: XEP-0333 (Displayed Markers)
4) Items for voting
a) Move 'XEP-0334 (Message Processing Hints)' to stable
b) Move 'XEP-0333 (Displayed Markers)' to stable
c) XEP-0388: Fix typo https://github.com/xsf/xeps/pull/1338
5) Pending votes
none
See the spreadsheet of Doom:
https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa…
6) Date of Next
Version 0.7.0 of XEP-0333 (Displayed Markers) has been released.
Abstract:
This specification introduces a method to let the sender, or multiple
participants in a group chat, know that a client has displayed
messages up to a certain point.
Changelog:
* Change title to "Displayed Markers"
* Bring back Service Discovery feature (dg)
URL: https://xmpp.org/extensions/xep-0333.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
