Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of February 2022.
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, especially throughout the current situation, please consider saying thanks or help these projects! Interested in supporting the Newsletter team? Read more at the bottom.
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):
- French: jabberfr.org and linuxfr.org
- German: xmpp.org/de/blog and anoxinon.de
- Italian: nicfab.it
- Spanish: xmpp.org/es/blog
- The XSF is planning to participate in Google Summer of Code 2022 (GSoC). If you are interested in participating as a student, mentor or as a project in general, please add your ideas and reach out to us.
- All XSF members are called to vote in the currently on-going member applications.
- XMPP Office Hours: available on our YouTube channel
- Berlin XMPP Meetup (remote): monthly meeting of XMPP enthusiasts in Berlin, every 2nd Wednesday of the month
- JMP.chat describes in their blog why gateways, and especially bidirectional gateways, with XMPP and other protocols, are so useful. Their Newsletter also announces the launch of worldwide calling and completion of their rebrand.
Erik Bärwaldt, from the German “Linux Magazin” evaluated instant messengers including Conversations for XMPP [DE].
Mellium Dev Communiqué: This month saw the release of several new packages including integration testing for Slixmpp, support for PEP Native Bookmarks, better support for various cryptographic hashes, and support for entity capabilities.
0.3 has been released: Video calls and conferences - encrypted and peer-to-peer. Dino now supports calls between two or more people!
Gajim development news: February brought a unified group chat details window, which offers all the configuration knobs you need. Also this month: less memory leaks and improved OMEMO QR codes.
Monal had a successful funding campaign for a build server, which will significantly reduce build time. Further insights into Monal development: Monal will drop support for iOS 12 and 13, and for macOS Catalina. Monal’s team is searching for a SwiftUI developer, and they need help with building a new and simplified website.
Big news from Movim: Movim
0.20 “Skiff” has been released, which features OMEMO support, GUI improvements, and better group chat management.
1.5.1605 has been released with OMEMO fixes.
0.13.2 has been released, this version only fixes the compatibility with the newly released slixmpp
1.8.0, but a much more interesting release is to come soon.
Profanity developers wrote a blog post on how to run their client on Pinephones.
0.57.0, an XMPP server written in Go has been released.
Openfire announces the release of Openfire
4.7.1: Notable fixes include security updates to bundled database drivers, logging configuration fixes, and an important fix for users experiencing troubles with users getting booted from group chat rooms. Furthermore, Openfire Pàdé
1.6.1 has been released. REST API Openfire plugin
1.7.1 hase been released, too.
Snikket published an important update for users of their server software on ARM devices, including Raspberry Pi boards.
Tigase XMPP Server
8.2.0 has been released.
Mellium Co-op has released
v0.21.1 of the melium.im/xmpp library for Go! Highlights for this release include basic support for
PubSub and PEP as well as In-Band Bytestreams. More information can be found in the release announcement. Version 0.21.1 fixes a security issue that was discovered in the websocket package and should be preferred when updating. For more information see CVE-2022-24968.
1.8.0 has been released, which adds compatibility with python 3.10, as well as a lot of improvements related to typing and async under the hood.
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.
- This specification provides a way to filter PubSub nodes in a disco query.
- This specification provides a way to reduce the amount of queries necessary to stay up-to-date with affiliations in a MUC room.
- 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.
2.13.0of XEP-0004 (Data Forms)
- Add incomplete submission form handling (melvo)
1.24.1of XEP-0060 (Publish-Subscribe)
- Add hint for processing incomplete submission forms (melvo)
1.24.0of XEP-0060 (Publish-Subscribe)
- Advertise support for publishing items
- Replace ‘allow’ with ‘allows’ (melvo)
1.23.0of XEP-0060 (Publish-Subscribe)
- Clarify (redefine) pubsub#type field. (edhelas, pep)
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.
Info: The XSF has decided to rename ‘Draft’ to ‘Stable’. Read more about it here.
- No XEPs advanced to Stable this month.
- No XEP deprecated this month.
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.
Please share the news on other networks:
Subscribe to the monthly XMPP newsletterSubscribe
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.
This XMPP Newsletter is produced collaboratively by the XMPP community. Therefore, we would like to thank Adrien Bourmault (neox), alkino, anubis, Anoxinon e.V., Benoît Sibaud, cpm, daimonduff, emus, Ludovic Bocquet, Licaon_Kter, marevalo, mathieui, MattJ, nicfab, patasca, seveso, Sam Whited, singpolyma, TheCoffeMaker, wurstsalat,xdelatour, Ysabeau for their support and help in creation, review and translation. Many thanks to all contributors and their continuous support!
Each months’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
This newsletter is published under CC BY-SA license.