libQuotient
libQuotient copied to clipboard
quotient-im
A Qt library to write cross-platform clients for Matrix
It is well-known that uMatriks, Tensor and Quaternion have duplicating code, and it would be great if it were collected into a separate library. libqmatrixclient, though, strives to target (still...
There should be a setting that allows to skip on `m.notice` events when determining whether a room has unread messages.
Apparently the thing is a rage these days, so probably have to prioritise its implementation, despite not even being properly specced yet. Enables LarreaMikel/uMatriks#50.
Blocking is more important because it is supposed to effectively ban devices from conversation, while verifying "merely" allows to decorate that certain messages come from an actually verified source.
Without this, adoption of libqmatrixclient boils down to reusing parts of Tensor/Quaternion, which is not always the best way (especially for special-purpose cases).
While a naïve implementation would be dead simple (just add @room to the highlight-setting logic mentioned in #106), the proper implementation should follow the spec and Synapse/Riot behaviour described in...
The relevant code is already in Quaternion (see `Message` to start with); it only takes to pick the backend part of it and move to `QMatrixClient::TimelineItem`.
Now that Quaternion gains multiple accounts support, a need arises to have a `ConnectionManager` singleton that would create, keep, and delete `Connection` objects. This same singleton would own a `NetworkAccessManager`...
Quaternion and Tensor now have very similar (since Tensor borrowed it from Quaternion sometime ago) code to produce some representation of any `RoomEvent`. At least parts of this should go...
(From the commit message:) This is behind a configuration switch because direct unauthenticated requests are at odds with the Matrix model where clients stick to their homeservers and only homeservers...
Metadata
Owner
Metadata
A Qt library to write cross-platform clients for Matrix