The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Jingle User Location
Abstract:
This specification defines a Jingle application extension for
negotiating and updating user location inside an active Jingle session
using the XEP-0080 User Location payload.
URL: https://xmpp.org/extensions/inbox/jingle-geoloc.html
The Council will decide in the next two weeks whether to accept this
proposal as an official XEP.
Version 0.1.0 of XEP-0514 (Emoji Markup) has been released.
Abstract:
This specification leverages Message Markup (XEP-0394) and Stateless
file sharing (XEP-0447) (or Stateless Inline Media Sharing (XEP-0385))
to send custom emojis
Changelog:
Accepted as Experimental by council vote on 2026-05-12 (XEP Editor
(dg))
URL: https://xmpp.org/extensions/xep-0514.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.
Version 1.35.5 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:
* Fix 'from' attribute in examples where the room itself sends a
message.
* Fix associated pubsub node field name in disco info example. (nc)
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.
Hello Council and XEP Editors,
I would like to request reactivation of XEP-0346: Form Discovery and
Publishing.
The XEP is currently Deferred due to lack of activity. We are building
an alpha/prototype XMPP client, Tiedragon Teletyptel 2.0, and during
implementation of poll support we found that XEP-0346 is highly relevant
as a general mechanism for discovering and publishing forms.
Our current implementation is not production-ready, but we have running
code and a concrete use case:
- user-facing polls in 1:1 and MUC conversations
- form templates based on XEP-0004
- possible publication/discovery through PubSub
- accessibility and total-conversation workflows where structured forms
are useful beyond polls
We do not want to depend on a Deferred XEP as if it were stable.
Instead, we would like to help revive discussion and provide
implementation feedback from an alpha implementation.
The initial use case is poll creation and voting, but the broader need
is reusable form discovery/publishing for XMPP applications.
Would the Council / Editors be open to moving XEP-0346 back to
Experimental if we submit a substantive update or implementation notes?
If useful, I can prepare a pull request with:
- updated motivation and modern use cases
- security/privacy considerations
- relationship to XEP-0004 and XEP-0060
- implementation experience from Teletyptel 2.0
- clarification of poll-style usage without making polls the only use case
Kind regards,
Edward Tie
Tiedragon
Hello,
I have submitted two related Jingle ProtoXEPs:
1. Jingle T.140 / RTT
2. Jingle Location
Could someone from the XEP Editors / Council, or someone with Jingle
experience, help process and review these submissions?
Both ProtoXEPs are based on implementation work in Teletyptel 2.0 alpha.
The software is not production-ready yet, but we have running code and
practical test results. The goal is to explore accessible total
conversation over XMPP with audio, video, real-time text and optional
location sharing.
The main review areas are:
- correct Jingle session design
- whether the proposed features should be separate Jingle contents or
session metadata
- compatibility with existing Jingle/WebRTC clients
- relationship to T.140, RFC 4103 and XEP-0080
- fallback behavior when the peer does not support the feature
- security and privacy considerations
- whether the split into two ProtoXEPs is correct
I would appreciate help moving these submissions through the correct
XMPP Standards Foundation process.
Kind regards,
Edward Tie
Tiedragon
