Psi

This program is licensed under the GNU General Public License. See the COPYING file for more information. Psi is an XMPP client designed for experienced users. It is highly portable and runs on GNU/Linux, MS Windows, macOS, FreeBSD, NetBSD and Haiku. User interface of program is very flexible in customization. For example, there are "multi windows" and "all in one" modes, support of different iconsets and themes. Psi supports file sharing and audio/video calls. Security is also a major consideration, and Psi provides it for both client-to-server (TLS) and client-to-client (OpenPGP, OTR, OMEMO) via appropriate plugins. WebKit version of Psi has few additional features (in comparing with basic version of Psi): support of animated emoticons, support of (adium) themes in private chats and group chats, support of previewing of images and videos in private chats and group chats, etc. But if you prefer old fashioned plain text chats from era of IRC heyday, then basic version of Psi is your obvious choice. Better work with embedded video (in chats) in MS Windows. Worse integration to system. (It does not use system theme and fonts in GNU/Linux.) Supports less amount of compilers, systems and CPU architectures. Stability issues in macOS. GNU/Linux and BSD users may install packages from official and unofficial repositories, ports, etc. or download app bundles from SourceForge and install them manually. Program doesn't have embedded mechanism of updates, so in this case users should monitor updates themselves. MS Windows users may download official installers and portable builds from SourceForge. Program doesn't have embedded mechanism of updates, so users should monitor updates themselves. In 2009 a Psi fork named Psi+ was started. Project purposes were: implementation of new features, writing of patches and plugins for transferring them to upstream. As of 2017 all active Psi+ developers have become official Psi developers and now Psi+ is just a development branch of Psi with rolling release development model. Users who wants to receive new features and bug fixes very quickly may use Psi+ on daily basis. Users who do not care about new trends and prefer constancy may choose Psi as it uses classical development model and its releases are quite rare. Psi versions should look like: X.Y (where X and Y are not digits but numbers). Psi+ versions should look like: X.Y.Z (where X , Y and Z are not digits but numbers). All development of Psi is done in master branch of psi repository and its submodules. Each commit to it increases Z part of Psi+ version to one. At some point of time new release branch is detouched from master branch (for example, release-1.x , release-2.x , etc.). All new releases (git tags) will be done in it. Necessary changes from master branch to stable branches should be cherry-picked or moved manually. Do not forget to merge release branch into master after adding of new git tags. Psi plugins are developed separately. Plugins API in guaranteed to be compatible only for git tags. In master branches of psi, plugins and psimedia repos they may be not in sync during development. Psi+ solves this problem by providing all-in-one tarballs (Psi core + all officially supported plugins and resources), see special repository psi-plus-snapshots. All translations are prepared for Psi+ project and are semi-automatically adapted for Psi (using special script). Travis CI: psi, plugins, psimedia, psi-plus. Sibuserv CI: psi, plugins, psi-plus, psimedia. There are a lot of people who were involved into Psi and Psi+ development. Some of them are listed in license headers in source files, some of them might be found only in the history of commits in our git repositories. Also there are translators, makers of graphics and just active users. We are thankful to all them! As we (intentionally) do not have nor beta versions of Psi, nor daily build builds for it, you are invited to use Psi+ program for suggesting and testing of new fea