The Jami team is pleased to announce a major release of Jami, Világfa. You can read the full announcement article on the Jami blog: https://jami.net/vil/
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 - 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-20230206.0 (Világfa) release highlights -------------------------------------------- Highlights from the Világfa release of Jami: - Group swarm conversations (currently up to 8 members). - Added swarm details panel showing various aspects of swarm conversations including settings (e.g. conversation colour, and notification preferences), members (for group swarms), and shared documents, as well as synchronization of several of these aspects across devices. - Improved audio processing with voice activity detection (and indication), automatic gain control, noise reduction, and echo cancellation. - Replying to a specific message in swarm. - Reacting to messages with emojis. - Improved displaying of message read status. - Support for sharing location and displaying others' shared location. - Support for opening "jami:" URIs/links in Jami on GNU/Linux. - Support for using the system theme on GNU/Linux and Windows. - Support for translation of plugins. - Improved participants layout in certain call/conference scenarios. - Added video preview to the initial call view displayed while ringing for incoming or outgoing calls. - Added 'advanced information' call overlay. - New and improved swarm file transfer subsystem: https://jami.net/swarm-file-transfers/ - Improved calling experience using swarm: https://jami.net/improving-call-experience-in-jami/ - Improved performance in calls. - Improved UI/UX and visuals, thanks to several revamped views (e.g. the new account wizard and the main welcome view). - Additions and improvements to keyboard shortcuts for convenience and improved accessibility. - Many other improvements and bug fixes across various Jami subsystems including the connectivity and media stacks. Some notable developer-oriented changes in this release include: - The naming scheme used for the Jami release tarballs has been changed from the previous 'jami_YYYYMMDD.hhmm.COMMIT.tar.gz' to 'jami-YYYYMMDD.X.tar.gz', where 'YYYYMMDD' is the date of the last commit on the current branch, and 'X' the number of releases tagged that day, starting from zero. The new format is shorter, omits the unnecessary and confusing commit id, and uses dash instead of underscore. Also, it contains everything in a top-level directory with the same name as the tarball (without the .tar.gz extensions), so that jami-YYYYMMDD.X.tar.gz nicely extracts to jami-YYYYMMDD.X. With these changes, Jami release tarballs will follow more closely the related instructions from the GNU maintainers manual. - Use of the jami-project.git repository for continuous integration and packaging has been deprecated in favour of consolidating all of these aspects in jami-client-qt.git repository itself, organized mostly under the 'extras' directory. The 'daemon' submodule at the repository top-level points to a recent version of the daemon known to build and work with the Qt client. Also, the 'build.py' script at the repository top-level can be used to conveniently install the dependencies and build the Jami daemon and client from source. - The 'DRing' C++ namespace of the Jami daemon/library has been renamed to 'libjami'. For a detailed and comprehensive list of changes see the changelog: https://git.jami.net/savoirfairelinux/jami-client-qt/-/wikis/Changelog Download jami-20230206.0 (Világfa) ---------------------------------- Pre-built Jami binaries/packages for various GNU/Linux distributions and other platforms can be downloaded from https://jami.net/download. 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: https://ftp.gnu.org/gnu/jami/jami-20230206.0.tar.gz (94MB) https://ftp.gnu.org/gnu/jami/jami-20230206.0.tar.xz (90MB) Here are the GPG detached signatures: https://ftp.gnu.org/gnu/jami/jami-20230206.0.tar.gz.sig https://ftp.gnu.org/gnu/jami/jami-20230206.0.tar.xz.sig Use a mirror for higher download bandwidth: https://www.gnu.org/prep/ftp.html Here are the SHA1 and SHA256 checksums: 4606f9b8bd45fc5bc827f777112e891cf4a6dab0 jami-20230206.0.tar.gz 2e8c473083481a7ddd2ac6fc6dc80032cfb86f67 jami-20230206.0.tar.xz 5f8e16402bfb3c19361b89d810f57bf8dac1f59da4fdff18c2a30389b061a7bb jami-20230206.0.tar.gz cf0e361fe70bb00070cf723059008f0bdadb125f85be6684a0aca721fc9f463e jami-20230206.0.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-20230206.0.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 <band...@gnu.org> uid Amin Bandali <band...@kelar.org> uid Amin Bandali <m...@gnu.org> uid Amin Bandali <band...@uwaterloo.ca> uid Amin Bandali <band...@csclub.uwaterloo.ca> uid Amin Bandali <a...@shemshak.org> uid Amin Bandali <aband...@uwaterloo.ca> uid Amin Bandali <aband...@csclub.uwaterloo.ca> uid Amin Bandali <amin.band...@savoirfairelinux.com> uid Amin Bandali <amin.band...@canonical.com> uid Amin Bandali <band...@canonical.com> 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 band...@gnu.org gpg --recv-keys BE6273738E616D6D1B3A08E8A21A020248816103 As a last resort to find the key, you can try the official GNU keyring: wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg gpg --keyring gnu-keyring.gpg --verify jami-20230206.0.tar.gz.sig
signature.asc
Description: PGP signature
