-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Delight: Highlight the importance of the security passphrase #22073
Comments
I'm not so sure this would impact D1 that much. |
Thinking out loud; If D1 is "returned users in a 24h period" and users are using the Web product they may need to sign in again when they return tomorrow... In my head it looks like this: User creates account, user validates email, user signs in, user starts DM and sends message, user closes browser tab, user opens element tomorrow, user needs to sign-in, user can't sign in because no security passphrase... I guess we could find out how common it is to signin vs already be signed in when you return to app.element.io? |
If you don't explicitly log out, closing the tab will not require you to sign-in again. Matrix sessions never expire unless manually done so by you on one of your other devices or your server admin. The exception to this is if you are running a browser like Tor which is amnesiac and forgets everything when you close it. |
Good to know - I have adjusted the Occasion and Priority rating of this issue accordingly |
Moving to "Next" as it's not prioritised just yet but we marked it as important |
We should also make the language consistent |
Also see this issue that was onboarding feedback... Feel free to close this if it's a duplicate of things you're already tracking. |
During a user's first session we don't explain the security passphrase to users. If a user does not set it up correctly, or loses this it makes it much harder to log in (impacting D1 and user success!)
At some point during the first session we should take time to educate users and ensure that they're set up for success when they choose to return to Element.
The text was updated successfully, but these errors were encountered: