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
{{ message }}
Repository navigation
Can't verify messages whose keys were forwarded #8470
I can't quite fully reason through whether we'll need to fix this as part of our E2E UX push, or whether it will almost always not be a problem if all the other components (existing and pending) are doing their job properly. One to revisit later.
I think it depends whether we're relying on key sharing. If we're expecting key sharing to never normally be necessary then fixing this is not so important.
Activity
lampholder commentedon Feb 19, 2019
I can't quite fully reason through whether we'll need to fix this as part of our E2E UX push, or whether it will almost always not be a problem if all the other components (existing and pending) are doing their job properly. One to revisit later.
dbkr commentedon Feb 27, 2019
I think it depends whether we're relying on key sharing. If we're expecting key sharing to never normally be necessary then fixing this is not so important.
ShadowJonathan commentedon Dec 16, 2021
Messages that were forwarded from different devices currently show as (properly) verified on other devices, is this still applicable?
kittykat commentedon Dec 16, 2021
@dbkr I'm going to close this for now as it seems resolved, could you please re-open if it's still valid?
Merge tag 'v1.11.0' into sc