Install Trinity
Trinity is an end-to-end encrypted Matrix client. Release 0.4.0 is available for macOS, Windows and Linux, and as a self-hostable web app (PWA). Android and iOS apps are still in development.
Downloads are attached to the latest release.
Apple Silicon, macOS 13 or later. With Homebrew:
brew install --cask quwisky/trinity/trinityOr download the .dmg from the latest release. It is signed with a Developer ID and
notarized by Apple.
Windows
Section titled “Windows”Download the .exe installer from the latest release. The installer is not code-signed
yet, so Windows SmartScreen shows “Windows protected your PC”: choose More info, then
Run anyway.
x86-64 only. Download the .deb or the AppImage from the latest release. On Debian and
Ubuntu, prefer the .deb: AppImages need libfuse2, and recent Ubuntu releases restrict
the sandbox they rely on.
On Debian and Ubuntu:
sudo apt install ./trinity-desktop_0.4.0_amd64.debWith the AppImage:
chmod +x Trinity-0.4.0.AppImage./Trinity-0.4.0.AppImageRun the web app on your own server from the container image:
docker run -d -p 8080:8080 ghcr.io/quwisky/trinity-web:latestThen open http://localhost:8080. You can also serve the static files from
Trinity-Web-0.4.0.zip with any web server. For HTTPS, headers and updates, see
Self-host a release
in the developer guide.
Get help
Section titled “Get help”Report problems on GitHub Issues.
Server requirements
Section titled “Server requirements”From Trinity 0.3, signing in through your server’s own sign-in page (OAuth 2.0, also called next-generation authentication) needs Synapse 1.138 or newer when the server uses Matrix Authentication Service (MAS). Tuwunel 1.6 or newer and Continuwuity 26.6 or newer provide OAuth 2.0 sign-in themselves; older releases do not. On an older Synapse with MAS, Trinity cannot offer that sign-in page, and an account that is already signed in stops connecting the next time its access token expires. Trinity keeps the account and its encryption keys on the device. Before you update, turn on key backup, or ask your server’s admin to upgrade Synapse first. If an account has already stopped connecting, export your room keys, then remove the account and sign in again.