- Standards

LAST CALL: XEP-0398 (User Avatar to vCard-Based Avatars Conversion)
by Daniel Gultsch 02 Apr '24

02 Apr '24

This message constitutes notice of a Last Call for comments on XEP-0398. Title: User Avatar to vCard-Based Avatars Conversion Abstract: This specification describes a method for using PEP based avatars and vCard based avatars in parallel by having the user’s server do a conversion between the two. URL: https://xmpp.org/extensions/xep-0398.html This Last Call begins today and shall end at the close of business on 2024-04-14. 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!

1 0

UPDATED: XEP-0424 (Message Retraction)
by Daniel Gultsch 28 Mar '24

28 Mar '24

Version 0.4.1 of XEP-0424 (Message Retraction) has been released. Abstract: This specification defines a method for indicating that a message should be retracted. Changelog: * Fix schema. * Add missing for attribute in fallback element (Example 4). (nc) URL: https://xmpp.org/extensions/xep-0424.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.

1 0

STABLE: XEP-0392 (Consistent Color Generation)
by Daniel Gultsch 27 Mar '24

27 Mar '24

Version 1.0.0 of XEP-0392 (Consistent Color Generation) has been released. Abstract: This specification provides a set of algorithms to consistently generate colors given a string. The string can be a nickname, a JID or any other piece of information. All entities adhering to this specification generate the same color for the same string, which provides a consistent user experience across platforms. Changelog: Accept as Stable as per Council Vote from 2024-03-27. (XEP Editor (dg)) URL: https://xmpp.org/extensions/xep-0392.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.

1 0

REJECT: XEP-0360 (Nonzas (are not Stanzas))
by Daniel Gultsch 27 Mar '24

27 Mar '24

Version 0.2 of XEP-0360 (Nonzas (are not Stanzas)) has been released. Abstract: This specification defines the term "Nonza", describing every top level stream element that is not a Stanza. Changelog: Defer due to lack of activity. (XEP Editor (jwi)) URL: https://xmpp.org/extensions/xep-0360.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.

1 0

LAST CALL: XEP-0392 (Consistent Color Generation)
by Daniel Gultsch 26 Mar '24

26 Mar '24

This message constitutes notice of a Last Call for comments on XEP-0392. Title: Consistent Color Generation Abstract: This specification provides a set of algorithms to consistently generate colors given a string. The string can be a nickname, a JID or any other piece of information. All entities adhering to this specification generate the same color for the same string, which provides a consistent user experience across platforms. URL: https://xmpp.org/extensions/xep-0392.html This Last Call begins today and shall end at the close of business on 2024-03-25. 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!

3 4

UPDATED: XEP-0333 (Displayed Markers (was: Chat Markers))
by Daniel Gultsch 26 Mar '24

26 Mar '24

Version 0.5.0 of XEP-0333 (Displayed Markers (was: Chat 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: * Remove <received/> to not replicate functionality. * Remove <acknowledged/> because it was not implemented in the last 10 years and apparently is not needed. * Remove Disco feature. Opting in via <markable/> is enough (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.

3 5

LAST CALL: XEP-0333 (Displayed Markers (was: Chat Markers))
by Daniel Gultsch 26 Mar '24

26 Mar '24

This message constitutes notice of a Last Call for comments on XEP-0333. Title: Displayed Markers (was: Chat Markers) 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. URL: https://xmpp.org/extensions/xep-0333.html This Last Call begins today and shall end at the close of business on 2024-04-08. 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!

3 3

NEW: XEP-0490 (Message Displayed Synchronization)
by Daniel Gultsch 26 Mar '24

26 Mar '24

Version 0.1.0 of XEP-0490 (Message Displayed Synchronization) has been released. Abstract: This specification allows multiple clients of the same user to synchronize the displayed state of their chats. Changelog: * Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0490.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.

1 0

XMPP Council Agenda 2024-03-26
by Daniel Gultsch 25 Mar '24

25 Mar '24

Good morning Council Members, the next XMPP Council Meeting will take place on, Tuesday, March 26 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 * LAST CALL: XEP-0333 (Displayed Markers (was: Chat Markers)) * LAST CALL: XEP-0334 (Message Processing Hints) * Message Processing Hints, Displayed markers and Extensible SASL Profile received updates 4) Items for voting a) Move to Stable / Move to Rejected 'XEP-0360 (Nonzas (are not Stanzas))' b) Move to Stable / Move to Rejected 'XEP-0392 (Consistent Color Generation)' 5) Pending votes * Dan on 'Proposed XMPP Extension: Message Displayed Synchronization' * Dan on 'Issue Last Call on XEP-0398: User Avatar to vCard-Based Avatars Conversion' See the spreadsheet of Doom: https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa… 6) Date of Next 7) AOB 8) Close

1 0

LAST CALL: XEP-0334 (Message Processing Hints)
by Daniel Gultsch 25 Mar '24

25 Mar '24

This message constitutes notice of a Last Call for comments on XEP-0334. Title: Message Processing Hints Abstract: This document defines a way to include hints to entities routing or receiving a message. URL: https://xmpp.org/extensions/xep-0334.html This Last Call begins today and shall end at the close of business on 2024-04-08. 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!

1 0