Since the release of Atlas: Jami’s biggest step toward reliable communication, work hasn’t slowed down. On the contrary: the past few months have been about tightening the bolts, cleaning up edge cases, and making day-to-day use more predictable and reliable.
For this fifteenth edition, we’re bringing you: more control over 1:1 conversations, more accurate presence indicators, sturdier group calls, improved security on macOS, and a touch of extra customization on Desktop.
Every update makes your Jami experience a little more robust.
🔧 CORE
1:1 conversations, clean up without losing contacts
You can now delete a 1:1 conversation without removing the associated contact.
This gives you more control over your history: you can clear a thread that’s no longer relevant, keep your address book intact, and avoid the awkward “I deleted you by mistake” moment.
While implementing this, we uncovered and fixed several synchronization issues between contacts and conversations. Those fixes help keep your conversations list more consistent across devices when you modify or remove histories.
Presence indicator: green really means “online”
The presence indicator (the green/orange dot showing whether a contact is connected) was sometimes out of sync with reality. In a peer-to-peer system, presence is already a subtle thing; an unreliable indicator doesn’t help.
We’ve fixed this bug that could cause this status to be wrong in some cases. You should now see a presence state that better reflects what’s actually happening on the network.
Group calls: steady improvements after Atlas
Group calls remain one of the main focuses since Atlas. We’ve merged a series of commits in the daemon to make multi-party communication more resilient and less fragile in tricky conditions.
This includes several improvements such as:
- fixes to group call handling and internal signaling, like this set of changes,
- additional stability work, including this patch, this one, and this one.
Many of these changes target edge cases: unstable networks, participants joining and leaving rapidly, or complex device setups. You may not see them directly, but you should feel them during longer, more complex calls. And there’s more to come in the next iterations.
Fewer crashes, fewer deadlocks
We’ve identified and fixed various crashes and deadlocks in the daemon. These are the kind of bugs that might show up only in specific sequences of events, but when they do, they completely block your experience.
Each one removed is one less reason for Jami to freeze or quit unexpectedly.
🖥️ DESKTOP
macOS: App Sandbox for jami.net builds
On macOS, Jami has long used the App Sandbox, a security mechanism that isolates applications from the rest of the system, for the version distributed through the App Store.
However, the version downloaded directly from jami.net did not benefit from this protection. That’s now fixed: thanks to this change in the Qt client, the jami.net macOS builds now also run inside the App Sandbox.
What this means for you:
- better isolation of Jami from the rest of your system,
- a reduced attack surface,
- a more consistent security level between App Store and jami.net versions.
If you prefer installing from the website, you now get the same security benefits without changing your habits.
Qt Desktop: a customizable home background
On the Desktop (Qt) client, you can now change the background image on the home screen, a feature requested and tracked in this GitLab issue.
This allows you to:
- align Jami with your organization’s visual identity,
- distinguish between different environments (work, personal, community),
- or simply make the app feel more like your own space.
Small touches like this don’t change the core protocol, but they do change how it feels to open Jami every day.
Supporting Jami: why donations matter
We are already working on the next set of changes, with the same goal in mind: to make Jami a tool you can rely on at all times. But to support these improvements, we need your help.
Jami is free software: no ads, no tracking, no data sold to third parties, and no central server owned by a company that monetizes your communications.But this philosophy comes at a cost: building maintaining that kind of infrastructure, and testing a peer-to-peer communication platform requires time, resources, and a dedicated team is not free.
If you can, please support the project with a donation to fund ongoing development, increase testing and optimization on all platforms, and strengthen a truly free and privacy-respecting alternative.
Thank you for your support.
