Damir Jelić

I'll assume that this has been fixed by https://github.com/matrix-org/matrix-rust-sdk/pull/1873. Please feel free to reopen if that's not the case.

How would this make the life of the caller simpler? This is a [builder pattern](https://rust-unofficial.github.io/patterns/patterns/creational/builder.html), if you don't want to set the proxy, don't call the method? What is the...

> That being said, if most of the methods of a builder are called upon construction, we might as well have a ClientBuilderParameters public record, and a Client::new(params: ClientBuilderParameters) method...

Hmm, I don't think it is. Only `serde_json::Value` to handle the custom stuff that might appear in the `DeviceKeys` so signature verification continues to work.

Yup, seems like this is a false alarm. Could you please upstream the test, albeit we could use the `json` macro to make the device keys a bit more readable,...

This turned out to be a non-issue in the end, tests confirming this have been added. Closed by https://github.com/matrix-org/matrix-rust-sdk/issues/3132#issuecomment-2002060930.

We discussed this a while ago when EX needed EXIF stripping, while I agree that it would be nice to have this functionality, the only viable crate for this seems...

Yeah, that might be doable. Though we likely need to remove the metadata without writing a file, i.e. do it on the fly while we're uploading/encrypting the data.

> In EXA, I see this: > > ``` > 2024-05-14T23:32:01.479257Z DEBUG matrix_sdk::http_client: Error while sending request: Api(Server(ClientApi(Error { status_code: 400, body: Standard { kind: Unknown, message: "One time key...

And another case where EX creates multiple `Client` objects in the same process: https://github.com/element-hq/element-x-ios/pull/2944