element-hq / element-meta

Shared/meta documentation and project artefacts for Element clients
65 stars 11 forks source link

Epic: Failing to import keys from key backups cause UTDs #2350

Closed kegsay closed 1 month ago

kegsay commented 3 months ago

As part of our work on UTDs it has become apparent that one source of UTDs is around historical messages before the client logged in. In this scenario, the sender will not encrypt for the target device, which is to be expected. If key backup is enabled and the user has >1 client, the newly logged in client should still be able to read the message because another client has decrypted and uploaded the key.

There is evidence this is not working as intended:

All these cases will cause UTDs which are visible to the end-user. The above rageshakes were from Matthew and Patrick A as well as community members.

Separately to this, there is a class of expected UTDs which can occur which we currently do not have good support for. Consider:

We need to figure out a solution for this failure mode, whether it is hiding the events as "expected UTDs" or otherwise.

Definition of done:

richvdh commented 3 months ago

Separately to this, there is a class of expected UTDs which can occur which we currently do not have good support for....

This is https://github.com/element-hq/element-meta/issues/2327, I believe

BillCarsonFr commented 3 months ago

@kegsay found another source https://github.com/matrix-org/matrix-rust-sdk/issues/3247 might be similar to https://github.com/matrix-org/matrix-rust-sdk/issues/3197 but can't confirm yet

richvdh commented 1 month ago

Causes of this are fixed.