You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you login a new session, all the history messages retrieved via initial sync will be in Error with **unable to decrypt** errors for all messages in timeline.
If the user did verify his session and have a keybackup, a backup import should be happening in background. But during this process the messages would still be displayed with hugly errors. Even key gossiping with the other session could take time.
Actual rendering:
Proposal
We should hide undecryptable history if we know that there is no chance for the current device to get the key without a user action (verify, manual import..)
We should hide history while a key backup is in progress, and give feedback on the import process
The user should have an option to show history anyway
If the session is verified and the user already did a key import, or if he decided to show message anyway, or if this room is setup to share room key history, we should then show them, but the error level should lowered and a dismissable banner should be shown with details and CTA
We should also give feedbacks to the user about the key gossiping process, currently for the user it's like a shot in the dark (re-request encryption keys)
Some feedback; i personally love this variant the most, as it does not hide which messages can be decrypted, which i personally think is a downside of other designs.
Problem description
Currently if you login a new session, all the history messages retrieved via initial sync will be in Error with **unable to decrypt** errors for all messages in timeline.
If the user did verify his session and have a keybackup, a backup import should be happening in background. But during this process the messages would still be displayed with hugly errors. Even key gossiping with the other session could take time.
Actual rendering:
Proposal
We should hide undecryptable history if we know that there is no chance for the current device to get the key without a user action (verify, manual import..)
We should hide history while a key backup is in progress, and give feedback on the import process
The user should have an option to show history anyway
If the session is verified and the user already did a key import, or if he decided to show message anyway, or if this room is setup to share room key history, we should then show them, but the error level should lowered and a dismissable banner should be shown with details and CTA
We should also give feedbacks to the user about the key gossiping process, currently for the user it's like a shot in the dark (
re-request encryption keys
)Dev Tasks
The text was updated successfully, but these errors were encountered: