mirror of
https://github.com/matrix-org/matrix-rust-sdk.git
synced 2026-06-13 19:04:23 -04:00
e47867f232
The supported versions are necessary for querying almost all endpoints, but after homeserver auto-discovery the well-known info is only necessary to get the MatrixRTC foci advertised by the homeserver. So it shouldn't be necessary to always request both at the same time. Besides: - Not all clients support MatrixRTC, so they don't need the well-known info. - The well-known info is only supposed to be used for homeserver auto-discovery before login. In fact, the MatrixRTC MSC was changed to use a new endpoint for this. - We don't have access to the server name after restoring the Client, so the well-known lookup is more likely to fail. Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
Matrix Rust SDK bindings
In this directory, one can find bindings to the Rust SDK that are maintained by the owners of the Matrix Rust SDK project.
appleormatrix-rust-components-swift, Swift bindings of thematrix-sdkcrate viamatrix-sdk-ffi,matrix-sdk-crypto-ffi, UniFFI (Kotlin, Swift, Python, Ruby) bindings of thematrix-sdk-cryptocrate,matrix-sdk-ffi, UniFFI bindings of thematrix-sdkcrate.
There are also external bindings in other repositories:
matrix-sdk-crypto-wasm, JavaScript / WebAssembly bindings of thematrix-sdk-cryptocrate,matrix-sdk-crypto-nodejs, Node.js bindings of thematrix-sdk-cryptocrate
Contributing
To contribute read this guide.