The XMPP Newsletter March 2023

 Posted on April 5, 2023 |  8 minutes |  Newsletter |  XMPP Communication Team and Contributors

Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of March 2023. Many thanks to all our readers and all contributors!

Like this newsletter, many projects and their efforts in the XMPP community are a result of people’s voluntary work. If you are happy with the services and software you may be using, please consider saying thanks or help these projects! Interested in supporting the Newsletter team? Read more at the bottom.

XSF Announcements

  • got a new software section! Looking for XMPP software, i.e. clients, servers, libraries, components, and tools? Check out’s new software section, which lets you filter software by your own criteria. Looking for a client which works on Android and supports audio/video calls? Looking for a library that supports XEP-0461: Message Replies? Just apply the filter and see what you get!’s new software section’s new software section

XMPP and Google Summer of Code 2023

The XSF has been accepted again as hosting organisation at the GSoC 2023 !

XSF and Google Summer of Code 2023

XSF and Google Summer of Code 2023

XSF fiscal hosting projects

The XSF offers fiscal hosting for XMPP projects. Please apply via Open Collective. For more information, see the announcement blog post. Current projects:

XMPP Events


  • Debian package maintainers give a summary of XMPP packages that will be available in the next Debian stable release (Debian 12 “Bookworm”).

  • Cheogram Android introduces Stickers.

  • IgniteRealtime: Translations everywhere!

  • Carl Schwan writes on the Digital Market Act workshop in Brussels

    Digital Market Act workshop in Brussels

    Digital Market Act workshop in Brussels

  • The IETF has approved publication of Messaging Layer Security (MLS), a new standard for end-to-end security that will make it easy for apps to provide the highest level of security to their users. End-to-end encryption is an increasingly important security feature in Internet applications. It keeps users’ information safe even if the cloud service they’re using has been breached.

Software news

Clients and applications

  • Cheogram Android 2.12.1-4 has been released with support for sending message replies and reactions, swipe to reply, “note to self” contact, viewing vcard4 profiles, and occasional MUC pings.
  • Gajim 1.7.2 has been released. This release brings many bug fixes and some useful improvements. Gajim now allows you to delete messages from your local chat history (in case of nasty spam messages). Furthermore, detection of WAV audio files has been improved and you can now click the waveform to skip to a specific timestamp within a voice message.
  • monocles chat 1.6.3 received support for message moderation (XEP-0425) and will get some new features of Cheogram Android as well.
  • Movim 0.21 “Whipple” has been released, and it comes with a ton of new features. Message Replies, Web Push, voice messages, new emojis, and much more.
  • SiskinIM 7.3.3 and BeagleIM 5.3.4 from Tigase have been released.
  • Spark 3.0.2 from Ignite Realtime has been released.
Movim supports replies

Movim supports replies


  • Metronome IM 4.0.2 brings some bug fixes.

Libraries & Tools

From the ignite realtime community:

Extensions and specifications

The XMPP Standards Foundation develops extensions to XMPP in its XEP series in addition to XMPP RFCs.

Developers and other standards experts from around the world collaborate on these extensions, developing new specifications for emerging practices, and refining existing ways of doing things. Proposed by anybody, the particularly successful ones end up as Final or Active - depending on their type - while others are carefully archived as Deferred. This life cycle is described in XEP-0001, which contains the formal and canonical definitions for the types, states, and processes. Read more about the standards process. Communication around Standards and Extensions happens in the Standards Mailing List (online archive).


The XEP development process starts by writing up an idea and submitting it to the XMPP Editor. Within two weeks, the Council decides whether to accept this proposal as an Experimental XEP.

  • No XEPs proposed this month.


  • No new XEPs this month.


If an experimental XEP is not updated for more than twelve months, it will be moved off Experimental to Deferred. If there is another update, it will put the XEP back onto Experimental.

  • No XEPs deferred this month.


  • Version 0.2.0 of XEP-0444 (Message Reactions)
    • Add emoji rejection mechanism. (NC)
  • Version 0.7.0 of XEP-0359 (Unique and Stable Stanza IDs)
    • Add security consideration regarding spoofability and reference example (fs)
  • Version 0.12.0 of XEP-0292 (vCard4 Over XMPP)
    • Removes raw-IQ mode and specifies the reuse of PEP (spw)
  • Version 0.4.0 of XEP-0388 (Extensible SASL Profile)
    • Bump namespace
    • Add reference to XEP-0440 and RFC 5802
    • Update security considerations and business rules
    • Clarify <continue/> and tasks
    • Add expansion point to inline stream resumption and BIND2 (and possibly others)
    • Add optional <user-agent/> element
    • Move from Deferred to Experimental
  • Version 0.4.0 of XEP-0386 (Bind 2)
    • Various changes, made in parallel with working client and server implementation experience, and SASL2 updates.
    • More tightly define the integration with XEP-0388 and several session feature XEPs: XEP-0198, XEP-0280, XEP-0352.
    • Replace the custom latest-id element with the new metadata element from XEP-0313, which also provides richer information.
    • Drop unread tracking, as this is a deep topic not directly related to resource binding. Instead the details of integration with other extensions have been better defined and demonstrated, to allow such functionality when it is fully defined and exists.
    • Adjust proposed namespace on aesthetic grounds and consistency with SASL2’s approach. As this protocol may become part of the new preferred connection flow for a long time to come, it makes no sense to include the redundant and potentially confusing ‘2’ when there is no conflict without it. Similarly, the ‘.0’ has been dropped from the XEP’s title, as it isn’t really a version number.
    • Allow the client some influence over the resulting resource identifier, and define a standard format for these combined identifiers.
    • Specify that servers should terminate old sessions from a client when it binds a new resource.
  • Version 0.2.0 of XEP-0428 (Fallback Indication)
    • Add ‘for’ attribute such that entities can discover what the fallback is for.
    • Allow to specify that only one of <subject> or <body is meant as a fallback.
    • Allow to specify the part of respective text that is meant as fallback where applicable.
    • Don’t use encryption example, which should use XEP-0380 instead.

Last Call

Last calls are issued once everyone seems satisfied with the current XEP status. After the Council decides whether the XEP seems ready, the XMPP Editor issues a Last Call for comments. The feedback gathered during the Last Call help improving the XEP before returning it to the Council for advancement to Stable.

  • No Last Call this month.


  • No XEP moved to stable this month.


  • No XEP deprecated this month.

Call for Experience

A Call For Experience - like a Last Call, is an explicit call for comments, but in this case it’s mostly directed at people who’ve implemented, and ideally deployed, the specification. The Council then votes to move it to Final.

  • No Call for Experience this month.

Spread the news!

Please share the news on other networks:

Subscribe to the monthly XMPP newsletter

Also check out our RSS Feed!

Looking for job offers or want to hire a professional consultant for your XMPP project? Visit our XMPP job board.

Newsletter Contributors & Translations

This is a community effort, and we would like to thank translators for their contributions. Volunteers are welcome! Translations of the XMPP Newsletter will be released here (with some delay):

  • English (original):
    • General contributors: Adrien Bourmault (neox), Alexander “PapaTutuWawa”, Arne, emus, Licaon_Kter, Ludovic Bocquet, melvo, MSavoritias (fae,ve), wurstsalat, XSF iTeam
  • French: and
    • Translators: Adrien Bourmault (neox), alkino, anubis, Benoît Sibaud, Pierre Jarillon, Ppjet6, Ysabeau
  • German: and
    • Translators: Jeybe, wh0nix
  • Italian:
    • Translators: nicfab
  • Spanish:
    • Translators: daimonduff, TheCoffeMaker

Help us to build the newsletter

This XMPP Newsletter is produced collaboratively by the XMPP community. Each month’s newsletter issue is drafted in this simple pad. At the end of each month, the pad’s content is merged into the XSF Github repository. We are always happy to welcome contributors. Do not hesitate to join the discussion in our Comm-Team group chat (MUC) and thereby help us sustain this as a community effort. You have a project and want to spread the news? Please consider sharing your news or events here, and promote it to a large audience.

Tasks we do on a regular basis:

  • gathering news in the XMPP universe
  • short summaries of news and events
  • summary of the monthly communication on extensions (XEPs)
  • review of the newsletter draft
  • preparation of media images
  • translations
  • communication via media accounts


This newsletter is published under CC BY-SA license.