Work is still ongoing to improve communication reliability and efficiency, especially on mobile devices.


The medium-term project to change the way users associate new devices with their Jami Account is making good progress, as a first prototype is now working in the Jami Core.

Smoke test scenarios have been drawn up to provide a basis for automatic testing.

In the upcoming months, we're honing in on two primary objectives for DHTNet:

  1. Addressing a multitude of bugs to boost Jami's connectivity. This week, we have already started tackling bugs that directly affect Jami's performance.
  2. Preparing the first release of DHTNet as a standalone library, poised for integration into different projects. So far, our work has been focused on this.


Screen sharing on Wayland with Pipewire has been merged in Jami, and is still in review to be integrated in FFmpeg.


The last two weeks have been devoted to automating test launches when modifications are made to the code.

While still experiencing difficulties implementing automatic testing on all the systems, the Android team is also in the process of eliminating a few small UI bugs, including those related to importing an account from another device.


With the discovery of major bugs and in-depth work underway to improve reliability, the Jami iOS team has been working on push notification management, as well as a new preference screen, which is now only in the design phase.

A new user interface for creating smart lists and swarms is also under development.


The ongoing work on JAMS has mostly been focused on the users' web interface, such as :

  • Enforced strict typing rules
  • Added a CI/CD stage to enforce code style rules
  • General bug fixes of the client
  • Revamped UI on the client

Keep up to date with our progress on Jami. A lot of groundwork, not yet visible to the user, has been underway since January, and you should start to reap the rewards in the coming months. 😏