The XMPP Newsletter June 2021

Welcome to the XMPP Newsletter covering the month of June 2021.

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, especially throughout the current situation, please consider to say thanks or help these projects!

Read this Newsletter via our RSS Feed!

Interested in supporting the Newsletter team? Read more at the bottom.

Other than that - enjoy reading!

Newsletter translations

Translations of the XMPP Newsletter will be released here (with some delay):

Many thanks to the translators and their work! This is a great help to spread the news! Please join them in their work or start over with another language!

XSF Announcement

The XMPP Operators Channel is a place primarily for operators of federated XMPP services, to have civil and low-bar discourse and resolution of interoperability issues. While discussions can get further from on-topic there was no written code of conduct or rules until this month. You can read them here and join if you find the topic interesting.


XMPP Office Hours each week - Also, checkout our new YouTube channel!

Berlin XMPP Meetup (remote): Monthly Meeting of XMPP Enthusiasts in Berlin - always 2nd Wednesday of the month.


Demo: ad-hoc commands and data forms in Mellium - Sam Whited demos the new support for XEP-0050: Ad-Hoc Commands and XEP-0004: Data Forms in the Mellium XMPP library.


Axel Reimer published a short installation and configuration guide for Monal 5.0. It is available in English and German.

Ingrid’s Space has thoughts on why decentralised applications don’t work.

Martin Dosch wrote a short blog post about how to use the “Jabber-ID” email header with neomutt [DE]. The setting of this header is also described in the wiki.

Software freedom conservancy moved their chat from IRC to XMPP using Snikket.

Vaxbot, the XMPP based vaccine bot has been featured on Canadian National News.

Software news

Clients and applications

Blabber.IM XMPP service has been discontinued and has shut down its server. On June 25, the website reported that they were discontinuing support for their XMPP server due to personal reasons.

In this respect, MattJ announced created a tool for users to migrate their roster and vcards but also subscriptions to another XMPP account. Find the XMPP account exporter here.

Gajim Development News: This month brought some fixes for themes and spell checking. Development on the new Gajim version made a big step forward: file previews are working again and more important they’re now a core integrated feature, they look even better while also being privacy respecting for those anonymous chats.

Monal 5.0 has been released, featuring support for group chats (not yet OMEMO encrypted, will come next) and sending voice messages and videos, but also a lot of internal code refactoring and bug fixes.

Monal Group Chat (MUC)

Profanity, a console-based XMPP client, has implemented attention flags. Use the shortcut ALT+F to toggle the flag.

UWPX v. has been released. It includes support for XMPP Providers for convenient auto-complete and registration of new accounts to XMPP servers. Besides that, this release fixes a few bugs related to stream close and open message parsing.

UWPX Server Onboarding


Jackal, an XMPP server written in Go, released version 0.54.0 with support for XEP-0198: Stream Management, docker compose support, graphana service dashboard and a new fancy logo:

New Jackal Logo

OpenFire 4.6.4 has been released, bringing some bug fixes.


Have you heard about qxbridge a Qt XMPP Bridge for Telegram based on QXmpp.

There is a new ProtoXEP for for pre-auth key generation, which would allow for fancy new uses, such as XMPP Self Provisioning with Mastodon

Extensions and specifications

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.


  • Version 0.1.0 of XEP-0459 (XMPP Compliance Suites 2022)

    • Accepted by vote of Council on 2021-05-26.
  • Version 0.1.0 of XEP-0458 (Community Code of Conduct)

    • Accept as Experimental after unanimous approval by Board of the ProtoXEP draft for discussion within the community.


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 XEP deferred this month.


  • Version 0.2.0 of XEP-0458 (Community Code of Conduct)

    • Integrate various comments from various sources (dwd)
  • Version 0.3 of XEP-0377 (Spam Reporting)

    • Rework based on list feedback. (ssw)
  • Version 0.11 of XEP-0292 (vCard4 Over XMPP)

    • Recommend use of contact bare JIDs for item IDs (ka)
  • Version 1.20.0 of XEP-0060 (Publish-Subscribe)

    • Add integer-or-max datatype to use with Data Forms Validation. (pep)


  • Version 1.0.0 of XEP-0423 (XMPP Compliance Suites 2020)
    • Update to Draft as per council vote on 2019/11/07
    • Successors are XMPP Compliance Suites 2021 (XEP-0443) and 2022 (XEP-0459)

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 Draft.

  • No Last Call this month.


  • No Draft 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.

Thanks all!

This XMPP Newsletter is produced collaboratively by the XMPP community.

Therefore many thanks to Adrien Bourmault, alkino, BAud, emus, Jeybe, nicola, mdosch, Leirda, Licaon_Kter, Pierre Jarillon, pmaziere, seveso, VI, wurstsalat, xdelatour, Ysabeau for their support and help in creation, review and translation!

Spread the news!

Please share the news on “social networks”:

Find and place job offers in the XMPP job board.

Subscribe to the monthly XMPP newsletter

Also check out our RSS Feed!

Help us to build the newsletter

We started drafting in this simple pad in parallel to our efforts in 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. We really need more support!

You have a project and write about it? Please consider sharing your news or events here, and promote it to a large audience! And even if you can only spend a few minutes of support, these would already be helpful!

Tasks which need to be done on a regular basis are for example:

  • Aggregation of news in the XMPP universe
  • Short formulation of news and events
  • Summary of the monthly communication on extensions (XEP)
  • Review of the newsletter draft
  • Preparation for media images
  • Translations: especially German and Spanish


This newsletter is published under CC BY-SA license.