The XMPP Newsletter November 2020

 Posted on December 9, 2020 |  8 minutes |  Newsletter |  emus

Welcome to the XMPP newsletter covering the month of November 2020.

This will be the last newsletter release for this (crazy) year, it was great to have you here reading! Many thanks to you contributors and reviewers. The XMPP Newsletter is a community project, and if you are interested to contribute to it in the coming year - you’re welcome to join!

For everyone having a new year’s break: we wish you a nice time! Until then stay safe and see you in the next year.

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 this year, please consider to say thanks or help these projects. Looking forward to XMPP in 2021!

Newsletter translations

Translations of the XMPP Newsletter will be released here:

XSF Announcement

We would like to make an informational announcement about an important circumstance regarding certificates to all parties involved in XMPP. If you or related parties are affected please spread the word on this:

Let’s Encrypt announced to switch away from their Root CA certificate cross-signed by IdenTrust. This means that old client devices (especially the roughly one third of Android phones running Android 7.0 and older) will consider Let’s Encrypt certificates issued after January 11th 2021 as untrustworthy. This problem will not go away, as the IdenTrust cross-signed certificate will expire in September, but there are some possible mitigations:

The implementation of the ISRG Root X1 certificate is explained in this article.


Chris Beckstrom wrote a post on the details of how they hacked together a bridge between iMessage and XMPP.

Nico Wellpott wrote a post on how he gathered presence and user count statistics for a group chat.

This month ejabberd celebrated their 18th birthday. On this occasion Marek Foss talked with Alexey Shchepin, who created ejabberd in November 2002.

Software news

Clients and applications

Dino 0.2 ‘Mexican Caribbean Coral Reefs’ has been released: The 0.2 release adds message correction, improves the file upload functionality and provides more information about message encryption. Besides other smaller changes it also fixes a number of bugs.


Conversations 2.9.1 has been released. This release includes fixes for searching on older Android devices, and optimizes memory consumption.

Snikket also released a new version of their Android app, based on the Conversations 2.9.0 release. They also announced sponsorship of OMEMO end-to-end encryption for group chats in Siskin IM, the iOS client by Tigase.

Beagle IM 4.1 and Siskin IM 6.1 have been released. The biggest change for this release is the introduction of XEP-0215: External Service Discovery which helps with establishing audio and video calls.


New Beta releases for Monal 4.9 have been published. While 4.9 final has already been released for Mac, the ARM version still need some time.

The first stable App version 3.0.1 is available for download. If you want to update your Pix-Art Messenger to, please read our update guide. (EN/DE)

Gajim Development News: In November, Gajim’s development team worked on Chat Markers, a feature many of you had wished to see in Gajim. Chat Markers enable you to see whether your contact has read your messages, and they help Gajim to manage notifications if you read messages on your phone or other devices.

News from the Ignite Realtime community: Spark has been released in version 2.9.4. This release includes fixes for SSL certificates, a new option to disable games, and further improvements.


News again from the Ignite Realtime community: Version 2.1.6 of the Client Control plugin for Openfire has been released.

Both Tigase clients had MIX support for a while, so now the XMPP component (based on Tigase PubSub Component) for Tigase XMPP Server providing support for XEP-0369: Mediated Information eXchange (MIX), is publicly available too.

During the interview with Alexey Shchepin, the author of ejabberd mentioned Jamler, as an 2011 experiment to rewrite ejabberd in OCaml. This historic code is now released as open-source too, so it can be studied.


Yes - more news from the Ignite Realtime community: There is a first release candidate of Smack 4.4.0 (Smack 4.4.0-rc1). The developers call for testing.


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.

Proposed Extensions

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.

  • Several extensions have been proposed this month. They have been accepted by the council, and are listed in the New section below.


  • Version 0.1.0 of XEP-0449 (Stickers)

    • This specification provides a protocol to send stickers and to create and share sticker packs.
    • Accepted by vote of Council on 2020-11-18.
  • Version 0.1.0 of XEP-0448 (Encryption for stateless file sharing)

    • This specification provides a protocol for sharing encrypted files using the stateless file sharing protocol (XEP-0447).
    • Accepted by vote of Council on 2020-11-18.
  • Version 0.1.0 of XEP-0447 (Stateless file sharing)

    • This specification describes a protocol for stateless asynchronous file sharing with integrity and transport flexibility. It allows clients to provide a good interoperable user experience in combination with Carbons and MAM.
    • Accepted by vote of Council on 2020-11-18.
  • Version 0.1.0 of XEP-0446 (File metadata element)

    • This specification defines a generic file metadata element to be used in other specifications.
    • Accepted by vote of Council on 2020-11-18.
  • Version 0.2.0 of XEP-0445 (Pre-Authenticated In-Band Registration)

    • This document extends the In-Band-Registration protocol to use invitation tokens, e.g. for registering accounts on non-public servers.
    • Accepted by vote of Council on 2020-11-04.


If an experimental XEP isn’t updated for more than six 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.6.0 of XEP-0373 (OpenPGP for XMPP)

    • Fix ’to’-attribute requirements: All content elements which are signed using OpenPGP need that attribute to prevent Surreptitious Forward Attacks. The <crypt/> element does not require one, as the intended recipient is established by the encryption itself. The XEP had the requirements for <sign/> and <crypt/> mixed up.
  • Version 0.6.0 of XEP-0389 (Extensible In-Band Registration)

    • Error out if a client selects an invalid flow.
  • Version 0.3.0 of XEP-0443 (XMPP Compliance Suites 2021)

    • Add more notable XEPs.
  • Version 0.2.0 of XEP-0438 (Best practices for password hashing and storage)

    • Update to match draft-ietf-kitten-password-storage-01.
  • Version 1.34.0 of XEP-0045 (Multi-User Chat)

    • Specify the use of a delay element in the initial subject message.
  • Version 1.3.0 of XEP-0118 (User Tune)

    • Add further tags for non-pop music.
  • Version 1.2.0 of XEP-0308 (Last Message Correction)

    • Reword note about how to handle LMC in cases where it is not clear that all recipients support it.

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.


  • Version 1.0.0 of XEP-0443 (XMPP Compliance Suites 2021)
    • Accept as Draft as per Council vote from 2020-11-11.

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

Thanks to Dominion0815, emus, kikiuchiyo, Licaon_Kter, mwild1, nico, SeveFP and wurstsalat3000 for their help in creating it! Special thanks to wurstsalat3000, for running a great summary on the XEPs each month!

See you in the next year, stay safe!

Spread the news!

Please share the news on “social networks”:

Find and place job offers in the XMPP job board.

Subscribe to the newsletter

We suggest you Subscribe to receive the next editions in your inbox as soon as it is published! Promote this newsletter to whoever may be interested.

Help us to build the newsletter

We started drafting every new issue in the XSF Github repository and 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 write about it? Please consider sharing your news or events here, and promote it to a large audience! Even if you can only spend a few minutes, 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.