- Standards

by Daniel Gultsch

Version 2.13.2 of XEP-0004 (Data Forms) has been released. Abstract: This specification defines an XMPP protocol extension for data forms that can be used in workflows such as service configuration as well as for application-specific data description and reporting. The protocol includes lightweight semantics for forms processing (such as request, response, submit, and cancel), defines several common field types (boolean, list options with single or multiple choice, text with single line or multiple lines, single or multiple JabberIDs, hidden fields, etc.), provides extensibility for future data types, and can be embedded in a wide range of applications. The protocol is not intended to provide complete forms-processing functionality as is provided in the W3C XForms technology, but instead provides a basic subset of such functionality for use by XMPP entities. Changelog: Add section on empty and absent values. (gk) URL: https://xmpp.org/extensions/xep-0004.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.

6 months, 2 weeks

1
0
0 0

XMPP Council Agenda 2024-09-17

by Daniel Gultsch

Good morning Council Members, the next XMPP Council Meeting will take place on, Tuesday, September 17 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 * UPDATED: XEP-0133 (Service Administration) * UPDATED: XEP-0474 (SASL SCRAM Downgrade Protection) * UPDATED: XEP-0045 (Multi-User Chat) * UPDATED: XEP-0272 (Multiparty Jingle (Muji)) * NEW: XEP-0493 (OAuth Client Login) * NEW: XEP-0494 (Client Access Management) 4) Items for voting a) XEP-0004: Empty and absent values https://github.com/xsf/xeps/pull/1387 b) XEP-0264: Restrict 'width' and 'height' to the 0..65535 range https://github.com/xsf/xeps/pull/1366 c) XEP-0198: Clarify server enabling SM without requested resumption https://github.com/xsf/xeps/pull/1376 d) XEP-0313: Fix MUC archive example https://github.com/xsf/xeps/pull/1321 5) Pending votes None See the spreadsheet of Doom: https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa… 6) Date of Next 7) AOB 8) Close

6 months, 2 weeks

1
0
0 0

UPDATED: XEP-0272 (Multiparty Jingle (Muji))

by Daniel Gultsch

Version 0.2.0 of XEP-0272 (Multiparty Jingle (Muji)) has been released. Abstract: This specification defines an XMPP protocol extension for initiating and managing multiparty voice and video conferences within an XMPP MUC Changelog: * Send Jingle IQs to real JID * Define how to use with XEP-0482 * Adjust namespace (lmw) URL: https://xmpp.org/extensions/xep-0272.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.

6 months, 2 weeks

1
0
0 0

UPDATED: XEP-0045 (Multi-User Chat)

by Daniel Gultsch

Version 1.35.1 of XEP-0045 (Multi-User Chat) has been released. Abstract: This specification defines an XMPP protocol extension for multi-user text chat, whereby multiple XMPP users can exchange messages in the context of a room or channel, similar to Internet Relay Chat (IRC). In addition to standard chatroom features such as room topics and invitations, the protocol defines a strong room control model, including the ability to kick and ban users, to name room moderators and administrators, to require membership or passwords in order to join the room, etc. Changelog: Add explicit error definition when non-owners attempt to use owner- specific functionality. (gk) URL: https://xmpp.org/extensions/xep-0045.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.

6 months, 2 weeks

1
0
0 0

NEW: XEP-0494 (Client Access Management)

by Daniel Gultsch

Version 0.1.0 of XEP-0494 (Client Access Management) has been released. Abstract: This specification details how an XMPP account owner can view and control which applications and services have access to their account. Changelog: * Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0494.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.

6 months, 2 weeks

1
0
0 0

NEW: XEP-0493 (OAuth Client Login)

by Daniel Gultsch

Version 0.1.0 of XEP-0493 (OAuth Client Login) has been released. Abstract: This specification details how a third-party can be securely granted access to an XMPP account without exposing the account credentials, using OAuth. Changelog: * Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0493.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.

6 months, 2 weeks

1
0
0 0

UPDATED: XEP-0474 (SASL SCRAM Downgrade Protection)

by Daniel Gultsch

Version 0.3.1 of XEP-0474 (SASL SCRAM Downgrade Protection) has been released. Abstract: This specification provides a way to secure the SASL and SASL2 handshakes against method and channel-binding downgrades. Changelog: * Fix typos * Adapt attack-model section to new simplified protocol (tm) URL: https://xmpp.org/extensions/xep-0474.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.

6 months, 2 weeks

1
0
0 0

UPDATED: XEP-0133 (Service Administration)

by Daniel Gultsch

Version 1.3.1 of XEP-0133 (Service Administration) has been released. Abstract: This document defines recommended best practices for service-level administration of servers and components using Ad-Hoc Commands. Changelog: Fixed typo in example for Get User Last Login Time (dc) URL: https://xmpp.org/extensions/xep-0133.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.

6 months, 2 weeks

1
0
0 0

XSF membership application period Q4 2024

by Alexander Gnauck

I have setup the membership application Wiki page for the application period Q4 2024 Applications are encouraged from developers and others who are actively involved in the Jabber/XMPP community. To apply, create a page about yourself on the Wiki at: https://wiki.xmpp.org/web/Membership_Applications_Q4_2024 If you don't have a wiki account, send your full name, preferred nickname and email address to me or one of the other Sysops: https://wiki.xmpp.org/web/Sysops Apply now!!! Thanks, Alex

6 months, 3 weeks

1
0
0 0

Atom Over XMPP (XEP-0277 and XEP-0472) classifying comments and reactions

by Schimon Jehudah

Good day! I am working on Rivista[1], which is a journal publisher for XMPP. I test instances of Libervia and Movim against Rivista. Most of the tests are conducted against the official instance of Movim. The matter of this message is concerning to Adding a Comment[2] (clause 3.2 to XEP-0277). I have noticed that "reactions" are manifested exactly the same as comments, inside element title. The couple of indications that a comment is a reaction are: 1) Element title has a single character; or 2) The character or character combination is included in the range of characters that are dedicated for reactions. I would suggest to use a classifier. 1) Use element title as a classifier of post type, either a comment or a reaction, and use element summary as a handler for the comment itself; or 2) Use element category (e.g. xmpp:comment and xmpp:reaction); or 3) Utilize "Extension Elements" (clause 6.4 to RFC 4287). I think that solution #3 would be the ideal solution. Current ------- <entry xmlns='http://www.w3.org/2005/Atom'> <author> <name>Juliet Capulet</name> <uri>xmpp:juliet@capulet.lit</uri> </author> <title type='text'>She is so pretty!</title> <published>2008-05-08T18:39:02Z</published> </entry> Title as an indicator --------------------- <entry xmlns='http://www.w3.org/2005/Atom'> <author> <name>Juliet Capulet</name> <uri>xmpp:juliet@capulet.lit</uri> </author> <title type='text'>comment</title> <summary type='text'>She is so pretty!</summary> <published>2008-05-08T18:39:02Z</published> </entry> Category as an indicator ------------------------ <entry xmlns='http://www.w3.org/2005/Atom'> <author> <name>Juliet Capulet</name> <uri>xmpp:juliet@capulet.lit</uri> </author> <title type='text'>She is so pretty!</title> <category term='xmpp:comment'/> <published>2008-05-08T18:39:02Z</published> </entry> A dedicated extension --------------------- <feed xmlns="http://www.w3.org/2005/Atom" xmlns:reactions="http://xmpp.org/2024/reactions"> For comments:  <entry xmlns='http://www.w3.org/2005/Atom'> <author> <name>Juliet Capulet</name> <uri>xmpp:juliet@capulet.lit</uri> </author> <title type='text'>She is so pretty!</title> <reactions:reaction type="💡️"/> <reactions:reaction type="👍️"/> <published>2008-05-08T18:39:02Z</published> </entry> For posts:  <reactions:reaction type="✒️" count="10"/> <reactions:reaction type="💡️" count="2"/> <reactions:reaction type="👍️" count="5"/> Kind regards, Schimon [1]: https://git.xmpp-it.net/sch/Rivista [2]: https://xmpp.org/extensions/xep-0277.html#comment_add

7 months

1
2
0 0

2025

2024

2023

Standards

2025

2024

2023

Standards ----- 2025 ----- April 2025 March 2025 February 2025 January 2025 ----- 2024 ----- December 2024 November 2024 October 2024 September 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 ----- 2023 ----- December 2023

Standards