- Standards

Resolve uncertainty about File Sharing Standards
by Philipp Hörist 04 Apr '26

04 Apr '26

Dear Council Members, For years now we have two competing standards https://xmpp.org/extensions/xep-0447.html and https://xmpp.org/extensions/xep-0385.html and it leads to confusion and additional work for new implementers and prevents in some cases implementations at all. According to the xmpp.org page both XEPs have each 6 implementations. I would suggest to issue a last call to gather feedback. After all feedback is addressed council should advances only one. Regards Philipp

4 4

Proposed XMPP Extension: Explicit Mentions
by Daniel Gultsch 02 Apr '26

02 Apr '26

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Explicit Mentions Abstract: This specification defines a way to explicitly mention a person or groups of people. URL: https://xmpp.org/extensions/inbox/explicit-mentions.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

11 65

Proposed XMPP Extension: Message Archive Management: Trim Command
by Daniel Gultsch 01 Apr '26

01 Apr '26

The XMPP Extensions Editor has received a proposal for a new XEP. Title: Message Archive Management: Trim Command Abstract: This specification describes how a client can request "trimming" of an archive URL: https://xmpp.org/extensions/inbox/xep-mam-trimming.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP.

1 0

NEW: XEP-0513 (Explicit Mentions)
by Daniel Gultsch 01 Apr '26

01 Apr '26

Version 0.1.0 of XEP-0513 (Explicit Mentions) has been released. Abstract: This specification defines a way to explicitly mention a person or groups of people. Changelog: Accepted as Experimental by council vote on 2026-03-31 (dg) URL: https://xmpp.org/extensions/xep-0513.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

NEW: XEP-0512 (XMPP as Interpretive Dance)
by Daniel Gultsch 01 Apr '26

01 Apr '26

Version 5.6.7.8 of XEP-0512 (XMPP as Interpretive Dance) has been released. Abstract: This document defines a method for representing XMPP communications through the medium of interpretive dance. By mapping core protocol elements to specific physical movements, it allows expressive, low- bandwidth, and audience-friendly implementations of XMPP suitable for artistic performances, theatrical demonstrations, and deeply confusing hackathons. Changelog: Initial published version. (gdk) URL: https://xmpp.org/extensions/xep-0512.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

Extending XEP-0313 with trimming support
by Matthew Wild 31 Mar '26

31 Mar '26

Hi folks, There are a few limitations with XEP-0313 which I've been hoping to address for a while, mostly around giving users more control and making it easier for operators to comply with various data protection requirements. Users have control over most account data in XMPP. However archives are, generally, read-only. In particular, user data should generally be deleted upon request. Currently such requests would have to be manually sent to the service operator, as there is no in-band method for this yet. My proposal is to support an in-band 'trim' command, which allows removal of all archived messages, or up to (and including) a specific archived message, or deletion of the entire archive. The functionality is optional and discoverable, so shouldn't affect backwards compatibility. This has some limitations. For example, it wouldn't allow selectively deleting all messages with a specific contact, which is occasionally requested. Such an operation would leave holes in the archive (which XEP-0313 forbids to ensure sync points don't get removed). But I'm in favour of solving what we easily can for now. There are other things I would like to improve around archiving, such as exposing retention configuration. But I plan for these to live in new XEPs. As XEP-0313 is stable and almost universally implemented, I wanted to raise awareness of this proposal and seek some consensus from the community before pushing it forward to Council. The PR can be found at https://github.com/xsf/xeps/pull/1514 The new section is rendered at https://matthewwild.co.uk/uploads/xep-0313.html#trim Regards, Matthew

4 9

XMPP Council Agenda 2026-03-31
by Daniel Gultsch 31 Mar '26

31 Mar '26

Good Morning Council Members, the next XMPP Council Meeting will take place on, Tuesday, March 31 2026 at 15:30 UTC in xmpp:council@muc.xmpp.org?join Notice the time zone change. For some people this might now be an hour later than usual. The Agenda is as follows: 1) Roll call 2) Agenda Bashing 3) Editors update • LAST CALL: XEP-0377 (Blocking Command Reports) • UPDATED: XEP-0461 (Message Replies) • UPDATED: XEP-0493 (OAuth Client Login) The two updated XEPs are just minor editorial changes. 4) Items for voting a) XEP-0045: Add clarification regarding unsetting reserved nicknames https://github.com/xsf/xeps/pull/1512 5) Pending votes Marvin, Stephan Paul, Dan, Jerome on XEP-xxxx: Explicit Mentions (https://xmpp.org/extensions/inbox/explicit-mentions.html) See the spreadsheet of doom: https://docs.google.com/spreadsheets/d/14gy_nhuTnqlktakJfLZ2Mc-jblSaG0na0Kh… 6) Date of Next 7) AOB 8) Close

1 0

UPDATED: XEP-0493 (OAuth Client Login)
by Daniel Gultsch 31 Mar '26

31 Mar '26

Version 0.1.1 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: * Fix reference to RFC 7628 for SASL OAUTHBEARER (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.

1 0

UPDATED: XEP-0461 (Message Replies)
by Daniel Gultsch 31 Mar '26

31 Mar '26

Version 0.2.1 of XEP-0461 (Message Replies) has been released. Abstract: This document defines a way to indicate that a message is a reply to a previous message. Changelog: Update the example to use the correct fallback namespace. (mye) URL: https://xmpp.org/extensions/xep-0461.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-0377 (Blocking Command Reports)
by Daniel Gultsch 31 Mar '26

31 Mar '26

This message constitutes notice of a Last Call for comments on XEP-0377. Title: Blocking Command Reports Abstract: This document specifies a mechanism by which reporting information can be attached to a Blocking Command (XEP-0191) request. It enables servers to process reports related to blocked entities while remaining focused on this specific workflow rather than general abuse reporting. URL: https://xmpp.org/extensions/xep-0377.html This Last Call begins today and shall end at the close of business on 2026-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