Slidge is an XMPP gateway designed to connect your account to third-party chat networks like WhatsApp, Telegram, or Matrix. It acts as a bridge, allowing you to send and receive messages with all your contacts directly from your single, preferred XMPP client.

This guide provides instructions to configure an Openfire XMPP server to work with Slidge and the Slidge WhatsApp plugin as an example.

Openfire requires configuration in its Admin Console to allow external components like Slidge to connect and to grant them the necessary permissions for features like file transfers.

Prerequisites

Before you begin, ensure you have:

• A running and accessible Openfire server.
• Administrative access to the Openfire Admin Console.
• Root or sudo access to the Debian/Ubuntu server where you will install Slidge.
• The Slidge Debian repository added to your system, as per the official Slidge installation instructions ( Installation - Slidge documentation ).

This guide used the below install method.

• ( https://codeberg.org/slidge/debian )

Step 1: Configure Openfire Services

You must configure Openfire to accept the bridge connection and handle file transfers before you configure Slidge.

1.1. Install and Configure HTTP File Upload Plugin

Slidge requires a working XEP-0363 HTTP File Upload component to send and receive images, videos, and other files.

• Log in to your Openfire Admin Console.
• Navigate to Server → Plugins → Available Plugins.
• Find the plugin named “HTTP File Upload” and click the green + icon to install it.
• After installation, navigate to Server → Server Settings → HTTP File Upload.
• Ensure the box for “Enable HTTP File Upload” is checked.

Take note of the configuration. For a standard setup behind a reverse proxy, your public URL might be https://upload.your.domain while the internal service address is httpfileupload.your.domain .
We will use this internal address later.

• Click Save Settings.

1.2. Enable External Component Connections

This step allows Openfire to listen for incoming connections from bridges.

In the Openfire Admin Console, navigate to Server → Server Settings → External Components.

• Ensure the service is Enabled.
• Under the “Allowed to Connect” section, define your new WhatsApp bridge:
• Subdomain: whatsapp (This will create the JID whatsapp.your.domain ).
• Shared Secret: Create a new, strong, random password.
• Copy this shared secret to a safe place. You will need it for the Slidge configuration.
• Click “Add”.

Your Openfire server is now ready for Slidge.

Step 2: Install and Configure Slidge

Now, on your server’s command line, we will install and configure the Slidge packages.

2.1. Install Slidge Packages

As per these instructions: slidge/debian: Debian (unofficial) package bundling slidge-based gateways. - Codeberg.org

2.2. Configure common.conf

This file contains settings shared by all your bridges.

• Edit the file: nano /etc/slidge/conf.d/common.conf
• Set the following parameters:

  admins=admin@your.domain
  upload-service=httpfileupload.your.domain
  user-jid-validator=.*@your.domain
  server=localhost
  #port=5347 #(default slidge setting)
  port=5275 #(openfire default)
  

2.3. Configure whatsapp.conf

This file contains the settings for the WhatsApp bridge specifically.

• Create or edit the file: nano /etc/slidge/whatsapp.conf
  (I just did mv /etc/slidge/whatsapp.conf.example /etc/slidge/whatsapp.conf )
• Add the connection details to match what you configured in Openfire:

  # The XMPP address of your bridge component
  jid = whatsapp.your.domain
  # The shared secret you created in the Openfire admin console
  secret = PASTE_YOUR_SHARED_SECRET_HERE
  legacy-module=slidge.plugins.whatsapp
  

Step 3: Start and Verify Slidge

Enable and start the Slidge WhatsApp service:

sudo systemctl enable --now slidge@whatsapp

Check the logs to ensure it started without errors:

sudo journalctl -u slidge@whatsapp -f

Step 4: User Registration and Login

From your XMPP client (e.g., Conversations, Gajim), discover the services on your server. You should see the “WhatsApp” bridge listed.

Register with the service.

The bridge ( whatsapp.your.domain ) will be added to your contacts. Send it the message login or qr.

(I just started a conversation with a new chat to whatsapp.you.domain and typed help , it gives a list of commands, follow these e.g register )

You may see warnings in the Slidge log about “IQ privileges not granted” for pubsub and bookmarks (XEP-0356).

Troubleshooting: Fixing Permission Warnings (not yet implemented in Openfire so can’t fix this just yet)

For good luck I also did this at the end.

sudo systemctl restart openfire
sudo systemctl restart slidge@whatsapp

3 posts - 2 participants

Read full topic

Slidge is an XMPP gateway designed to connect your account to third-party chat networks like WhatsApp, Telegram, or Matrix. It acts as a bridge, allowing you to send and receive messages with all your contacts directly from your single, preferred XMPP client.

This guide provides instructions to configure an Openfire XMPP server to work with Slidge and the Slidge WhatsApp plugin as an example.

Openfire requires configuration in its Admin Console to allow external components like Slidge to connect and to grant them the necessary permissions for features like file transfers.

Prerequisites

Before you begin, ensure you have:

• A running and accessible Openfire server.
• Administrative access to the Openfire Admin Console.
• Root or sudo access to the Debian/Ubuntu server where you will install Slidge.
• The Slidge Debian repository added to your system, as per the official Slidge installation instructions ( Installation - Slidge documentation ).

This guide used the below install method.

• ( https://codeberg.org/slidge/debian )

Step 1: Configure Openfire Services

You must configure Openfire to accept the bridge connection and handle file transfers before you configure Slidge.

1.1. Install and Configure HTTP File Upload Plugin

Slidge requires a working XEP-0363 HTTP File Upload component to send and receive images, videos, and other files.

• Log in to your Openfire Admin Console.
• Navigate to Server → Plugins → Available Plugins.
• Find the plugin named “HTTP File Upload” and click the green + icon to install it.
• After installation, navigate to Server → Server Settings → HTTP File Upload.
• Ensure the box for “Enable HTTP File Upload” is checked.

Take note of the configuration. For a standard setup behind a reverse proxy, your public URL might be https://upload.your.domain while the internal service address is httpfileupload.your.domain .
We will use this internal address later.

• Click Save Settings.

1.2. Enable External Component Connections

This step allows Openfire to listen for incoming connections from bridges.

In the Openfire Admin Console, navigate to Server → Server Settings → External Components.

• Ensure the service is Enabled.
• Under the “Allowed to Connect” section, define your new WhatsApp bridge:
• Subdomain: whatsapp (This will create the JID whatsapp.your.domain ).
• Shared Secret: Create a new, strong, random password.
• Copy this shared secret to a safe place. You will need it for the Slidge configuration.
• Click “Add”.

Your Openfire server is now ready for Slidge.

Step 2: Install and Configure Slidge

Now, on your server’s command line, we will install and configure the Slidge packages.

2.1. Install Slidge Packages

As per these instructions: slidge/debian: Debian (unofficial) package bundling slidge-based gateways. - Codeberg.org

2.2. Configure common.conf

This file contains settings shared by all your bridges.

• Edit the file: nano /etc/slidge/conf.d/common.conf
• Set the following parameters:

  admins=admin@your.domain
  upload-service=httpfileupload.your.domain
  user-jid-validator=.*@your.domain
  server=localhost
  #port=5347 #(default slidge setting)
  port=5275 #(openfire default)
  

2.3. Configure whatsapp.conf

This file contains the settings for the WhatsApp bridge specifically.

• Create or edit the file: nano /etc/slidge/whatsapp.conf
  (I just did mv /etc/slidge/whatsapp.conf.example /etc/slidge/whatsapp.conf )
• Add the connection details to match what you configured in Openfire:

  # The XMPP address of your bridge component
  jid = whatsapp.your.domain
  # The shared secret you created in the Openfire admin console
  secret = PASTE_YOUR_SHARED_SECRET_HERE
  legacy-module=slidge.plugins.whatsapp
  

Step 3: Start and Verify Slidge

Enable and start the Slidge WhatsApp service:

sudo systemctl enable --now slidge@whatsapp

Check the logs to ensure it started without errors:

sudo journalctl -u slidge@whatsapp -f

Step 4: User Registration and Login

From your XMPP client (e.g., Conversations, Gajim), discover the services on your server. You should see the “WhatsApp” bridge listed.

Register with the service.

The bridge ( whatsapp.your.domain ) will be added to your contacts. Send it the message login or qr.

(I just started a conversation with a new chat to whatsapp.you.domain and typed help , it gives a list of commands, follow these e.g register )

You may see warnings in the Slidge log about “IQ privileges not granted” for pubsub and bookmarks (XEP-0356).

Troubleshooting: Fixing Permission Warnings (not yet implemented in Openfire so can’t fix this just yet)

For good luck I also did this at the end.

sudo systemctl restart openfire
sudo systemctl restart slidge@whatsapp

3 posts - 2 participants

Read full topic

Slidge is an XMPP gateway designed to connect your account to third-party chat networks like WhatsApp, Telegram, or Matrix. It acts as a bridge, allowing you to send and receive messages with all your contacts directly from your single, preferred XMPP client.

This guide provides instructions to configure an Openfire XMPP server to work with Slidge and the Slidge WhatsApp plugin as an example.

Openfire requires configuration in its Admin Console to allow external components like Slidge to connect and to grant them the necessary permissions for features like file transfers.

Prerequisites

Before you begin, ensure you have:

• A running and accessible Openfire server.
• Administrative access to the Openfire Admin Console.
• Root or sudo access to the Debian/Ubuntu server where you will install Slidge.
• The Slidge Debian repository added to your system, as per the official Slidge installation instructions ( Installation - Slidge documentation ).

This guide used the below install method.

• ( https://codeberg.org/slidge/debian )

Step 1: Configure Openfire Services

You must configure Openfire to accept the bridge connection and handle file transfers before you configure Slidge.

1.1. Install and Configure HTTP File Upload Plugin

Slidge requires a working XEP-0363 HTTP File Upload component to send and receive images, videos, and other files.

• Log in to your Openfire Admin Console.
• Navigate to Server → Plugins → Available Plugins.
• Find the plugin named “HTTP File Upload” and click the green + icon to install it.
• After installation, navigate to Server → Server Settings → HTTP File Upload.
• Ensure the box for “Enable HTTP File Upload” is checked.

Take note of the configuration. For a standard setup behind a reverse proxy, your public URL might be https://upload.your.domain while the internal service address is httpfileupload.your.domain .
We will use this internal address later.

• Click Save Settings.

1.2. Enable External Component Connections

This step allows Openfire to listen for incoming connections from bridges.

In the Openfire Admin Console, navigate to Server → Server Settings → External Components.

• Ensure the service is Enabled.
• Under the “Allowed to Connect” section, define your new WhatsApp bridge:
• Subdomain: whatsapp (This will create the JID whatsapp.your.domain ).
• Shared Secret: Create a new, strong, random password.
• Copy this shared secret to a safe place. You will need it for the Slidge configuration.
• Click “Add”.

Your Openfire server is now ready for Slidge.

Step 2: Install and Configure Slidge

Now, on your server’s command line, we will install and configure the Slidge packages.

2.1. Install Slidge Packages

As per these instructions: slidge/debian: Debian (unofficial) package bundling slidge-based gateways. - Codeberg.org

2.2. Configure common.conf

This file contains settings shared by all your bridges.

• Edit the file: nano /etc/slidge/conf.d/common.conf
• Set the following parameters:

  admins=admin@your.domain
  upload-service=httpfileupload.your.domain
  user-jid-validator=.*@your.domain
  server=localhost
  #port=5347 #(default slidge setting)
  port=5275 #(openfire default)
  

2.3. Configure whatsapp.conf

This file contains the settings for the WhatsApp bridge specifically.

• Create or edit the file: nano /etc/slidge/whatsapp.conf
  (I just did mv /etc/slidge/whatsapp.conf.example /etc/slidge/whatsapp.conf )
• Add the connection details to match what you configured in Openfire:

  # The XMPP address of your bridge component
  jid = whatsapp.your.domain
  # The shared secret you created in the Openfire admin console
  secret = PASTE_YOUR_SHARED_SECRET_HERE
  legacy-module=slidge.plugins.whatsapp
  

Step 3: Start and Verify Slidge

Enable and start the Slidge WhatsApp service:

sudo systemctl enable --now slidge@whatsapp

Check the logs to ensure it started without errors:

sudo journalctl -u slidge@whatsapp -f

Step 4: User Registration and Login

From your XMPP client (e.g., Conversations, Gajim), discover the services on your server. You should see the “WhatsApp” bridge listed.

Register with the service.

The bridge ( whatsapp.your.domain ) will be added to your contacts. Send it the message login or qr.

(I just started a conversation with a new chat to whatsapp.you.domain and typed help , it gives a list of commands, follow these e.g register )

You may see warnings in the Slidge log about “IQ privileges not granted” for pubsub and bookmarks (XEP-0356).

Troubleshooting: Fixing Permission Warnings (not yet implemented in Openfire so can’t fix this just yet)

For good luck I also did this at the end.

sudo systemctl restart openfire
sudo systemctl restart slidge@whatsapp

3 posts - 2 participants

Read full topic

It is exciting to be able to announce the immediate availability of the beta release of Openfire 5.0.0!

In this release, we have addressed approximately 125 issues! I’ll reserve the details for a blog post on the 5.0.0 (non-beta) release, but some of the important changes are:

• We’ve dropped support for Java 11. The minimum requirement is Java 17 now
• The embedded web server has received a major upgrade
• Various security-related updates were applied, including library updates and code changes that resulted from an independent security audit (more on that later!)

This beta release (and some of its precursors) have been extensively tested by the developers and other members of the Ignite Realtime community. At this stage, we’re not seeing any critical issues. However, prior to cutting the full release, we prefer to have more feedback. That is where you come in!

We are looking for your help!

Please help us test this release! If you host your own instance of Openfire, please consider upgrading it to the new beta release. If you can’t, or if you’re not running Openfire but another brand of XMPP server, please do some interoperability testing with the server at igniterealtime.org .

Are you a client developer? Please see how your application behaves, when connecting to the beta (we can make available accounts for testing to help you do this).

If you’re nothing of a tech-head but can use an XMPP client, try to interact with our domain (for example, join our chatroom at open_chat@conference.igniterealtime.org ) to see if there are any issues.

You can obtain the beta from our download page for beta releases or from the GitHub Releases page .

We would love to hear from you! If you have any questions, please stop by our community forum or our live groupchat . We are always looking for volunteers interested in helping out with Openfire development!

For other release announcements and news follow us on Mastodon or X

1 post - 1 participant

Read full topic

It is exciting to be able to announce the immediate availability of the beta release of Openfire 5.0.0!

In this release, we have addressed approximately 125 issues! I’ll reserve the details for a blog post on the 5.0.0 (non-beta) release, but some of the important changes are:

• We’ve dropped support for Java 11. The minimum requirement is Java 17 now
• The embedded web server has received a major upgrade
• Various security-related updates were applied, including library updates and code changes that resulted from an independent security audit (more on that later!)

This beta release (and some of its precursors) have been extensively tested by the developers and other members of the Ignite Realtime community. At this stage, we’re not seeing any critical issues. However, prior to cutting the full release, we prefer to have more feedback. That is where you come in!

We are looking for your help!

Please help us test this release! If you host your own instance of Openfire, please consider upgrading it to the new beta release. If you can’t, or if you’re not running Openfire but another brand of XMPP server, please do some interoperability testing with the server at igniterealtime.org .

Are you a client developer? Please see how your application behaves, when connecting to the beta (we can make available accounts for testing to help you do this).

If you’re nothing of a tech-head but can use an XMPP client, try to interact with our domain (for example, join our chatroom at open_chat@conference.igniterealtime.org ) to see if there are any issues.

You can obtain the beta from our download page for beta releases or from the GitHub Releases page .

We would love to hear from you! If you have any questions, please stop by our community forum or our live groupchat . We are always looking for volunteers interested in helping out with Openfire development!

For other release announcements and news follow us on Mastodon or X

1 post - 1 participant

Read full topic

It is exciting to be able to announce the immediate availability of the beta release of Openfire 5.0.0!

In this release, we have addressed approximately 125 issues! I’ll reserve the details for a blog post on the 5.0.0 (non-beta) release, but some of the important changes are:

• We’ve dropped support for Java 11. The minimum requirement is Java 17 now
• The embedded web server has received a major upgrade
• Various security-related updates were applied, including library updates and code changes that resulted from an independent security audit (more on that later!)

This beta release (and some of its precursors) have been extensively tested by the developers and other members of the Ignite Realtime community. At this stage, we’re not seeing any critical issues. However, prior to cutting the full release, we prefer to have more feedback. That is where you come in!

We are looking for your help!

Please help us test this release! If you host your own instance of Openfire, please consider upgrading it to the new beta release. If you can’t, or if you’re not running Openfire but another brand of XMPP server, please do some interoperability testing with the server at igniterealtime.org .

Are you a client developer? Please see how your application behaves, when connecting to the beta (we can make available accounts for testing to help you do this).

If you’re nothing of a tech-head but can use an XMPP client, try to interact with our domain (for example, join our chatroom at open_chat@conference.igniterealtime.org ) to see if there are any issues.

You can obtain the beta from our download page for beta releases or from the GitHub Releases page .

We would love to hear from you! If you have any questions, please stop by our community forum or our live groupchat . We are always looking for volunteers interested in helping out with Openfire development!

For other release announcements and news follow us on Mastodon or X

1 post - 1 participant

Read full topic

XMPP Newsletter Banner

Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of May 2025.

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 .

XMPP Events

• XMPP Italian happy hour [IT]: monthly Italian XMPP web meeting, every third Monday of the month at 7:00 PM local time (online event, with web meeting mode and live streaming).
• The XMPP Sprint in Berlin took place during the 23rd-25th of May 2025. Developers from Germany, France & the United Kingdom representing Conversations , Dino , ejabberd , Kaidan , LiveDashboard, Macaw, Monal , Renga , and Prose gathered to make it happen! The sprint was sponsored by the XSF , Ammonit Measurement GmbH, and Wikimedia e.V. .

A still from the XMPP Sprint in Berlin, May 2025

Videos

• Goffi , from Libervia , published a short progress overview of the new web frontend design on the Libervia video channel .

Talks

• On Friday, May 16, Vril hosted the Workshop di XMPP e Free Software all’AntiBiennale di Venezia (a workshop on XMPP and free software) at Cabasego, in Venice, Italy. The whole workshop lasted around one and a half hours and the slides are freely available for you to check out . The event took place in a most beautiful house, incredibly located in the center of Venice, inhabited by people who are always willing to leave their door open to Venice’s underground communities. [IT]

XMPP Articles

• El gran lío de la mensajería instantánea by Jacobo Da Riva Muñoz . [ES]
• Monocles , the project responsible for the XMPP Monocles chat Web and Android clients, started a crowdfunding campaign . The main goal is to create a platform where privacy, digital sovereignty and sustainability take center stage. Your privacy is non-negotiable. The funding period will span from March 28 to June 30.
• XMPP is now featured on the list of the ‘Delightful Lists’.
• Towards a Password-Mukt XMPP for some thoughts and fantasies by Badri (Hippo) on how passwordless XMPP login could be achieved, either via an out-of-band mechanism or by authorizing from an already logged-in client.
• XMPP packages coming with Debian 13 as the freeze toward next stable Debian (13 or Trixie) has been engaged, an overview of the XMPP clients, servers and librairies coming with it is provided in this article from the Debian XMPP Team.

XMPP Software News

XMPP Clients and Applications

• Converse.js has released version 11.0.0 of its open-source and web-based XMPP chat client. The Desktop version can be downloaded from here . This release comes packed full of bugfixes, changes and new features. Way too many to list in here. Make sure to check out the release link for all the details!

Converse 11

• Gajim has released version 2.2.0 . This release brings three new features: message retraction (via XEP-0424: Message Retraction ), blocking participants in group chats, and updated support for modern group chat avatars (via XEP-0486: MUC Avatars ), among many other improvements and bugfixes. Head over to their news section or check the changelog for all the details.
• Monal has released version 6.4.11 for iOS an macOS.
• Monocles Chat 2.0.7 for Android, has been released. This version brings fixes for lagging, pinned status message, I2P and more.
• Prose has released versions 0.10.1 of its web frontend prose-web-app .

XMPP Servers

• Prosody IM is pleased to announce version 13.0.2 . This update addresses various issues that have been noticed since the previous release, as well as a few improvements, including some important fixes for invites. Some log messages and prosodyctl commands have been improved as well. Read all the details on the release changelog . As always, detailed download and install instructions are available on the download page for your convenience.

XMPP Libraries & Tools

• Pade plugin version 1.8.4 for Openfire has been released.
• peertube-plugin-livechat version 12.0.4 has been released.
• python-nbxmpp version 6.2.0 has been released.
• strophejs version 3.1.1 has been released.

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

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

• 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 can help improve the XEP before returning it to the Council for advancement to Stable.

• No Last Call this month.

Stable

• No XEPs moved to Stable this month.

Deprecated

• No XEPs deprecated this month.

Rejected

• No XEPs rejected this month.

Spread the news

Please share the news on other networks:

• Mastodon
• Movim
• Bluesky
• LinkedIn
• YouTube
• Lemmy instance (unofficial)
• Reddit (unofficial)
• XMPP Facebook page (unofficial)

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 and more languages are welcome! Translations of the XMPP Newsletter will be released here (with some delay):

• English (original): xmpp.org
  • General contributors: Adrien Bourmault (neox), Alexander “PapaTutuWawa”, Arne, Badri Sunderarajan, Benson Muite, cal0pteryx, emus, Federico, Gonzalo Raúl Nemmi, Jonas Stein, Kris “poVoq”, Licaon_Kter, Ludovic Bocquet, Mario Sabatino, melvo, MSavoritias (fae,ve), nicola, Schimon Zachary, Simone Canaletti, singpolyma, XSF iTeam
• French: jabberfr.org and linuxfr.org
  • Translators: Adrien Bourmault (neox), alkino, anubis, Arkem, Benoît Sibaud, mathieui, nyco, Pierre Jarillon, Ppjet6, Ysabeau
• Italian: notes.nicfab.eu
  • Translators: nicola
• Spanish: xmpp.org
  • Translators: Gonzalo Raúl Nemmi
• German: xmpp.org
  • Translators: Millesimus

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

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 you can support:

• Mellium Co-op
• Bifrost bridge
• Prav
• diasp.in

Unsubscribe from the XMPP Newsletter

To unsubscribe from this list, please log in first . If you have not previously logged in, you may need to set up an account with the appropriate email address.

License

This newsletter is published under CC BY-SA license .

XMPP Newsletter Banner

Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of May 2025.

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 .

XMPP Events

• XMPP Italian happy hour [IT]: monthly Italian XMPP web meeting, every third Monday of the month at 7:00 PM local time (online event, with web meeting mode and live streaming).
• The XMPP Sprint in Berlin took place during the 23rd-25th of May 2025. Developers from Germany, France & the United Kingdom representing Conversations , Dino , ejabberd , Kaidan , LiveDashboard, Macaw, Monal , Renga , and Prose gathered to make it happen! The sprint was sponsored by the XSF , Ammonit Measurement GmbH, and Wikimedia e.V. .

A still from the XMPP Sprint in Berlin, May 2025

Videos

• Goffi , from Libervia , published a short progress overview of the new web frontend design on the Libervia video channel .

Talks

• On Friday, May 16, Vril hosted the Workshop di XMPP e Free Software all’AntiBiennale di Venezia (a workshop on XMPP and free software) at Cabasego, in Venice, Italy. The whole workshop lasted around one and a half hours and the slides are freely available for you to check out . The event took place in a most beautiful house, incredibly located in the center of Venice, inhabited by people who are always willing to leave their door open to Venice’s underground communities. [IT]

XMPP Articles

• El gran lío de la mensajería instantánea by Jacobo Da Riva Muñoz . [ES]
• Monocles , the project responsible for the XMPP Monocles chat Web and Android clients, started a crowdfunding campaign . The main goal is to create a platform where privacy, digital sovereignty and sustainability take center stage. Your privacy is non-negotiable. The funding period will span from March 28 to June 30.
• XMPP is now featured on the list of the ‘Delightful Lists’.
• Towards a Password-Mukt XMPP for some thoughts and fantasies by Badri (Hippo) on how passwordless XMPP login could be achieved, either via an out-of-band mechanism or by authorizing from an already logged-in client.
• XMPP packages coming with Debian 13 as the freeze toward next stable Debian (13 or Trixie) has been engaged, an overview of the XMPP clients, servers and librairies coming with it is provided in this article from the Debian XMPP Team.

XMPP Software News

XMPP Clients and Applications

• Converse.js has released version 11.0.0 of its open-source and web-based XMPP chat client. The Desktop version can be downloaded from here . This release comes packed full of bugfixes, changes and new features. Way too many to list in here. Make sure to check out the release link for all the details!

Converse 11

• Gajim has released version 2.2.0 . This release brings three new features: message retraction (via XEP-0424: Message Retraction ), blocking participants in group chats, and updated support for modern group chat avatars (via XEP-0486: MUC Avatars ), among many other improvements and bugfixes. Head over to their news section or check the changelog for all the details.
• Monal has released version 6.4.11 for iOS an macOS.
• Monocles Chat 2.0.7 for Android, has been released. This version brings fixes for lagging, pinned status message, I2P and more.
• Prose has released versions 0.10.1 of its web frontend prose-web-app .

XMPP Servers

• Prosody IM is pleased to announce version 13.0.2 . This update addresses various issues that have been noticed since the previous release, as well as a few improvements, including some important fixes for invites. Some log messages and prosodyctl commands have been improved as well. Read all the details on the release changelog . As always, detailed download and install instructions are available on the download page for your convenience.

XMPP Libraries & Tools

• Pade plugin version 1.8.4 for Openfire has been released.
• peertube-plugin-livechat version 12.0.4 has been released.
• python-nbxmpp version 6.2.0 has been released.
• strophejs version 3.1.1 has been released.

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

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

• 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 can help improve the XEP before returning it to the Council for advancement to Stable.

• No Last Call this month.

Stable

• No XEPs moved to Stable this month.

Deprecated

• No XEPs deprecated this month.

Rejected

• No XEPs rejected this month.

Spread the news

Please share the news on other networks:

• Mastodon
• Movim
• Bluesky
• LinkedIn
• YouTube
• Lemmy instance (unofficial)
• Reddit (unofficial)
• XMPP Facebook page (unofficial)

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 and more languages are welcome! Translations of the XMPP Newsletter will be released here (with some delay):

• English (original): xmpp.org
  • General contributors: Adrien Bourmault (neox), Alexander “PapaTutuWawa”, Arne, Badri Sunderarajan, Benson Muite, cal0pteryx, emus, Federico, Gonzalo Raúl Nemmi, Jonas Stein, Kris “poVoq”, Licaon_Kter, Ludovic Bocquet, Mario Sabatino, melvo, MSavoritias (fae,ve), nicola, Schimon Zachary, Simone Canaletti, singpolyma, XSF iTeam
• French: jabberfr.org and linuxfr.org
  • Translators: Adrien Bourmault (neox), alkino, anubis, Arkem, Benoît Sibaud, mathieui, nyco, Pierre Jarillon, Ppjet6, Ysabeau
• Italian: notes.nicfab.eu
  • Translators: nicola
• Spanish: xmpp.org
  • Translators: Gonzalo Raúl Nemmi
• German: xmpp.org
  • Translators: Millesimus

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

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 you can support:

• Mellium Co-op
• Bifrost bridge
• Prav
• diasp.in

Unsubscribe from the XMPP Newsletter

To unsubscribe from this list, please log in first . If you have not previously logged in, you may need to set up an account with the appropriate email address.

License

This newsletter is published under CC BY-SA license .

XMPP Newsletter Banner

Welcome to the XMPP Newsletter, great to have you here again! This issue covers the month of May 2025.

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 .

XMPP Events

• XMPP Italian happy hour [IT]: monthly Italian XMPP web meeting, every third Monday of the month at 7:00 PM local time (online event, with web meeting mode and live streaming).
• The XMPP Sprint in Berlin took place during the 23rd-25th of May 2025. Developers from Germany, France & the United Kingdom representing Conversations , Dino , ejabberd , Kaidan , LiveDashboard, Macaw, Monal , Renga , and Prose gathered to make it happen! The sprint was sponsored by the XSF , Ammonit Measurement GmbH, and Wikimedia e.V. .

A still from the XMPP Sprint in Berlin, May 2025

Videos

• Goffi , from Libervia , published a short progress overview of the new web frontend design on the Libervia video channel .

Talks

• On Friday, May 16, Vril hosted the Workshop di XMPP e Free Software all’AntiBiennale di Venezia (a workshop on XMPP and free software) at Cabasego, in Venice, Italy. The whole workshop lasted around one and a half hours and the slides are freely available for you to check out . The event took place in a most beautiful house, incredibly located in the center of Venice, inhabited by people who are always willing to leave their door open to Venice’s underground communities. [IT]

XMPP Articles

• El gran lío de la mensajería instantánea by Jacobo Da Riva Muñoz . [ES]
• Monocles , the project responsible for the XMPP Monocles chat Web and Android clients, started a crowdfunding campaign . The main goal is to create a platform where privacy, digital sovereignty and sustainability take center stage. Your privacy is non-negotiable. The funding period will span from March 28 to June 30.
• XMPP is now featured on the list of the ‘Delightful Lists’.
• Towards a Password-Mukt XMPP for some thoughts and fantasies by Badri (Hippo) on how passwordless XMPP login could be achieved, either via an out-of-band mechanism or by authorizing from an already logged-in client.
• XMPP packages coming with Debian 13 as the freeze toward next stable Debian (13 or Trixie) has been engaged, an overview of the XMPP clients, servers and librairies coming with it is provided in this article from the Debian XMPP Team.

XMPP Software News

XMPP Clients and Applications

• Converse.js has released version 11.0.0 of its open-source and web-based XMPP chat client. The Desktop version can be downloaded from here . This release comes packed full of bugfixes, changes and new features. Way too many to list in here. Make sure to check out the release link for all the details!

Converse 11

• Gajim has released version 2.2.0 . This release brings three new features: message retraction (via XEP-0424: Message Retraction ), blocking participants in group chats, and updated support for modern group chat avatars (via XEP-0486: MUC Avatars ), among many other improvements and bugfixes. Head over to their news section or check the changelog for all the details.
• Monal has released version 6.4.11 for iOS an macOS.
• Monocles Chat 2.0.7 for Android, has been released. This version brings fixes for lagging, pinned status message, I2P and more.
• Prose has released versions 0.10.1 of its web frontend prose-web-app .

XMPP Servers

• Prosody IM is pleased to announce version 13.0.2 . This update addresses various issues that have been noticed since the previous release, as well as a few improvements, including some important fixes for invites. Some log messages and prosodyctl commands have been improved as well. Read all the details on the release changelog . As always, detailed download and install instructions are available on the download page for your convenience.

XMPP Libraries & Tools

• Pade plugin version 1.8.4 for Openfire has been released.
• peertube-plugin-livechat version 12.0.4 has been released.
• python-nbxmpp version 6.2.0 has been released.
• strophejs version 3.1.1 has been released.

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

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

• 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 can help improve the XEP before returning it to the Council for advancement to Stable.

• No Last Call this month.

Stable

• No XEPs moved to Stable this month.

Deprecated

• No XEPs deprecated this month.

Rejected

• No XEPs rejected this month.

Spread the news

Please share the news on other networks:

• Mastodon
• Movim
• Bluesky
• LinkedIn
• YouTube
• Lemmy instance (unofficial)
• Reddit (unofficial)
• XMPP Facebook page (unofficial)

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 and more languages are welcome! Translations of the XMPP Newsletter will be released here (with some delay):

• English (original): xmpp.org
  • General contributors: Adrien Bourmault (neox), Alexander “PapaTutuWawa”, Arne, Badri Sunderarajan, Benson Muite, cal0pteryx, emus, Federico, Gonzalo Raúl Nemmi, Jonas Stein, Kris “poVoq”, Licaon_Kter, Ludovic Bocquet, Mario Sabatino, melvo, MSavoritias (fae,ve), nicola, Schimon Zachary, Simone Canaletti, singpolyma, XSF iTeam
• French: jabberfr.org and linuxfr.org
  • Translators: Adrien Bourmault (neox), alkino, anubis, Arkem, Benoît Sibaud, mathieui, nyco, Pierre Jarillon, Ppjet6, Ysabeau
• Italian: notes.nicfab.eu
  • Translators: nicola
• Spanish: xmpp.org
  • Translators: Gonzalo Raúl Nemmi
• German: xmpp.org
  • Translators: Millesimus

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

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 you can support:

• Mellium Co-op
• Bifrost bridge
• Prav
• diasp.in

Unsubscribe from the XMPP Newsletter

To unsubscribe from this list, please log in first . If you have not previously logged in, you may need to set up an account with the appropriate email address.

License

This newsletter is published under CC BY-SA license .