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

New device verification is verbose and spammy #5791

Closed
turt2live opened this issue Dec 6, 2017 · 2 comments
Closed

New device verification is verbose and spammy #5791

turt2live opened this issue Dec 6, 2017 · 2 comments
Labels
A-E2EE P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@turt2live
Copy link
Member

Description

After logging in to a new device I get a few prompts for verification:

  • On my mobile device
  • On my home computer
  • On my work computer
  • On my laptop
  • etc...

Even if I accept the new device on my android phone, I'm still plagued with prompts on every single device after that. It would be greatly appreciated if this was less in my face every time.

Version information

  • Platform: web (in-browser)
  • Browser: Chrome 62
  • OS: Windows 10
  • URL: riot.im/develop
@uhoreg
Copy link
Member

uhoreg commented Dec 7, 2017

somewhat related to #5533

@lampholder lampholder added T-Defect S-Major Severely degrades major functionality or product features, with no satisfactory workaround P2 A-E2EE ui/ux labels Dec 8, 2017
@jryans jryans removed the Z-UI/UX label Mar 9, 2021
@turt2live
Copy link
Member Author

in practice, the cross-signing approach doesn't cause so many aggravating noises and alarm bells, so can be easily ignored on other (unused) devices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

4 participants