Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of August 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.

Newsletter 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): xmpp.org
• French: jabberfr.org and linuxfr.org
• German: xmpp.org and anoxinon.de
• Italian: nicfab.it
• Spanish: xmpp.org

XSF Announcements

• The XSF membership application period for the fourth quarter 2022 is currently open. If you are interested in becoming a XSF member then you can apply for membership . Please submit by November 27, 2022.

Google Summer of Code 2022

The Google Summer of Code 2022 has lifted off and coding started a while ago! The two new contributors Patiga and PawBud who will work on open-source software projects in the XMPP environment. Read their first blog posts, too.

• Patiga works on more flexible file transfers in Dino . Mentors are fiaxh and Marvin W. .
  • Stateless File Sharing GSoC project
  • Project Stateless File Sharing: First Steps
  • Stateless File Sharing: Base implementation
  • Stateless File Sharing: Sources and Compatibility
• PawBud works towards adding support for A/V communication via Jingle in ConverseJS . Mentors are JC Brand and vanitasvitae .
  • On-Boarding Experience with XSF (Converse)
  • ConverseJS: An in-depth view into my GSoC'22 project!
  • Google Summer of Code 2022 at XSF: Converse.js - Mid Term Evaluation Update

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:

• Bifrost bridge: Offline messages exchange between Matrix and XMPP
• Mellium Co-op

Events

• 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

Articles

Prosody’s team announces a rework of their permission system in context of modernizing XMPP authentication and authorization .

Eversten.net published two articles:

• Snikket: Getting Started (iOS)
• Snikket: Getting Started (Android)

JMP newsletter announces a new major release of the Cheogram Android client, with support for ad-hoc command UI and more, as well as a new multi-account billing feature. They also have an article showcasing the command UI in pictures .

Anoxinon Media published “XMPP - Teil 1 - Messaging mal anders” [DE]. It is about XMPP - an alternative that stands out from the mass.

Kaidan, the XMPP client for every device, released a post about its end-to-end encryption trust management

The Mellium Dev Communiqué for August 2022 outlines development for the past month including support for HTTP Upload, RFC 9266, various internal testing changes, and a call for feedback!

Easy Onboarding with Android Chat App blabber.im via XMPP Providers ! Passwords are generated automatically and XMPP providers are suggested. Those suggestions are based on the curated list of XMPP Providers project .

Software news

Clients and applications

Conversations 2.10.9 and 2.10.10 have finally been released for both Google Play Store and F-Droid. Many people were eagerly waiting for a new Conversations build on F-Droid as there were some issues regarding the usage of WebRTC libraries, for Audio/Video calls. F-Droid users were still on the 2.10.2.1+fcr build but now, after 5 months of waiting, they are using the latest version. These releases improve interactions with Bluetooth output devices so be sure to grant the permission as needed. A note for jmp.chat users, the F-Droid version uses an incompatible WebRTC library, so it’s better to switch to the Cheogram app (a fork from the jmp.chat developers) at the moment. The Play Store version does not have this issue.

Moxxyv2 0.2.0, 0.2.1, 0.2.2, 0.2.3 have been released. A new XMPP client for the Android community is featured in this month’s newsletter; it is currently only in the alpha stage. However, the future of the project appears to be pretty promising, and we are pleased to have another XMPP project join the community! The initial version (0.2.0) was made available on July 29th, and the second version (0.2.1) was made available on August 14th. This project is the successor of moxxyv1, which was written in React Native and abandoned due to various technical issues.

Psi+ 1.5.1639 (2022-08-17) has been released.

Tigase released BeagleIM 5.3 (macOS) and SiskimIM7.3 (iOS) which contain changes and stability improvements. Note that SiskinIM will need at least iOS 13 from now on.

Servers

Openfire 4.7.3 has been released, which brings many bug fixes, especially for BOSH.

Libraries

libstrophe 0.12.2 has been released.

Mellium XMPP 0.21.3 has been released.

python-nbxmpp 3.2.0 and 3.2.1 have been released, which bring support for Extensible SASL Profile ( XEP-0388 ) and bug fixes.

Tigase Martin 3.2.1 has been released.

From the ignite realtime community:

• REST API Openfire plugin 1.9.0 and 1.9.1 has been released to fix several bugs.
• Openfire ThreadDump plugin 1.1.0 has been released and add two new evaluators for the TaskEngine and statistics from the database connection pool.

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

xmpp.org features a page about XMPP RFCs as well.

Proposed

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.

New

• Version 0.1.0 of XEP-0469 (Bookmark Pinning)
  • This document defines an XMPP protocol extension to allow users to pin PEP Native Bookmarks.
• Version 0.1.0 of XEP-0470 (Pubsub Attachments)
  • This specification provides a way to attach elements to a pubsub item.

Deferred

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.

Updated

• Version 0.2.0 of XEP-0447 (Stateless file sharing)
  • Add disposition attribute to signal when inlining is desired. (lmw)
• Version 0.2.0 of XEP-0470 (Pubsub Attachments)
  • Update reactions to be similar to Message Reactions (XEP-0444)
  • Namespace bump (jp)
• Version 1.1 of XEP-0231 (Bits of Binary)
  • Mention where to get textual names of hash functions. (ssw)
• Version 0.3.0 of XEP-0440 (SASL Channel-Binding Type Capability)
  • Make implementation of tls-server-end-point a MUST for servers. (tm)
• Version 0.2.0 of XEP-0446 (File metadata element)
  • Use height/width instead of dimensions (lmw)
• Version 0.2.0 of XEP-0448 (Encryption for stateless file sharing)
  • Replace the ProtoXEP reference with a reference to the published XEP.
  • Add urn:xmpp:ciphers:aes-256-cbc-pkcs7:0 (same as used in XEP-0384) (lmw)

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.

Stable

• Version 1.0.0 of XEP-0215 (External Service Discovery)
  • Accept as Stable as per Council Vote from 2022-08-03. (XEP Editor (jsc))

Deprecated

• 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:

• Mastodon
• Twitter
• YouTube
• Lemmy instance
• Reddit
• LinkedIn

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 .

Help us to build the newsletter

This XMPP Newsletter is produced collaboratively by the XMPP community. Therefore, we would like to thank Adrien Bourmault (neox), anubis, Anoxinon e.V., Benoît Sibaud, cpm, daimonduff, emus, Gooya, Holger, IM , Ludovic Bocquet, martin, MattJ, MSavoritias (fae,ve), nicfab, Pierre Jarillon, Sam Whited, TheCoffeMaker, wh0nix, vanitasvitae, wurstsalat, Zash for their support and help in creation, review, translation and deployment. Many thanks to all contributors and their continuous support!

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

License

This newsletter is published under CC BY-SA license .

It’s been a month since I wrote my last blog . For those of you who have been following my blogs, thanks a lot for taking the time to read them. In this blog, I will give the updates post mid-term evaluation and the challenges that I have been facing and how I overcame some of them.

The Mid-Term Evaluation

For those of you who don’t know much about GSoC, a mid-term evaluation was scheduled, where as a contributor you have to fill out a form which had some questions related to your experience with your mentor and the organization administrator so far and the project itself. It barely took me 5-10 minutes to complete the form so there’s that.

Project Updates & Challenges Faced

I have been working on the jingle message retraction feature and the jingle chat history feature. Let me explain:

If you have gone through XEP-0353 , you might be knowing about the retraction feature . If not, then the below two diagrams are my best attempts to explain it, and to be honest it is pretty simple.

Ok, now, let me show you another diagram which took me around 2 weeks to visualize:

This is what confused me the most and took a lot of my time. If you look at the way I have written my code (and I won’t link it, since I believe that the link might break in the future due to the constant changes in the codebase that are yet to come):

    // Responder's Side Parser
    function parseJingleMessage(stanza, attrs) {
    const jingle_propose_type = getJingleProposeType(stanza);
    return { ...attrs, ...{ 'jingle_propose': jingle_propose_type, 'jingle_retraction_id': getJingleRetractionID(stanza), 'template_hook': (attrs['template_hook']) ? 'getJingleTemplate' : undefined, 'jingle_status': attrs['jingle_status'] }
    }
    }

    // Initiator's Side
    function retractCall(context) {
    const initiator_message = context.model.messages.findWhere({ 'media': 'audio' });
    const propose_id = initiator_message.attributes.propose_id;
    const message_id = u.getUniqueId();
        api.send(
            $msg({
            'from': _converse.bare_jid,
            'to': context.jid,
            'type': 'chat',
            id: message_id
            }).c('retract', { 'xmlns': Strophe.NS.JINGLEMESSAGE, 'id': propose_id })
            .c('reason', { 'xmlns': Strophe.NS.JINGLE })
            .c('cancel', {}).up()
            .t('Retracted').up().up()
            .c('store', { 'xmlns': Strophe.NS.HINTS })
        });
        const attrs = {
            'from': _converse.bare_jid,
            'to': context.jid,
            'type': 'chat',
            'jingle_retraction_id': propose_id, 
            'msg_id': message_id,
            'jingle_status': context.model.get('jingle_status'),
            'template_hook': 'getJingleTemplate'
        }
        context.model.messages.create(attrs);
    }

I borrowed this code from a single file called “utils.js” which as the name suggests contains all the miscellaneous functions of a plugin that are needed for it to function. It doesn’t take much thinking to realize how big the problem becomes once the codebase is large enough. I must say it’s thanks to my mentor, I was able to differentiate the two sides, and i am now able to move on. Though, I still get confused but fortunately, I feel like its becoming more infrequent.

Ohh, and by the way, the create function creates an instance of the message model, and if you didn’t understand this statement, I highly recommend going through the backbone.js documentation .

So, lessons to learn:

• Comment or possibly document your code from day one.
• Don’t keep random variable names.
• Speak up to your mentor!! Period. I can assure you a lot of JC’s time could have been saved had I spoken up about my thought process sooner.

Ahemmm….. let’s move on now.

Message Chat History Rendering for Jingle

Now, when you get a missed call, you usually get a timestamp. It is no different in a jingle call, but I do need to have a discussion regarding it’s actual implementation with JC. The actual message content should be pretty straightforward and if you want to see how I implemented/am implementing it, I will straight up point towards JC’s explanation of it .

Non-Technical Corner of this blog

Hmmmm enough about the project, now for some unnecessary life updates. I will be leaving for my master’s program in a week’s time. My schedule is packed with various things right now. Going to a new country on your own is scary for the first time, especially when you know that there is no one who can help you there but GSoC seems like a perfect distraction from the nervousness. JC seems to be doing fine, speaking of whom, did I mention he took a hiatus last week? I really hope he enjoyed his time off. There were nights in the last week, which made me wonder if I did actually stress him out or something, but I am pretty sure I am just overthinking it. I value his patience out of all things and I am not joking when I say he has a lot of it. I mean, if I as a mentor would meet another PawBud, I would have probably quit by now and to be honest, that’s one of the million reasons why I am not a mentor right now. I feel so embarrassed about the little things JC has to repeat every time because I was distracted or too lazy to note them down. I hate inconsistency and love to be direct about things, so if you have made it this far, I would like to say that there is a good chance that this project might end with the implementation of XEP-0353 given my slow pace.

I do know that there are many people who are expecting this feature to be implemented, but yeah it is what it is. JC has somehow motivated me, to do what I do perfectly and I couldn’t agree more. Let’s see what the future holds now, I am giving it everything, and I will try to implement it as much as I can effectively.

Thanks for reading my blog.

Regards, PawBud

Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of July 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.

Newsletter 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): xmpp.org
• French: jabberfr.org and linuxfr.org
• German: xmpp.org and anoxinon.de
• Italian: nicfab.it
• Spanish: xmpp.org

XSF Announcements

• The XSF membership application period for the third quarter 2022 is currently open. If you are interested in becoming a XSF member then you can apply for membership . Please submit by August 25, 2022.

Google Summer of Code 2022

The Google Summer of Code 2022 has lifted off and coding started a while ago! The two new contributors Patiga and PawBud who will work on open-source software projects in the XMPP environment. Read their first blog posts, too.

• Patiga works on more flexible file transfers in Dino . Mentors are fiaxh and Marvin W. .
  • Stateless File Sharing GSoC project
  • Project Stateless File Sharing: First Steps
• PawBud works towards adding support for A/V communication via Jingle in ConverseJS . Mentors are JC Brand and vanitasvitae .
  • On-Boarding Experience with XSF (Converse)
  • ConverseJS: An in-depth view into my GSoC'22 project!

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:

• Bifrost bridge: Offline messages exchange between Matrix and XMPP
• Mellium Co-op

Events

• 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

Articles

There are some articles and thoughts on the European Digital Markets Act:

• ec.europa.eu
• ZDF about interoperatibility [DE]
• German freie-messenger.de about digital markets act
• German freie-messenger.de about interoperatibility
• The Digital Markets Act: ensuring fair and open digital markets, European Commission
• Interoperability - Digital Markets Act (DMA), freie-messenger.de
• Interoperability - Thoughts, freie-messenger.de
• WhatsApp muss sich für alle Messenger öffnen, Dominik Rzepka [DE]

The site “Chat standard (XMPP)” with lots of information is available in English now at freie-messenger.de

Axel from eversten.net published an XMPP Push Notification Test for iOS covering latest Monal, Siskin IM and Snikket versions on different server implementations. A good 15 minutes read for both iOS users and their multi-platforms contacts alike.

JMP now delivers transcribed voicemail in many common languages, not just English. The voicemail system has also been updated to source names from more modern XMPP profiles including vCard4 and PEP Nickname.

MoongoseIM 5.1 was released as announced, as announced in the June 2022 Newsletter . In addition to the previously mentioned features, this brought improvements to the Inbox feature. You can now read more about the new Inbox settings and scalability improvements in this article .

Software news

Clients and applications

The Mellium Dev Communiqué for July 2022 has been published! Important updates this month include an implementation of the new RFC 9266 and a new tool for finding documentation related issues in Go projects. In addition, Mellium has moved to Codeberg! The repositories can now be found at codeberg.org/mellium and the announcement post can be found on Lemmy or Open Collective .

Conversations 2.10.8 , a Jabber/XMPP client for Android, has been released.

Gajim 1.4.6 and 1.4.7 have been released. These releases bring performance improvements, better file previews, and fix some bugs with the status icon and notifications. Emoji short code detection has been improved as well.

Monal version 5.2.0 has been released by the Monal development team! This release’s highlights are the new (private) push servers in Europe and the US, display of transferred files in app’s documents directory, and several fixes regarding encryption (OMEMO), QR code scanning, and onboarding. Besides, Monal also features a new webpage .

Psi+ 11.5.1634 (2022-07-11) has been released.

Servers

eturnal 1.10.0 , a STUN / TURN standalone server, has been released.

Openfire version 4.7.2 is out, stabilizing and fixing bugs, notably improving BOSH connections under load.

Push Notification Openfire plugin 0.9.1 was released with only one, but an important fix.

Version 1.8.3 of the Openfire REST API plugin is out too, extending MUC search and updating dependencies.

Libraries

libstrophe 0.12.1 , a lightweight XMPP client library written in C, has been released.

nbxmpp 3.1.1 has been released . This version comes with performance improvements and bug fixes.

The XMPP webhooks component has been updated to support more webhooks out of the box. Effectively, this component replaces proprietary tools such as Slack with a better option based on open code and open protocols, fully under control of its users. It now has:

• Richer messages for GitLab events (labels, time spent, etc.)
• Support for Stripe events, including optional (but recommended) signature verification.
• Support for SMS to URL Forwarder , a simple but effective SMS forwarder application for Android. This is handy for those with a second or third phone and it’s also used to showcase some of the new features .
• Integration with Nextcloud via Flow Webhooks .

Paul Schaub wrote a short blog post about their recent progress towards adding Web-of-Trust support to PGPainless. With release 1.3.2, the OpenPGP library got support for creating signatures on third-party certificates, which will help users to build their trust network.

xmpp-dns, a tool to check XMPP SRV records, was released in version 0.3.0 , bringing support for DNS over TLS (DoT) and for setting a custom DNS server.

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

xmpp.org features a page about XMPP RFCs as well.

Proposed

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.

• Bookmark Pinning
  • This document defines an XMPP protocol extension to allow users to pin PEP Native Bookmarks.
• Pubsub Attachments
  • This specification provides a way to attach elements to a pubsub item.

New

• WebSocket S2S
  • This specification defines a procedure to make s2s XMPP connections over WebSocket.
• XMPP over QUIC
  • This specification defines a procedure to make both c2s and s2s XMPP connections over the QUIC protocol instead of TCP+TLS.

Deferred

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.

Updated

• No XEPs updated this month.

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.

• External Service Discovery
  • This document specifies an XMPP protocol extension for discovering services external to the XMPP network.

Stable

• No XEPs advanced to Stable this month.

Deprecated

• 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:

• Mastodon
• Twitter
• YouTube
• Lemmy instance
• Reddit
• LinkedIn

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 .

Help us to build the newsletter

This XMPP Newsletter is produced collaboratively by the XMPP community. Therefore, we would like to thank Adrien Bourmault (neox), anubis, Anoxinon e.V., Benoît Sibaud, cpm, daimonduff, emus, Holger, IM , Ludovic Bocquet, martin, MattJ, MSavoritias (fae,ve), nicfab, Pierre Jarillon, Sam Whited, TheCoffeMaker, wh0nix, vanitasvitae, wurstsalat, Zash for their support and help in creation, review, translation and deployment. Many thanks to all contributors and their continuous support!

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

License

This newsletter is published under CC BY-SA license .

Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of June 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.

Newsletter 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): xmpp.org
• French: jabberfr.org and linuxfr.org
• German: xmpp.org and anoxinon.de
• Italian: nicfab.it
• Spanish: xmpp.org

XSF Announcements

• The XSF membership application period for the third quarter 2022 is currently open. If you are interested in becoming a XSF member then you can apply for membership .

Google Summer of Code 2022

The Google Summer of Code 2022 has lifted off and coding started a while ago! The two new contributors Patiga and PawBud who will work on open-source software projects in the XMPP environment. Read their first blog posts, too.

• Patiga works on more flexible file transfers in Dino . Mentors are fiaxh and Marvin W. .
  • Stateless File Sharing GSoC project
  • Project Stateless File Sharing: First Steps
• PawBud works towards adding support for A/V communication via Jingle in ConverseJS . Mentors are JC Brand and vanitasvitae .
  • On-Boarding Experience with XSF (Converse)

Feel free to spread the word via Mastodon or Twitter . More details in our designated page at xmpp.org .

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:

• Bifrost bridge: Offline messages exchange between Matrix and XMPP
• Mellium Co-op

Events

• 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

Articles

JMP News: Command UI and better transcriptions coming soon .

Nicola Fabiano wrote the article To be «IM apps addicted» or not to be, that is the question. Choose to be free: Snikket, the system messaging based on XMPP protocol highlighting XMPP as his best solution and Snikket as his choice. In another article he states his reasons to avoid WhatsApp, also considering the European Commission’s actions: Persisting with Whatsapp use: how to persevere unknowingly. The whys of our «No» .

Paul Schaub wrote a piece on PGPainless: Reproducible Builds – Telling of a Debugging Story .

Prosody devs got funded by EU’s NGI Assure via the NLnet Foundation to modernize XMPP authentication and authorization so users can secure their sessions with MFA (multi-factor authentication) and have peace of mind with per session controls.

Software news

Clients and applications

Gajim 1.4.3 , 1.4.4 , and 1.4.5 have been released: Gajim’s new versions come with many improvements: emoji auto-complete, automatic theme switching when your desktop switches from light to dark in the evening, a completely reworked Gajim remote interface, and many bug fixes.

Servers

MongooseIM’s new release 5.1 comes with a configuration rework .

Jackal 0.61.0 has been released.

ProcessOne announced ejabberd .deb and .rpm repositories for amd64 and arm64 systems.

Prosody 0.12.1 has been released, and it comes with improved compatibility with Jitsi Meet plus bug fixes for its newly-extended XEP-0227 support.

From the ignite realtime community:

• Smack version 4.4.6 has been released .
• Openfire REST API plugin has been released in version 1.8.1 .

Libraries

No news this month.

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

By the way, xmpp.org features a new page about XMPP RFCs .

Proposed

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.

• WebSocket S2S
  • This specification defines a procedure to make s2s XMPP connections over WebSocket.
• XMPP over QUIC
  • This specification defines a procedure to make both c2s and s2s XMPP connections over the QUIC protocol instead of TCP+TLS.

New

• No New XEPs this month

Deferred

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.

Updated

• No XEPs updated this month.

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.

• External Service Discovery
  • This document specifies an XMPP protocol extension for discovering services external to the XMPP network.

Stable

• No XEPs advanced to Stable this month.

Deprecated

• 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:

• Mastodon
• Twitter
• YouTube
• Lemmy instance
• Reddit
• LinkedIn

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 .

Help us to build the newsletter

This XMPP Newsletter is produced collaboratively by the XMPP community. Therefore, we would like to thank Adrien Bourmault (neox), anubis, Anoxinon e.V., Benoît Sibaud, cpm, daimonduff, emus, guusdk, Holger, Ludovic Bocquet, MattJ, MSavoritias (fae,ve), nicfab, TheCoffeMaker, wh0nix, wurstsalat, Zash for their support and help in creation, review, translation and deployment. Many thanks to all contributors and their continuous support!

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

License

This newsletter is published under CC BY-SA license .

In this blog, I will discuss my GSoC project, and post an update about the work done since the GSoC contribution period started. Ok, so I would like to split the whole project in two phases, with the first GSoC evaluation (29th July) as being the divider. Since it’s only been three weeks, I will only write about the first phase of the project.

About my project

• Expected Hours: 175 Hrs(Medium Project)
  • Adding support for Audio/Video Communication via Jingle.
  • Deliverables / Expected Results:
    • The goal is to create a Converse plugin that adds the ability to make one-on-one audio/video calls from Converse
    • The audio/video calls must be compatible with other XMPP clients such as Conversations .

Jingle protocol works something like this:

In short it signals WebRTC to start/end or modify the status of a session.

Proposed Plan

The first phase, as it stands, will consist of the UI implementation, it’s associated tests and implementaion of XEP 0353 . I genuinely thought that I would be done with the UI implementation till now, but choosing a UI can be surprisingly tough. Given the deadline, I want to make sure that I complete the implementation of the project in time, so for now we (me & my mentor JC) decided to implement a decent looking UI that would be enough to cover all the edge cases and functionality of the project.

UI

Here is a screenshot which shows the current UI.

Do mind the spacing between the Call Initiated text and the End Call button. The call can simply be ended after clicking either the end call button or the call button in the toolbar. Having said that, I presented Discord’s UI to my mentor and he seemed to like it.

Although, we plan to build something much more simpler for converse, it’s good to have a long term vision for this feature.

Tests

As on this date of writing this blog, I am working on integrating XEP 0353. The XEP makes it easier to keep track of my progress since it splits the feature into sections.

You can track my progress through this Pull Request

Hi, I am PawBud. I will be working as a GSoC Contributor with XSF. To know more about my project kindly read this blog . Feel free to contact me through my email to ask me anything you want!

Before I start, I feel that some things that I am going to write in this blog might offend someone. Kindly note that these thoughts are my own . Once again you are free to contact me through my email if you have anything to say, I would be happy to hear your thoughts.

On-Boarding Experience with XSF & Community Bonding Period

Well, I must say, this is unlike any technical internship that you will experience. The level of attention and support that you will get from the organization admins and your project mentors from day 1 is genuinely surprising. I mean, I started having weekly calls with my mentor before the coding period even began, and I am still quite thankful that my mentor(s) spent their time to guide me. Believe it or not, as soon as the results were announced and I saw my name, my first reaction was “oops, well this is bad”. I wasn’t ready for it! Meeting JC (my primary mentor) definitely helped me a lot during the community bonding period. Turns out not everyone does feel the same (thanks to Patiga, I knew about this). Still, from my past experience in internships, I do believe that self-doubt is something that our present-day society profits from, and it is something that one can’t afford if one wants to improve.

I wanted to spend as much time with the source code as I could but my university exams did not allow me to do so. I managed to work on some minor issues though, but I still feel that I need to put in as much work as I can. As of writing this blog, it’s the second week of GSoC. I have to work on designing and implementing a UI for the jingle call modal and will hopefully be done with that and the tests, by the end of this week.

Why Choose GSoC & specifically XSF?

Ok, this is an interesting one, I still remember the special treatment I received from the whole community once the GSoC results were announced. I think Eddie instantly shared the results with the community through the XSF GSoC group chat, Twitter and a couple of other XSF social media pages. I genuinely feel pampered by the overwhelming support of the community, but I am so proud that I chose GSoC over a usual company internship.

I took a course on software engineering during my sophomore year, and until now I have never ever seen/experienced its concepts being implemented. In Converse, I learned more about the applications of test-driven software development in 2 weeks than I ever did during my whole semester. Turns out, that practising a technique is actually the best way to learn it. The fact that my mentor takes out his time which he could very easily spend on developing Converse, just to guide me through the smallest of obstructions, is what really makes this whole thing special. No manager or supervisor in any company is going to give you this kind of attention! Period.

There is this book called Zucked by Roger McNamee. For those of you who haven’t read it here is a gist:- Roger was one of the initial investors of Facebook and a mentor to Mark Zuckerberg. Throughout the book, he explains how Facebook turned into an evil giant, and how the guilt he feels that he could not stop Zuckerberg and Facebook from pivoting to its present-day state. My hate for social media giants like Instagram, Facebook and Twitter, started after I graduated from Secondary School, this was because I started watching a lot of technology-related youtube channels and understood how toxic these social media giants actually are and how they exploit human psychology by giving instant gratification, and blah blah blah. I must say, I was infuriated and disgusted that all this time, I was just a product of these social media giants.

That mentality has grown stronger over the years and yes, I am not on any social media except Reddit, which I occasionally use to text my friends. Hence, XSF was a no-brainer for me, plus I wanted to learn Javascript well, so I only submitted one proposal, which was for Converse.

This was a personal and a non-technical blog post. To be honest, I am still figuring out how to write blogs, as this is my first blog post. I think I will start writing more technical and project-related blog posts after this.

Acknowledgement

In conclusion, I would like to thank my Mentors ( JC & Vanitas), Eddie (XSF GSoC Admin), Patiga (Co-contributor for XSF) and the whole XSF community for putting their trust in me. I would also like to take this opportunity to thank Zerefwayne & Yash Rathore for guiding me in the journey leading up to me getting selected as a contributor for XSF. I look forward to learning from all of you henceforth the GSoC period is finished.

For those of you who could not make it to GSoC with any organization including XSF

Remember, open source is not GSoC. I would honestly still contribute to various organizations, had I not gotten selected to GSoC, because it’s fun! Imagine writing code that is used by potentially millions of users daily. All those late-night hotfixes and mistakes that you do, do become good memories and of course, you get to learn a lot. The open source community is so friendly, that I have yet to see organizations that have core contributors who do not support newcomers.

GSoC should be a side goal in my opinion. If you get selected, that’s good for you. If you don’t get selected, you haven’t lost anything, you simply gain knowledge and contributions.

The Google Summer of Code 2022 is about to lift off and coding starts soon! The XSF has not just been accepted (again!) as a hosting organization for XMPP projects, we also can welcome two new contributors who will work on open-source software projects in the XMPP environment! We have updated our designated web-page for the Google Summer of Code 2022 accordingly.

The XMPP projects at Google Summer of Code 2022

So, please welcome Patiga and PawBud as new contributors! It is really great that you chose XMPP for your coding adventure!

• Patiga will work on more flexible file transfers in Dino . Mentors will be fiaxh and Marvin W. - many thanks to both of you!
  • Resource-wise, messenger applications tend to be on the lightweight side of the spectrum. This drastically changes when file transfers are added to the equation. File transfers can arbitrarily increase resource-usage, both on network and data storage aspects. To alleviate this issue, stateless file sharing empowers the user to make informed decisions on which files to download. Deliverables:
    • Unified handling of HTTP and Jingle (peer-to-peer) file transfers
    • Enable sending metadata alongside files
    • Thumbnail previews for images
• PawBud will work towards adding support for A/V communication via Jingle in ConverseJS . Mentors will be JC Brand and vanitasvitae - many thanks to both of you, too!
  • The idea is to add support for Audio & Video communication through the Jingle protocol. The goal is to create a Converse plugin that adds the ability to make one-on-one audio/video calls from Converse. The audio/video calls will be compatible with other XMPP clients.

Feel free to spread the word via Mastodon or Twitter .

Resources

• Google’s website
• XSF wiki
• Reach us via web chat or review your “Getting started with XMPP” page and reach us via our public chat .

Checkout our media channels, too!

• Twitter
• Mastodon/Fediverse
• Youtube

Looking forward!

–The XSF Organisation Admin

Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of March 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.

Newsletter 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):

• French: jabberfr.org and linuxfr.org
• German: xmpp.org and anoxinon.de
• Italian: nicfab.it
• Spanish: xmpp.org

XSF Announcements

• The XSF has been accepted as hosting organization at 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 . The contributor application period has begun already, so be quick!
• XMPP Newsletter via mail: We migrated to our own mail-list server and stopped using Tinyletter. Its read-only and you will receive the XMPP Newsletter on a monthly basis. It also eliminates the privacy concerns with Tinyletter.

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:

• Bifrost bridge: Offline messages exchange between Matrix and XMPP
• Mellium Co-op

Events

• 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

Articles

The Profanity devs posted a quick guide on how to use OpenPGP for XMPP (OX) .

JMP’s Newsletter announces a new client for Android (based on Conversations) that has a focus on improving UX for users of standards-compliant gateways.

The Mellium Dev Communiqué for March 2022 has been released! This release includes changes to the sidebar in the Communiqué TUI client and improvements to various packages in the main mellium.im/xmpp module.

Software news

Clients and applications

Gajim development news : March brings a new issue reporting system and many performance improvements for both Gajim and python-nbxmpp. Gajim’s OMEMO plugin comes with some improvements as well. Last but not least, there has been a security issue in python-nbxmpp, which has been fixed in version 2.0.6 .

Openfire Pàdé 1.5.7 and 1.6.3 and Openfire Pàdé 1.6.2 have been released.

Profanity 0.12.0 has been released, with in-band account registration and user mood support, new theme, improved OX user experience (as the article above shows) and a slew of fixes and polished features.

Psi+ 1.5.1615 and Psi+ 1.5.1618 have been released.

Conversations 2.10.5 is out, bringing better call reconnections after network switches, showing caller JID and account JID in incoming call screen, adapting the file storage locations per the new Android 11 requirements and a security fix affecting file downloads. Note that the F-Droid version lags behind, due to unrelated issues, but 2.10.2.1 is out and includes only the security fix. Also announced was that accounts on conversations.im are free from now on.

Servers

Jackal 0.58.0 has been released and added the BoltDB repository type.

After three years of development Prosody 0.12.0 has been released. The update covers XMPP Compliance, mobile and connectivity optimizations, updated HTTP file sharing, improved audio/video calling support, Direct TLS and many more - congratulations!

Tigase XMPP Server 8.2.0 has been released! Biggest feature is the support for MIX protocol, which offers better group chat experience, especially on mobile devices. Group chat (MUC) was not left be and received a lot of fixes as well. In addition we improved server-to-server connectivity, added option to store certificates in the repository (really helpful in cluster deployments) and more!

The Ignite Realtime community is happy to announce the immediate availability of a maintenance release 2.2.3 of the GoJara plugin for Openfire . GoJara provides an implementation of XEP-0321 “Remote Roster Management” and helps out with monitoring Spectrum 2 .

Libraries

slixmpp version 1.8.1 has been released, fixing a compatibility issue with the python standard library due to the defusedxml introduction in the 1.8.0 release.

python-nbxmpp versions 2.0.5 and 2.0.6 have been released, fixing a security issue in resolving websocket URIs.

Smack 4.4.5 and 4.5.0-alpha1 has been released.

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

Proposed

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.

New

• Version 0.1.0 of XEP-0462 (PubSub Type Filtering)

  • Accepted by vote of Council on 2022-02-09.

• Version 0.1.0 of XEP-0463 (MUC Affiliations Versioning)

  • Accepted by vote of Council on 2022-02-16.

Deferred

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.

Updated

• Version 1.6.0 of XEP-0115 (Entity Capabilities)

  • Mention preimage attacks explicitly (ssw)

• Version 1.4.0 of XEP-0156 (Discovering Alternative XMPP Connection Methods)

  • Remove DNS _xmppconnect method due to security vulnerability. (tjb)

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.

Stable (formerly known as Draft)

Info: The XSF has decided to rename ‘Draft’ to ‘Stable’. Read more about it here.

• No XEPs advanced to Stable this month.

Deprecated

• No XEP deprecated this month.

Obsoleted

• XEP-0008 (IQ-Based Avatars)

  • Obsoleted due to two superseding specifications (egp)

• XEP-0038 (Icon Styles)

  • Obsolete due to the omnipresence of Unicode emoji, as well as Bits of Binary stickers. (egp)

• XEP-0051 (Connection Transfer)

  • Obsolete because this feature has been merged into XMPP core, see RFC6120 section 4.9.3.19, which describes the stream error. (egp)

• XEP-0138 (Stream Compression)

  • Obsolete due to security vulnerability. (tjb)

• XEP-0229 (Stream Compression with LZW)

  • Obsolete due to security vulnerability. (tjb)

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:

• Mastodon
• YouTube
• Twitter
• Reddit
• LinkedIn

Here you can subscribe via email . It is read-only and only the Newsletter will be send to you on a monthly basis.

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 .

Help us to build the newsletter

This XMPP Newsletter is produced collaboratively by the XMPP community. Therefore, we would like to thank Adrien Bourmault (neox), anubis, Anoxinon e.V., Benoît Sibaud, cpm, daimonduff, emus, Ludovic Bocquet, Licaon_Kter, MattJ, nicfab, Sam Whited, singpolyma, TheCoffeMaker, wurstsalat, Ysabeau, Zash for their support and help in creation, review, translation and deployment. Many thanks to all contributors and their continuous support!

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

License

This newsletter is published under CC BY-SA license .

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.

Newsletter 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):

• French: jabberfr.org and linuxfr.org
• German: xmpp.org/de/blog and anoxinon.de
• Italian: nicfab.it
• Spanish: xmpp.org/es/blog

XSF Announcements

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

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:

• Bifrost bridge: Offline messages exchange between Matrix and XMPP
• Mellium Co-op

Events

• 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

Articles

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

Software news

Clients and applications

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

Psi+ 1.5.1605 has been released with OMEMO fixes.

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

Tigase released BeagleIM 5.1 and SiskinIM 7.1 featuring improved OMEMO support.

Servers

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

Libraries

Mellium Co-op has released v0.21.0 and 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 .

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

Tigase had several releases for their products: Halcyon 0.0.17 , JaXMPP 3.5.0 , Tigase Swift 3.1.0 , and Tigase Swift-OMEMO 2.1.0 .

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

Proposed

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.

• PubSub Type Filtering

  • This specification provides a way to filter PubSub nodes in a disco query.

• MUC Affiliations Versioning

  • This specification provides a way to reduce the amount of queries necessary to stay up-to-date with affiliations in a MUC room.

New

• No new XEPs this month.

Deferred

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.

Updated

• Version 2.13.0 of XEP-0004 (Data Forms)

  • Add incomplete submission form handling (melvo)

• Version 1.24.1 of XEP-0060 (Publish-Subscribe)

  • Add hint for processing incomplete submission forms (melvo)

• Version 1.24.0 of XEP-0060 (Publish-Subscribe)

  • Advertise support for publishing items
  • Replace ‘allow’ with ‘allows’ (melvo)

• Version 1.23.0 of XEP-0060 (Publish-Subscribe)

  • Clarify (redefine) pubsub#type field. (edhelas, pep)

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.

Stable (formerly known as Draft)

Info: The XSF has decided to rename ‘Draft’ to ‘Stable’. Read more about it here.

• No XEPs advanced to Stable this month.

Deprecated

• 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:

• Mastodon
• YouTube
• Twitter
• Reddit
• LinkedIn

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 .

Help us to build the newsletter

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
• translations

License

This newsletter is published under CC BY-SA license .