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

Inform users that "forgetting a browser" means that the linked mnemonic will not work #904

Closed
Tbaut opened this issue Apr 9, 2021 · 0 comments · Fixed by #928
Closed
Assignees
Labels
Priority: P1 High Added to issues relating to a high severity bugs.

Comments

@Tbaut
Copy link
Collaborator

Tbaut commented Apr 9, 2021

Because we call everything interchangeably a "backup phrase/mnemonic/recovery key", and because they look the same (a suit of words), our users may expect them to perform the same and let them access their directory.

Now a browser backup recovery key is actually different, it is half of a mnemonic. The other half sits in the store on the Tkey network. If both are accessible (meaning the saved browser has not been deleted from Tkey store, and the user has the recovery key, then they can get access to their file using it).

This is all too complex to explain, but we should make a better job at informing our users of the risks at least. I'm suggesting to show a popup to confirm the deletion of a browser we could tell:
"You are about to delete a saved browser, any browser recovery mnemonic that was downloaded will not work any more, do you want to continue?".

I think this would be small enough for users to care reading. And if they don't.. then at least we tried.

Originally posted by @Tbaut in #865 (comment)

@Tbaut Tbaut added package: Files-UI Priority: P1 High Added to issues relating to a high severity bugs. labels Apr 9, 2021
@Tbaut Tbaut assigned Tbaut and unassigned Tbaut Apr 13, 2021
@tanmoyAtb tanmoyAtb self-assigned this Apr 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P1 High Added to issues relating to a high severity bugs.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants