Version 1.26.0 of XEP-0001 (XMPP Extension Protocols) has been
released.
Abstract:
This document defines the standards process followed by the XMPP
Standards Foundation.
Changelog:
* Surface (and correct) the source control information.
* Surface the publication URL (although I assume anyone reading this
has figured that one out by now).
* Surface the contributor side of things.
* Add bit about XEP authors making PRs if they don't exist - this is
"new" rather than documenting existing practice.
* Add bit about PRs getting XEP author approval (existing practice
hithertofore undocumented).
* Add bit about Council (etc) adding authors if they drop off
(existing practice hithertofore undocumented).
* Add note to clarify that Retraction doesn't mean Deletion (existing
practice, documented, but has been misunderstood before). (dwd)
URL: https://xmpp.org/extensions/xep-0001.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.
Hi,
Following what I've said yesterday at the summit, I would like to explain more
my idea, and get your feedback.
So basically the problem with presence in large MUC is that we get 2 things:
- initial presence when we join the room
- all the presence update when people join and leave, which is quite often
with people on mobiles.
So my point was that we are seeing MUC by the way it's used today. But we
don't have to.
We don't have to be actively in the room. What we want when we are in a large
room, is to be able to check it when we want, and be notified when we are
mentioned.
For smaller rooms, we may want to be notified on each new message.
The way I see it, we could have 2 ways to join a MUC: active and passive.
The active join would be what we do today, we get all the presence, and
updates, it's really bandwidth intensive.
The passive join, on the other hand, would only say "we are in the room". The
MUC service would then notify the client only in case of mention (or for any
message in case of "subscribed" room).
Benefit:
- we don't have presence spam anymore, the client does an active join only
when the user want to actually be in the room. So it's only one room at the
time.
- client doesn't have to actively parse message to look for mention, on mobile
it will get a push notification and wake up only when necessary
- It should be easy to implement on top on existing MUC implementation
- It's backward compatible: non-compatible client will just to "active" join
all the time, and get all the presence spam.
Probably we can also optimize the initial presence in case of active join, but
that's another topic.
I think that solves the presence issue. Let me know what you think about it.
Best,
Goffi
Dear Board members,
This email announces the agenda for our next Board meeting, scheduled for
Thursday, 5 February 2026, from 17:00 to 17:30 UTC. The meeting will take
place in the XSF chatroom at xmpp:xsf@muc.xmpp.org?join.
Brief context is included for each agenda item to support preparation.
*1. Welcome*Opening of the meeting.
*2. Formalize Agenda*Confirm and approve the agenda for this meeting.
*3. Review and vote on proposed changes to XEP-0001 and XEP-0143*The Board
will review and vote on proposed changes to XEP-0001, which require Board
approval.
The Council has already approved the proposed changes to XEP-0143. This
item is included to ensure process clarity and to determine whether the
Board wishes to formally note or endorse those changes as well.
*4. Summit and FOSDEM report and follow ups*A brief review of the recent
Summit and our presence at FOSDEM. The purpose is to identify any concrete
outcomes, learnings, or potential follow-up topics that may require future
Board or membership attention. No decisions are expected under this item.
*5. Increase Board meeting frequency*Discussion of a proposal to increase
the frequency of Board meetings, with the aim of improving engagement,
continuity, and overall productivity.
*6. Any Other Business*Items not listed above that require brief attention.
*7. Date of Next Meeting*Agreement on the date of the next Board meeting.
*8. Close*Closing of the meeting.
Please review the relevant materials ahead of the meeting so that we can
use our time efficiently.
Kind regards,
Guus
