Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unverified encrypted calls should not open warning dialogs #12935

Closed
notramo opened this issue Mar 30, 2020 · 1 comment
Closed

Unverified encrypted calls should not open warning dialogs #12935

notramo opened this issue Mar 30, 2020 · 1 comment
Labels

Comments

@notramo
Copy link

notramo commented Mar 30, 2020

Description

If Alice knows Bob's voice very vell, they could verify in-band. It shouldn't place any dialogs about unverified session, but should allow to place the call and show a warning when the call is active. This would the best approach to new users because it wouldn't pop up any dialogs. They don't want dialogs asking them what to do with verification when they don't even know what this encryption thing is. They are scared out by these dialogs. New users is mostly invited by someone who is more familiar with Matrix. If the call is established, they could ask the experienced user what that warning means.
It should default to emoji verification because if they are calling, that mostly means that they are away from each other, so they can't start QR code verification.

image
(Sorry for the green shield, I was too lazy to change it to red, but it should be.)

@notramo notramo changed the title Unverified encrypted calls should be allowed Unverified encrypted calls should not open warning dialogs Mar 30, 2020
@dbkr
Copy link
Member

dbkr commented Mar 31, 2020

I think this is talking about the pre-cross-signing UI so I think this is effectively fixed with cross-signing enabled, if I've understood correctly.

@dbkr dbkr closed this as completed Mar 31, 2020
@jryans jryans removed the Z-UI/UX label Mar 8, 2021
t3chguy pushed a commit that referenced this issue Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants