Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

E2E stability and usability. #63

Open
4 tasks
lampholder opened this issue Apr 12, 2017 · 1 comment
Open
4 tasks

E2E stability and usability. #63

lampholder opened this issue Apr 12, 2017 · 1 comment
Labels

Comments

@lampholder
Copy link
Member

lampholder commented Apr 12, 2017

Project: https://github.com/vector-im/riot-web/projects/5

Push to improve E2E stability and usability:

@abread
Copy link

abread commented May 31, 2017

I have a suggestion that I didn't see anywhere. We, techies, handle it fine, but regular users may feel intimidated by all the "Verify Device" prompts. I propose that, by default, the process of adding a new device simply means an existing one has to acknowledge its existence via a prompt (and the other ones are just automatically introduced to it no questions asked). Also, they wouldn't be bothered with verifying other people's devices manually.

For the more privacy conscious, stricter opt-in options would be available to:

  • Require the user to manually verify their own devices in every other device, manually preventing cross talk.
  • Require the user to manually verify other people's devices.
  • (maybe) Require everyone to follow your policy (admin-only of course).
    These options would be available both per room and as a "Please do this in every room by default".

Regular users will see significantly better usability for E2E encryption without worrying about it. Those that want more, can get more, where they want more.

(Also, sorry if this isn't the right place to discuss this. At the time of writing it seemed the most fitting.)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants