uhoreg
commented
4 years ago We can probably use the message timestamp as a hint to show a more useful message to the user. Maybe something a long the lines of "This message seems to have been sent before you logged into this device. We're trying to fetch the keys from your other devices if any of them were logged in when the message was sent." Except we'd probably want the message to be shorter and/or collapse multiple UTD messages.
We could also offer to restore the keys from backup too. (In fact, why don't we do this for all undecryptable messages?) We can either check if the server has a backup for the key and then say "You can restore the key from backup", or we can ask the user if they want to "Try to restore from backup". The former would probably be more user-friendly, but would require querying the server (and would probably need to do some caching).
This probably requires design from @nadonomy, but it seems like it's non-trivial, so we may want to punt it for a bit unless he thinks it's worth doing right away.
aaronraimist
richvdh
The main blocker on this is trying to decide which messages predate your participation. Clearly a simple timestamp isn't good enough as there is a finite delay between your device coming on line and everyone else in the room hearing about it.
It also interacts with the key-sharing: you may be able to get the keys to the messages by some other means, so don't necessarily want them to be hidden - although a way to distinguish between "this was sent before you joined the room" from "something random went wrong" would certainly be useful.