[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

jami-20220726.1515.da8d1da released [stable]

From: Amin Bandali
Subject: jami-20220726.1515.da8d1da released [stable]
Date: Wed, 27 Jul 2022 15:32:51 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)

The Jami team is pleased to announce a new stable release of Jami,

What is Jami?

Jami is a GNU package for universal communication that respects the
freedom and privacy of its users.

Jami is an end-to-end encrypted secure and distributed voice, video,
and chat communication platform.  Jami requires no central server
for these communications and leaves the power of privacy and freedom
in the hands of users.

Jami provides the following key features to its users:

- Synchronized and enriched one-to-one conversations
- Group conversations (Beta)
- Audio/video calls and conferences
- Screen sharing in video calls and conferences
- Unlimited peer-to-peer file sharing
- Recording and sending audio/video messages
- Jami plugins SDK for additional functionality (green screen,
  watermark, audio filters, and more)
- Using Jami as your SIP phone with a variety of media codecs
  and VoIP providers

Jami 20220726.1515.da8d1da release highlights

The highlights of this new stable release of Jami include:

- The main graphical user interface of Jami, jami-client-qt or jami-qt
  for short, now supports macOS in addition to GNU/Linux and Windows,
  bringing Jami to an important milestone of having a single, unified
  client application on all our supported desktop operating systems.
  See our recent article 'Unified Jami application across desktop
  platforms'[1] to learn more.
- Beta of phase two of Swarm: synchronized group conversations of up
  to 8 members.  This experimental feature can be enabled from the
  General settings.  We recommend trying this experimental feature on
  a secondary account, to avoid risks with your primary account and
  its conversations.
  - Swarms are fully distributed, peer-to-peer chats with conversation
    histories synchronized across your devices.  To learn more about
    Swarms, see our earlier articles 'Swarm: a new generation of group
    conversations'[2] and 'Synchronizing conversation history with
  - In phase two of Swarm support, Swarms enable synchronization of
    small group conversations of up to 8 members, in addition to the
    existing 1-to-1 conversations synchronized across multiple devices
    associated with the same account.
- Improved and more flexible video conference layouts thanks to the
  'videosplit' series of patches.  This enables video conference
  participants to resize the row of participants locally, without
  affecting its display for other participants.
- Enable video conference participants to share both their camera and
  an additional media feed (such as a screen share) simultaneously.
- Allow increasing, decreasing, and resetting font sizes (text zoom)
  using Ctrl++, Ctrl+-, and Ctrl+0 respectively, in jami-client-qt.
- Various improvements to the Jami plugins system, including allowing
  translation of plugins like the rest of Jami.
- Make the sidebar in the main view fully resizable.
- Message 'read' statuses are now synchronized across devices.
- Use the correct/native theme on KDE.
- Use informative titles for missed call notifications.
- Don't perpetually run animations for invisible elements of the user
  interface in jami-client-qt, helping drastically reduce GPU usage
  with the OpenGL backend.
- Many other improvements and bug fixes in Jami's connectivity and
  media stack, such as a large refactoring of Jami's video pipelines
  which brings major performance improvements and fixes a variety of
  video-related crashes.

Some notable developer-oriented changes in this release include:

- Merging LibJamiClient (previously LibRingClient or LRC for short)
  into the jami-client-qt git repository and deprecating the older and
  separate jami-libclient repository.  For the Jami packages built and
  distributed via our repositories on this means that the
  jami-libclient package is no longer needed for the latest versions,
  and can be safely removed.  Further simplifications and cleanups in
  the project structure and packaging are planned for future releases.
- Making the Qt WebEngine dependency of jami-client-qt optional, which
  can help reduce the size of jami-client-qt's dependency graph
  drastically (especially useful in embedded development scenarios),
  and enable GNU FSDG distributions that don't package Qt WebEngine to
  package jami-client-qt without any issues.

For a detailed and comprehensive list of changes see the changelog[4].


Download Jami 20220726.1515.da8d1da

Pre-built Jami binaries/packages for various GNU/Linux distributions
and other platforms can be downloaded from
If you had previously installed Jami from the repositories of your
GNU/Linux distribution of choice and it has not been updated for a
while, you can instead install Jami following the instructions at the
above link for regularly-updated Jami packages.

Here are the compressed sources:   (86MB)   (83MB)

Here are the GPG detached signatures:

Use a mirror for higher download bandwidth:

Here are the SHA1 and SHA256 checksums:

8a0dba639649567079f2aacf8e36e0cf4877657e  jami-20220726.1515.da8d1da.tar.gz
f062f04f58631db1a8df250a1474c2c180932542  jami-20220726.1515.da8d1da.tar.xz

Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact.  First, be sure to download both the .sig file
and the corresponding tarball.  Then, run a command like this:

  gpg --verify jami-20220726.1515.da8d1da.tar.gz.sig

The signature should match the fingerprint of the following key:

  pub   rsa4096 2018-10-17 [C]
        BE62 7373 8E61 6D6D 1B3A  08E8 A21A 0202 4881 6103
  uid   Amin Bandali <>
  uid   Amin Bandali <>
  uid   Amin Bandali <>
  uid   Amin Bandali <>
  uid   Amin Bandali <>
  uid   Amin Bandali <>
  uid   Amin Bandali <>
  uid   Amin Bandali <>

If that command fails because you don't have the required public key,
or that public key has expired, try the following commands to retrieve
or refresh it, and then rerun the 'gpg --verify' command.

  gpg --locate-external-key

  gpg --recv-keys BE6273738E616D6D1B3A08E8A21A020248816103

As a last resort to find the key, you can try the official GNU

  wget -q
  gpg --keyring gnu-keyring.gpg --verify jami-20220726.1515.da8d1da.tar.gz.sig

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]