matrix-rust-sdk
matrix-rust-sdk copied to clipboard
Matrix Client-Server SDK for Rust
as per discussion: > Is there a reason that the Crypto SDK's Swift Request enum doesn't include a .signingKeysUpload? Skimming through some of the Rust code, e.g. [mark_request_as_sent](https://github.com/matrix-org/matrix-rust-sdk/blob/331ea35be6278351f3179b5e287353aa53845df6/crates/matrix-sdk-crypto/src/machine.rs#L388), it seems...
#1245 exposed `MembershipState` to the FFI but left ` _Custom(PrivOwnedStr)` for later. This will need to be implemented.
Currently is is possible to set a pusher, but not to delete one. The exposed API to add a pusher is: ```rs /// Registers a pusher with given parameters pub...
This patch removes `FrozenSlidingSyncRoom::timeline`, which means we no longer cache on-disk the latest events (up to 10). This feature will be back in a cleaner way with `matrix_sdk_ui::event_graph`. Because `FrozenSlidingSyncRoom::timeline`...
I don't think that the Device blacklist functionality is used anymore. I am not aware of clients offering this option. Should we get rid of this concept? Should also remove...
Since #1447 we create a root span for our `Client` object, and since https://github.com/matrix-org/matrix-rust-sdk/pull/1428 EX can push traces to an OpenTelemetry collector, aka Jaeger in this case. # Structured logging...
… since it's a non-sensical combination.
Depends on: https://github.com/ruma/ruma/pull/1704 This only adds helper functions to the FFI to send call notify events. Signed-off-by: Timo K - [x] Public API changes documented in changelogs (optional) Signed-off-by:
On Element Android X and Element iOS X we've noticed that it takes a significant amount of time to get the list of members in a room. Eyeballing the network...
On some clients, like Element X we would like to still keep state events, but not show read receipts on them, however this would create an issue where RRs would...