Joshua Goins 5b6e5a25e5 Allow opening message menus for out-of-room events
These are more common than we thought, good examples are pinned or
searched messages - which are not going to be in the room's history
unless you happen to have them loaded. But currently our message menu
infrastructure expects them to be, since its looked up by the room +
event ID.

To fix this is simple, we now move the job of finding the event to the
caller which may use a model instead. I didn't fix all existing
call-sites yet, mainly the message menu opening one since that was the
most obvious bug. But this opens up the door for other assumptions about
room history to be fixed too.

I had to do a bit of C++ re-jiggering in order to expose useful
functions to QML.
2026-01-11 18:30:02 -05:00
2021-04-02 23:55:13 +00:00
2025-11-10 17:27:25 +00:00
2023-09-27 16:23:29 +02:00
2026-01-11 01:44:50 +00:00
2024-12-22 18:23:55 +00:00
2025-05-02 20:43:39 +02:00
2026-01-04 13:48:30 +00:00
2021-01-27 14:51:10 +01:00
2026-01-04 13:48:30 +00:00
2021-01-27 18:54:13 +01:00
2021-05-22 19:12:29 +00:00
2023-09-27 23:43:55 -04:00
2025-08-11 23:18:56 +02:00
2025-05-11 11:11:52 +01:00

NeoChat

A Qt/QML based Matrix client.

Made for Matrix Download on Flathub Download on the Snap Store

Introduction

NeoChat is a client for Matrix, the decentralized communication protocol for instant messaging.

NeoChat is based on KDE frameworks and as libQuotient, a Qt-based SDK for the Matrix Protocol.

Timeline

Features

NeoChat aims to be a fully featured application for the Matrix specification. As such most parts of the current specification are supported, with the notable exceptions of VoIP, threads, and some aspects of End-to-End Encryption. There are a few other smaller omissions due to the fact that the Matrix spec is constantly evolving, but the aim remains to provide eventual support for the entire spec.

Due to the nature of the Matrix specification development NeoChat also supports numerous unstable features. Currently these are:

  • Polls - MSC3381
  • Sticker Packs - MSC2545
  • Location Events - MSC3488

Get it

Details where to find stable releases for NeoChat can be found on its homepage.

Nightly builds for Linux and Windows can be downloaded from cdn.kde.org. Nightly builds for Android are available from KDE's nightly F-Droid repository. Nightly Flatpaks are available from KDE's nightly Flatpak repository.

Building NeoChat

The best way to build KDE apps during development is to use kdesrc-build. The full instructions for this can be found on the KDE community website's get involved section under development. This is primarily aimed at Linux development.

For Windows and Android Craft is the primary choice. There are guides for setting up development environments for Windows and Android.

Running

Just start the executable in your preferred way - either from the build directory or from the installed location.

Tests

Tests are in the repository under autotests and appiumtests.

The project has CI setup to test new commits to the repository. All tests are expected to pass for a merge request to be complete.

Current build status

coverage

Currently the number of tests is limited, but growing. If anyone wants to help improve this, those contributions would be especially welcome.

Contributing

As is the case throughout the KDE ecosystem contributions are welcome from all. The code base is managed in the NeoChat repository of the KDE Gitlab instance.

Contact

The best place to reach the maintainers is on the KDE Matrix instance in the NeoChat channel, #neochat:kde.org. See Matrix for more details.

Acknowledgement

NeoChat utilizes libQuotient as its Matrix SDK.

NeoChat is a fork of Spectral.

License

GPLv3

This program is licensed under GNU General Public License, Version 3.

Description
A client for matrix, the decentralized communication protocol
Readme 74 MiB
Languages
C++ 51.4%
QML 31.5%
C 15.1%
CMake 1.5%
Python 0.5%