November 2024 - Standards

by Daniel Gultsch

The XMPP Extensions Editor has received a proposal for a new XEP. Title: MUC Slow Mode Abstract: This specification describes a way to rate limit messages a single user can send to a MUC room. It includes room configuration option, and how servers and clients can handle such a feature. URL: https://xmpp.org/extensions/inbox/xep-slow-mode.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

3 weeks, 4 days

6
12
0 0

XEP-0163 (Personal Eventing Protocol) Allow multiple publishers; XEP-0045 (Multi-User Chat) Allow PEP

by Schimon Jehudah

Good day! I am the developer of Slixfeed news bot, which is a syndication feed reader (Atom/RDF/RSS). This matter is also related to Morbot. See https://codeberg.org/TheCoffeMaker/Morbot/issues/13 Concern ------- I have to attempted experiment with PEP nodes, and my attempt has failed due to: XEP-0045 service-unavailable The feature requested is not supported by the conference XEP-0163 forbidden You're not allowed to create nodes Proposal -------- I suggest to enable PEP nodes for MUC JIDs too. I suggest to change the approach "One publisher per node.". See https://xmpp.org/extensions/xep-0163.html#approach-publisher > There is no need for multiple publishers to a PEP service, since by > definition the service generates information associated with only one > entity. The owner-publisher for every node is the bare JID of the > account owner. In order to allow a secondary "channel" interface for people and group chats, and also for other reasons (see further), it would be useful to: 1) Allow multiple publishers. 2) Allow PEP for MUC JIDs. By a "channel" interface, I mean, that should a news bot be included for a group chat, the updates would be sent to a PEP node of the group chat JID instead to the chat itself, which would keep the chat view cleaner. Example use cases: Number #3 represents the use of Morbot and Slixfeed, and is useful for forwarding of news journals. 1) Use : Inbox Affiliation : Publish-Only Publishers : JIDs which Presence is shared with or in Roster 2) Use : Collaboration (e.g. Pad, Whiteboard etc.) Affiliation : Publisher Publishers : Determined manually 3) Use : Updates Affiliation : Publish-Only Publishers : Determined manually Note ---- Slixfeed can use its own PEP nodes named after its subscribers respectively, albeit that would be more demanding on the server of which Slixfeed is operated on, than publishing to PEP nodes of other JIDs, and yet it would not be practical for group chat JIDs, which the bot also supports. Please advise. Kind regards, Schimon

3 weeks, 6 days

4
13
0 0

NEW: XEP-0500 (MUC Slow Mode)

by Daniel Gultsch

Version 0.1.0 of XEP-0500 (MUC Slow Mode) has been released. Abstract: This specification describes a way to rate limit messages a single user can send to a MUC room. It includes room configuration option, and how servers and clients can handle such a feature. Changelog: Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0500.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 month, 1 week

1
0
0 0

UPDATED: XEP-0490 (Message Displayed Synchronization)

by Daniel Gultsch

Version 1.0.1 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: * Fix some examples, and their indentation. * Add the XML Schema. (egp) 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 month, 1 week

1
0
0 0

XMPP Council Agenda 2024-11-22

by Daniel Gultsch

Good morning newly elected Council the first XMPP Council Meeting will take place on, Tuesday, November 26 2024 at 16:30 UTC in xmpp:council@muc.xmpp.org?join The Agenda is as follows: 1) Roll call 2) Agenda Bashing 3) Elect new Chair 4) Editors update * NEW: XEP-0496 (Pubsub Node Relationships) * NEW: XEP-0497 (Pubsub Extended Subscriptions) * NEW: XEP-0498 (Pubsub File Sharing) * NEW: XEP-0499 (Pubsub Extended Discovery) * Proposed XMPP Extension: MUC Slow Mode 5) Items for voting a) XEP-0490: Add the XML Schema and fix some examples https://github.com/xsf/xeps/pull/1400 b) Proposed XMPP Extension: MUC Slow Mode https://xmpp.org/extensions/inbox/xep-slow-mode.html c) Make Daniel (co-)author of 'XEP-0343: Signaling WebRTC datachannels in Jingle' https://xmpp.org/extensions/xep-0343.html 6) Pending votes none yet Here is the all new spreadsheet: https://docs.google.com/spreadsheets/d/1oAHUqBdlkobDcmfQ-YRMfZHGQLMWEdOFuEU… 7) Date of Next 8) AOB 9) Close P.S.: This is the first council email that does not get send to the council mailing list. The previous council has decided to get rid of that list and only use 'standards'.

1 month, 1 week

1
0
0 0

NEW: XEP-0499 (Pubsub Extended Discovery)

by Daniel Gultsch

Version 0.1.0 of XEP-0499 (Pubsub Extended Discovery) has been released. Abstract: This specification extends the discovery requests used with the XMPP PubSub protocol by introducing mechanisms to discover linked nodes, descendants, or metadata. Changelog: Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0499.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 month, 2 weeks

1
0
0 0

NEW: XEP-0498 (Pubsub File Sharing)

by Daniel Gultsch

Version 0.1.0 of XEP-0498 (Pubsub File Sharing) has been released. Abstract: This specification explains how to share files and optionally include directory structures similar to filesystems over XMPP Pubsub. It leverages XMPP Pubsub to enable notifications about file changes and manage permissions, providing users with real-time updates and control mechanisms. An optional mechanism is also specified for managing uploaded files. Changelog: Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0498.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 month, 2 weeks

1
0
0 0

NEW: XEP-0497 (Pubsub Extended Subscriptions)

by Daniel Gultsch

Version 0.1.0 of XEP-0497 (Pubsub Extended Subscriptions) has been released. Abstract: This specification extends the XMPP PubSub protocol by introducing mechanisms for users to subscribe to an entire node hierarchy or to receive notifications on node metadata updates. Changelog: Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0497.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 month, 2 weeks

1
0
0 0

NEW: XEP-0496 (Pubsub Node Relationships)

by Daniel Gultsch

Version 0.1.0 of XEP-0496 (Pubsub Node Relationships) has been released. Abstract: This specification describes how to establish links between pubsub nodes, allowing for optional hierarchical organization. Changelog: Promoted to Experimental (XEP Editor: dg) URL: https://xmpp.org/extensions/xep-0496.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 month, 2 weeks

1
0
0 0

PSA: Change your CSI implementations to let PEP notifications from the account through

by Daniel Gultsch

Hi, TLDR: It is common practice for CSI (Client State Indication) implementations to withhold (and deduplicate) PEP notifications and/or headline messages. Due to the rise of XEPs such as Message Displayed Synchronization (MDS) those implementations need to be changed to immediately let through PEP notifications from nodes that are on the account itself. I noticed the MDS problem in theory a while ago but didn’t care too much because due to a lack of implementations I’m not using MDS on a daily basis. (MDS needs to be able to dismiss notifications even if the client is in background) However today I ran into a related problem with Bookmarks 2 and User Nickname. I was writing code that actually performs a rename in a MUC if the desired nick changes (either pulled from the bookmark or if that one is unset from XEP-0172) instead of only using these sources on initial join. I think it is somewhat obvious that the rename should be done fairly instantly on all clients once a client has made the change (either to the bookmark or to 0172). Otherwise other users would see the user as being joined multiple times with different nicks until all clients have come to the foreground. I guess letting through all PEP notifications from the account (instead of allow listing certain nodes) is good enough. That’s beneficial for Nick, Bookmarks, OMEMO. The only one for which we technically don’t need it is Avatar. But how often do you change that one (meaning how many false positives would you generate?!) cheers Daniel

1 month, 3 weeks

1
0
0 0

2025

2024

2023

Standards November 2024

2025

2024

2023

Standards November 2024 ----- 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 November 2024