xmatic

Submitted by JimKnopfIoT on Mon, 2026/08/31 - 19:17

Rating:

Your rating: None Average: 5 (6 votes)

Native Matrix client built on matrix-rust-sdk with a Silica UI.

FEATURES

- Sliding sync, end-to-end encryption, cross-signing, device verification (both directions), key backup and recovery
- Rooms, spaces (nested), direct chats, threads (answer in one or start one), room directory search
- Create rooms, invite, leave; member list and member profiles with moderation
- Send, edit, delete, reply, pagination in encrypted rooms
- Search the messages of a conversation. The index lives on the device and is encrypted with the same key as the rest of the local storage; the query never leaves the phone
- Formatted messages: bold, italic, code, quotes, lists and links render as themselves
- Pinned messages, favourites, low priority, per-room mute, ignored users
- A line marks where reading stopped. A room opens there or at its newest message, whichever you set, and says who has read what
- A message whose authenticity could not be confirmed carries a mark next to its time, with a page explaining what each mark means
- Four coloured lines say how safe the device is: backup, recovery, cross-signing, local storage
- Reactions from an emoji picker whose first tab you fill yourself
- Pictures, files, sharing (also as share target from Gallery / file manager)
- Voice messages; voice and video calls (classic 1:1 VoIP; MatrixRTC-only clients cannot be called)
- Notifications, offline send queue, encrypted local storage
- OAuth (MAS) login, device-code login, password login
- 29 interface languages, switchable in the app

LANGUAGES

The interface is available in the 24 official languages of the European Union
plus Russian, Norwegian, Icelandic, Simplified Chinese and Hindi. Norwegian was contributed by a Norwegian
speaker and German is the project language; the rest are machine translations,
usable but unchecked. Account has a language setting of its own, English
included, so there is always a way back out of one. A change applies at the
next start.

Corrections are welcome at the GitHub repository below - the file to edit is
translations/harbour-xmatic-<language>.ts, and translations/STATUS.md says
which languages have been read by a native speaker.

LOCAL STORAGE

Session tokens and the message database are encrypted with a key from Sailfish
Secrets.

Some Sailfish images ship only the client library of that key service and not
the service itself. On such a device xmatic no longer creates an unencrypted
database quietly: it says what is missing, gives the command to install it and
a command to check the result with, and offers to continue without encryption
as an explicit choice. The package also requires the service, so on most
devices this never comes up.

An installation that already holds data is never blocked - that would strand
its room keys. Where a database simply predates the key, the encryption page
offers to re-create it encrypted, which costs one sign-out and your recovery
key.

How safe the device is stands in four coloured lines - backup, recovery,
cross-signing, local storage. Green is in order, orange is something you can
put right, red is something the system does not offer. If anything is not
green, the app says so once after starting, with the action that fits and
"later" always available. When everything is green you never see any of it.

WHY IS THE PACKAGE SO BIG?

The app ships the complete Matrix stack statically: matrix-rust-sdk, E2EE
(vodozemac), sliding sync, rustls, its own HTTP runtime and a bundled SQLite.
None of that exists as a system library on Sailfish OS, and Qt 5.6 is too old
for the C++ alternatives - which is exactly why the protocol core is written in
Rust. Installed size ~60 MB (Element X, same SDK: ~100 MB), RPM ~18 MB.

NO BACKGROUND DAEMON

Messages arrive while the app is running (the cover is enough). Like other
daemonless messengers on this platform, a closed app does not receive.

ARCHITECTURES

aarch64 (Sailfish OS 5.0+), armv7hl (Sailfish OS 4.6+). Tested on J2, Xperia10III and Gemini PDA.

REQUIREMENTS

xmatic syncs over simplified sliding sync (MSC4186), the same mechanism
Element X uses. Your homeserver must support it. If it does not, sign-in
works but no rooms load and the app keeps showing "Offline".

How to check your server: open this address in a browser

https://YOUR-SERVER/_matrix/client/versions

and look for this line:

"org.matrix.simplified_msc3575": true

If it is missing, xmatic cannot load your rooms from that server.

Sign-in methods supported: OAuth 2.0 / Matrix Authentication Service,
device code ("Sign in on another device"), and username plus password on
servers without OAuth.

The classic SSO redirect sign-in (SAML, CAS) is not supported.

Written with Claude Code (Anthropic), icons included; the protocol core is upstream matrix-rust-sdk.

Source, issues, releases:
https://github.com/JimKnopfIoT/harbour-xmatic

Screenshots:

Keywords:

Application versions:

Attachment	Size	Date
harbour-xmatic-0.27.0-1.aarch64.rpm	17.39 MB	31/08/2026 - 19:16
harbour-xmatic-0.27.0-1.armv7hl.rpm	17.91 MB	31/08/2026 - 19:16

Changelog:

- Messages can be searched, one conversation at a time, from the room's pull-down menu. The index lives on the device and is encrypted with the same key as the rest of the local storage; the query never leaves the phone. There is no server-side search and no fallback to one - a homeserver cannot read an encrypted room, so it could only ever search the rooms this app does not have. Opening the search page hands it whatever history is already on the device, so a room that has been scrolled back is searchable to that point. What it cannot do is written on the page itself: whole words only, so "test" does not find "test9", and only plain text - captions, file names and anything a bot sends are not in it. - The line marking where reading stopped is drawn for everybody now. It existed before but hung off a setting about *other* people's read status, which is off by default, so almost nobody ever saw it. It is independent of that setting, and it holds still while the room is read instead of sliding to the newest message. Where the room opens is a setting of its own (Display, on by default): at the last read message, or at the newest one with the line found by scrolling up. - A message whose authenticity could not be confirmed carries a mark instead of a sentence. A line of text under every affected message said the same thing twenty times over; a red triangle or an orange dot says it once, in the line that already holds the time. Nothing is hidden - every affected message keeps its mark, because leaving it off the ones below the first would claim they are fine. Tapping a mark shows what it means for that message, and leads to a page listing all six cases. - The unread count was wrong after every start. Messages that arrived while the app was closed were counted as one, however many there were, while the notification for the same room named the right number. The counters are computed on the device from the messages a sync has actually carried, and a sync carried exactly one per room. It carries what is needed now. - A room opened from a notification, from a direct chat or by following an upgrade shows its name in the header. Only the chat list passed one, so those three arrived with an identifier and left the header empty. - The chat list says how many rooms the server counts next to the number it holds, so "20 of 412" tells a missing room apart from a list that has not finished growing.

Comments

stoefelz

Tue, 2026/09/01 - 20:14

Search form

Main menu

You are here

User login

Categories

Tags Cloud

Recent comments

Who's online

xmatic

Category:

Keywords:

Comments