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

E2E Epic #222

lampholder opened this Issue Sep 27, 2018 · 4 comments


None yet
3 participants

lampholder commented Sep 27, 2018

There's a big list of E2E improvements we want to make in Riot across all platforms.

Our general approach (where possible) will be to tackle the E2E technical and UX challenges in web first, then when we're confident in our understanding translate this into mobile.

Some design tasks will require consideration of web and mobile UX simultaneously.


  1. E2E key backup 'back end' (aka all the stuff Hubert and Dave have been doing so far)
  2. Recovery Setup
  3. User Account Settings
  4. Registration and Login
  5. Room Settings


  1. Verifying Users
  2. Security Notifications
  3. Bi-directional user verification
  4. Cross-sign on login


  • Passphrase suggestions
  • Consider cycling back to registration and applying password strength validation to account creation

@lampholder lampholder changed the title from E2E Push to E2E Epic Sep 27, 2018


This comment has been minimized.


ara4n commented Sep 27, 2018

I'm a bit worried that (for a change) the big projects might be eclipsing smaller high-impact E2E fixes. Stuff we might also want to consider includes:

  • Hunting UISIs; there are still device-list sync issues over federation happening somehow (e.g. Tchap just got bitten by one)
  • Ensuring that key share prompts only happen at the right points (rather than repeatedly)

@manuroe manuroe referenced this issue Oct 8, 2018


Implement E2E key backup #2070

4 of 5 tasks complete

This comment has been minimized.


lampholder commented Oct 8, 2018

@ara4n this issue is just meant to represent the stream of large chunks of planned E2E work - specific issues that people are experiencing on specific platforms are best being raised, triaged and tackled as individual github bugs I think.

If you want a cross-platform UISI-squashing effort that might be something we make a github meta issue for, but that would still I think be best considered separately.

@lampholder lampholder referenced this issue Oct 8, 2018


E2E Key Backup #2642

0 of 4 tasks complete

This comment has been minimized.


lampholder commented Oct 19, 2018

I'm going to split @ara4n's smaller high-impact wins into a separate issue, then modify this one with the latest planning. The intention is for this issue to be your starting point to understand the current scope and progress of the e2e work more generally.

@lampholder lampholder referenced this issue Oct 19, 2018


Matthew's high-impact E2E fixes #226

0 of 2 tasks complete

@lampholder lampholder added the e2e label Oct 23, 2018

@uhoreg uhoreg referenced this issue Oct 29, 2018


Implement cross-signing proposal #4110

3 of 5 tasks complete

This comment has been minimized.

nadonomy commented Oct 30, 2018

Now tracking wireframes & feedback in this related doc, which follows the order of work of this epic:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment