November 2025 - Standards

LAST CALL: XEP-0424 (Message Retraction)

by Daniel Gultsch

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-01-06. 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 month, 4 weeks

9
27
0 0

LAST CALL: XEP-0484 (Fast Authentication Streamlining Tokens)

by Daniel Gultsch

This message constitutes notice of a Last Call for comments on XEP-0484. Title: Fast Authentication Streamlining Tokens Abstract: This specification defines a token-based method to streamline authentication in XMPP, allowing fully authenticated stream establishment within a single round-trip. URL: https://xmpp.org/extensions/xep-0484.html This Last Call begins today and shall end at the close of business on 2025-01-27. 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!

8 months, 2 weeks

6
20
0 0

XEP-0045 muc#roomconfig_allowinvites in practise

by Stephen Paul Weber

Hello everyone, XEP-0045 is very quiet about how some of the options are to be interpreted. For muc#roomconfig_allowinvites there is only one normative line in the XEP, in the registry submission, which is "Whether to Allow Occupants to Invite Others" Now, it seems that ejabberd and Conversations have interpreted this to mean "whether to allow occupants *who wouldn't normally be able to invite otherwise* to invite other" which is to say, pretty much, in a members only room can members invite members. On means members invite members, off means only admin can (actually Conversations checks for moderator role not for admin...) This feels like the correct implementation to me given that you can't meaningfully restrict invitations to a pubilc MUC (you could block mediated invitations but we're moving away from those and they don't do anything special in a public MUC traditionally) and it seems like nonsense to ban admins from inviting members (since the admins can change this settings anyway?) Why it matters: currently Prosody does not implement this option at all, because it seemed from the descriptio to mean something nonsensical. So Prosody has (AFAICT) implemented the same thing as ejabberd and Conversations, but under a custom name to make it clear how it works. My proposal: change the one line of text in the XEP to instead read "Whether to Allow Members to Invite Others".

9 months

2
1
0 0

New ProtoXEP: Initial Authentication Pipelining

by Dave Cridland

Hello, I've sketched out a proposal to either allow, or improve (depending on how you think of it) the initiating entity's ability to pipeline authentication (as in, send it without having waited for stream features it's seen before). XEP-0484 (FAST) implies very strongly that this is possible anyway - and of course it is - but in its current form clients have to take it on faith that the stream features are unlikely to change. This has ramifications in how quickly clients are likely to take advantage of new features or new SASL mechanisms. As an example, a client which already supports channel bindings, and is using FAST with a pre-existing token, will not see the features of a server newly enabling channel binding until after the authentications has succeeded, thus "missing out" on switching to the better security. https://github.com/xsf/xeps/pull/1483 is, I think, the obvious way of tightening this up. This is a relatively minor problem, but I think this is a relatively lightweight solution. Comments are, of course, welcome. Dave.

9 months, 2 weeks

1
0
0 0

Extending the roster item element

by Thilo Molitor

Hi all! With XEP-0469: Bookmark Pinning and XEP-0492: Chat notification settings we now have two XEPs that allow syncing pinning and notification settings across clients on the same account using the <extensions/> element of XEP-0402: PEP Native Bookmarks. Unfortunately, this now means that normal 1:1 chats (that are synchronized as roster items) lag behind. I'm volunteering to write a XEP adding an <extensions/> element alongside the <group/> element to allow arbitrary extensions for roster items. This would bring 1:1 roster items on-par with bookmarks2 and immediately allow XEP-0492 and XEP-0469 to be applied to roster items as well. But before I start I want to ask especially the server developers on this list: would you consider implementing this? If the answer is no or "some day far far in the future", it might be worth to try to invent some other mechanism that could be deployed faster. In my opinion, however, extending the roster items is by far the most elegant and simplest solution. What do you think? -tmolitor

9 months, 2 weeks

9
14
0 0

UPDATED: XEP-0492 (Chat notification settings)

by Daniel Gultsch

Version 0.2.0 of XEP-0492 (Chat notification settings) has been released. Abstract: This document defines an XMPP protocol extension to synchronise per- chat notification settings across different clients. Changelog: * Rework the spec to use more of the Service Discovery Identities registry * Fix the XML schema * Move the <advanced/> element into the notification setting element * Bump the namespace (tm) URL: https://xmpp.org/extensions/xep-0492.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.

9 months, 2 weeks

1
0
0 0

STABLE: XEP-0485 (PubSub Server Information)

by Daniel Gultsch

Version 1.0.0 of XEP-0485 (PubSub Server Information) has been released. Abstract: This document defines a data format whereby basic information of an XMPP domain can be expressed and exposed over pub-sub. Changelog: * Accept as Stable as per Council Vote from 2025-11-11 (XEP Editor (dg)) URL: https://xmpp.org/extensions/xep-0485.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.

9 months, 2 weeks

1
0
0 0

Atom Activity Streams and Atom Over XMPP (XEP-0277 and XEP-0472)

by Schimon Jehudah

Good day. I have explored the "Atom Activity Streams" documents of Friendica. https://activitystrea.ms/specs/atom/1.0/ I have further added rendering capabilities to an RSS extension. https://greasyfork.org/scripts/465932-newspaper-syndication-feed-reader Proposal -------- Since Atom Activity Streams documents can be delivered as a single "atom:entry" element, as so with XMPP PubSub Node Items; then, it might be beneficial to mention "Atom Activity Streams" in the XEP specifications of Atom Over XMPP (XEP-0277 and XEP-0472). Rational -------- Even though, as it seems, an Atom Activity Streams document is, as with Atom Over XMPP, a single "atom:entry" element, with a couple of XML namespaces, this would stimulate people to: * Utilize XMPP PubSub Node Items in an independent fashion, without compiling an Atom Syndication Format document; and * Consider interoperability with Friendica and other platforms that produce Atom Activity Streams documents, and also Json Activity Streams documents, which Nostr utilizes. * Consider interoperability of projects with XMPP. * Motivate projects, such as Friendica to extend support of XMPP. XML Namespace ------------- The namespaces that are utilized by Friendica, and may be relevant, are: xmlns="http://www.w3.org/2005/Atom" xmlns:at="http://purl.org/atompub/tombstones/1.0" xmlns:activity="http://activitystrea.ms/spec/1.0/" xmlns:dfrn="http://purl.org/macgirvin/dfrn/1.0" xmlns:georss="http://www.georss.org/georss" xmlns:media="http://purl.org/syndication/atommedia" xmlns:ostatus="http://ostatus.org/schema/1.0" xmlns:poco="http://portablecontacts.net/spec/1.0" xmlns:statusnet="http://status.net/schema/api/1/" xmlns:thr="http://purl.org/syndication/thread/1.0" Sample ------ Herein attached an Atom Activity Streams document. Source: https://my-place.social/display/feed-item/107999490.atom https://my-place.social/display/1c9fc4fa-f51b9f6f654d0bd7-7c3a0251 https://piaille.fr/@movim/115519544289510132 Kind regards, Schimon

9 months, 3 weeks

2
5
0 0

UPDATED: XEP-0060 (Publish-Subscribe)

by Daniel Gultsch

Version 1.30.0 of XEP-0060 (Publish-Subscribe) has been released. Abstract: This specification defines an XMPP protocol extension for generic publish-subscribe functionality. The protocol enables XMPP entities to create nodes (topics) at a pubsub service and publish information at those nodes; an event notification (with or without payload) is then broadcasted to all entities that have subscribed to the node. Pubsub therefore adheres to the classic Observer design pattern and can serve as the foundation for a wide variety of applications, including news feeds, content syndication, rich presence, geolocation, workflow systems, network management systems, and any other application that requires event notifications. Changelog: Describe the 'http://jabber.org/protocol/pubsub' disco#info feature. (gdk) URL: https://xmpp.org/extensions/xep-0060.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.

9 months, 3 weeks

1
0
0 0

LAST CALL: XEP-0485 (PubSub Server Information)

by Daniel Gultsch

This message constitutes notice of a Last Call for comments on XEP-0485. Title: PubSub Server Information Abstract: This document defines a data format whereby basic information of an XMPP domain can be expressed and exposed over pub-sub. URL: https://xmpp.org/extensions/xep-0485.html This Last Call begins today and shall end at the close of business on 2025-11-03. 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!

9 months, 3 weeks

4
5
0 0

2026

2025

2024

2023

Standards November 2025