Profanity Illustration

Profanity

Developer Blog

Profanity 0.19.0

jubalh

Wrapping up our catch-up series brings us to our latest release: Profanity 0.19.0, released in October 2026!

4 people contributed code to this release: onf, Jiho Kim, @YHNdnzj, and @jubalh.

A big thank you to all our testers, packagers, and supporters! If you would like to support Profanity development: please donate.

MUC MAM

The main feature of 0.19.0 is that this is the first release that supports MUC MAM.

Previously, MAM was only available for 1:1 direct chats. In 0.19.0:

Major Code Cleanup

Another major goal for 0.19.0 was a comprehensive cleanup and refactoring across the codebase, making Profanity leaner, safer, and easier to maintain. Some notable examples:

MUC Self-Ping (XEP-0410)

Have you ever sat quietly in a MUC wondering why nobody writes anything? Profanity 0.19.0 implements XEP-0410: MUC Self-Ping along with a new /mucping command. If the room ping fails, Profanity detects the broken connection and triggers an automatic rejoin.

Encrypted File Sharing for OX

When using /sendfile in an OX session, only the download link was encrypted in the message, while the actual file sat unencrypted on the HTTP upload server.

In 0.19.0, Profanity now encrypts the file locally with AES-256-GCM (XEP-0454) before uploading it via HTTP File Upload (XEP-0363). The resulting aesgcm:// URL is then transmitted inside an OX signcrypt message. This ensures that both the file stored on the server and the message link are end-to-end encrypted.

You can control this behavior with the new command: /ox encryptfile on|off. Which is enabled by default when Profanity is built with OMEMO support.

Further Highlights

Details

For more information and the full list of features, bug fixes, refactorings, and cleanup, check out the 0.19.0 release notes.