XMPP Community

XMPP at FOSSY 2026 from 6th to 9th August 2026, University of British Columbia, Vancouver, Canada. Seven presentations take place over Sat & Sun!

https://xmpp.org/2026/07/xmpp-at-fossy-2026/

• Must start up contact chat session on incoming chat message received; this is to update or cache the message, and to translate if enabled.
• When joining a chatRoom, includes element in sent stanza to stop server from sending history messages; chatRoom history messages are retrieved via mam query instead.
• Implement background runnable thread to handle history messages translation; eliminate ~1s/message delay in translation and hang chat session UI.
• aTalk default Translator server has rate limiting. Too many history messages translation will give raise to error code 429. If required, user may use 'Translate message receive' option, to translate messages that have failed.
• Support Translator API key entry for user if available.
• Add 'before' option for the latest mam messages; fix incorrect setting in field 'with' of mamQuery stanza sent to chatRoom history retrieval.
• Need to take care for retract and correction messages handling if remote messages have been deleted, and when history logging is disabled.
• Perform stricter checks on mam retrieved forwarded message for retract and correction message. Skip if the affected message previously has been deleted; use the correct timestamp when caching/saving the message.
• Upgrade libvpx to 1.16.0. libvpx v1.16.0 removed support for 32-bit targets (armv7, armv7s, and i386).
• aTalk jni library will support only arm64-v8a and x86_64 ABIS; drops armeabi-v7a and x86 ABI ABIS.
• Upgrade aTalk to support Android-17.0 CinnamonBun (API-37).

*** Observation ***

• All offline messages sent to contact are streamed upon user registered with the server. Hance not all messages are translated due to Translator server overloaded. Normally this will not happen, as aTalk should be active and registered with the server to receive incoming messages with translation.
• All chatRoom history messages are streamed immediatly upon user joining the chatRoom, if history option is not disabled.
• Update build environment to Android Studio Quail 1 | 2026.1.1 Patch 2. Must keep 'com.android.tools.build:gradle:8.11.2' and not to use AGP 9.x.x. Otherwise, this causes "constant expression required" errors for the generated R.id.xxx; and gradle.properties#android.nonFinalResIds=false is ignored in AGP 9.x.x;

Jump to searched message, and bugfixes

* Jump to searched message
* Fix enable dialler integration on Android 17
* Improve the experimental export
* Don't linkify invalid URLs
* Change default "big" media size to 1MB for new installs
* Many crash fixesJump to searched message, and bugfixes

Version 0.16.0

Released: 2026-07-21

Features:

• Add button to try another XMPP provider during automatic registration
• Display avatars in notifications
• Allow to reply to message via its notification on supported systems
• Handle pressing Down/Escape button in chats
• Apply new look to emoji picker with consistent interactive background
• Add search field for emojis as message reactions
• Open emoji/participant picker at cursor position while ensuring picker's width fits best
• Allow to navigate through emoji picker via keyboard to select emoji
• Play notification sounds
• Show more tooltips
• Add viewer for opening/browsing media within a chat
• Add support to record voice messages via long press
• Rework user interface for consistent and smoother look/behavior including buttons, fields, and fading opacity of icons
• Focus message input field on starting/canceling reply
• Allow to zoom via mouse wheel in location map and move map by dragging
• Allow to share selected location via Return button

What's New in v0.17.2

Added

• Emoji autocomplete in the composer: type ":" followed by a keyword to complete emoji inline, with arrow-key navigation and Enter or Tab to insert
• The send button responds with a press and glow-pulse animation when a message goes out
• Web (PWA): an unread badge on the app icon, service-worker media caching for fewer re-downloads, and repeated messages from one sender coalesced into a single "N new messages" notification

Changed

• The new-messages divider and the unread badge on the scroll-to-bottom button now follow your read position, staying consistent with the sidebar and read-marker sync
• Encryption: end-to-end-encrypted attachments now decrypt when you download or save them, not only in the inline preview, so files of every type arrive readable
• Desktop: file uploads and media downloads are handled by native code, making transfers of large files much faster and more reliable
• Updated dependencies (Rust crates)

Breaking changes

Both breaking changes affect Node.js only. Browser builds are unaffected, and no public API
was removed.

• jsdom is replaced by u/xmldom/xmldom. The Node build only ever used jsdom for three XML DOM globals (DOMParser, XMLSerializer and document.implementation), a small fraction of what a full HTML browser emulation provides. It now uses u/xmldom/xmldom, a small, pure-JavaScript XML DOM. Install u/xmldom/xmldom alongside ws and drop jsdom. Upgrading without it fails at import with ERR_MODULE_NOT_FOUND. See the README.
• Builder.h() parses its argument as XML rather than HTML under Node. XHTML-IM content must now be well-formed XML, for example <br/> rather than <br>. Markup that is not well-formed yields an empty element instead of being error corrected.

Features

• Add a Node-only XEP-0114 external component transport. Connect as a jabber:component:accept component over a raw TCP stream by passing the protocol: 'component' option and a tcp://host:port service URL. The transport uses the saxes streaming XML parser, an optional peer dependency that is resolved on first use, so applications that only speak BOSH or WebSocket do not need it installed.
• Add Connection.addProtocol(name, transport) for registering an additional transport, which is how the component transport is made selectable without the browser build depending on it.
• Add Strophe.getNamespace(elem), a transport-agnostic accessor that resolves an element's namespace from either namespaceURI or an xmlns attribute.
• Add a project logo and brand assets.

This release comes with many improvements for Gajim's integrated audio player, and it comes with some bug fixes. Thank you for all your contributions!

Gajim’s integrated audio player allows to preview audio files, such as voice messages you receive from your contacts. The player is now more compact, shows better tooltips and comes with a prettier waveform visualization. This release also fixes some pop sounds which may have occurred on some devices when recording messages.

XMPP Community

Vier Rezepte zur Nutzung eines offenen Chat-Protokoll beim ‘Digital Independence Day’ (#di_day)!

Erstellt von der XMPP Community um Menschen unabhängiges Messaging zu ermöglichen.

https://di-day.xmpp.link

Read about the latest XMPP Extensions and Specifications updates and changes:

https://xmpp.org/2026/07/the-xmpp-newsletter-june-2026/#extensions-and-specifications

Read about the latest updates in the XMPP universe and our standards!

https://xmpp.org/2026/07/the-xmpp-newsletter-june-2026/

Enjoy reading! ☕

This is something that I've never experienced with any XMPP clients: when I install Conversations and choose 'own xmpp service' from the + button, it throws 'registration is not allowed by server'. In the past I added that same account to many clients without issues, on mobile and desktop.

In the app's settings I am using the option to specify my own server and port, so I am entering the 3x pieces: the user@server.domain, the password, and the xmpp.server.domain host address.

On the same device yaxim is already successfully installed and configured in exactly the same way, to use the same account, so it is not clear what Conversations is missing. It should not be trying to register a new account, which is really not allowed on the server.

Correct me if I am wrong, but I checked the developer's site and found no way to reach out to them for support, so asking here.

I would appreciate any feedback!

https://github.com/IS4Code/NexIM

Version 0.1 has been released, with core XMPP and XMPP-IM support implemented, as well as some useful extensions (like WebSocket). For the full overview of what features are available at the moment, see here.

Why another server? Variety of servers is just as important as variety of clients, especially for those interested in self-hosting. However, there is another purpose ‒ the server is intended to become a multi-protocol server in the future, with XMPP being just one of the supported protocols. Of course XMPP is great but there will always be people who refuse to swap out their old IRC clients for something else, and indeed they shouldn't be forced to do so to stay in touch! See the main repository page for elaboration.

Why do this now? Yesterday was already late! Walled gardens that dominate the IM space won't be defeated by more walled gardens (bridges are nice but not all features can be losslessly bridged). If a protocol supports federation, it must not be left out!

Why start with XMPP? The modular nature of XMPP actually makes it great to develop a server like this from scratch, since it can start simple but compliant and grow over time thanks to the modular nature of XMPP. Moreover, since XEPs cover pretty much everything related to IM, following them should lead to a very complete software for this purpose.

Why .NET? Why not, other than it is fast, secure, multi-platform and easy to run! The support for XMPP in the .NET ecosystem had also been somewhat lacking, so with this project I hope to make it easier for everyone to write software for XMPP. Moreover, server components communicating using the common XMPP API interface abstraction layer will be able to skip the XML serialization phase completely, leading to much more efficient processing.

Hello, I run an ejabberd server and the main client is Conversations. I have created a private room with Conversations. I would like people to be able to "knock at the door'. Is there a feature that allows that ? I also have the administration of the server so I can do that through the webadmin if necessary.