We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When migrating from KeySAVe the Electron app to the web application, keys and formatting options should be transferred.
There are multiple ways of going about this
Please comment on which option you would prefer and why. If you can think of other technically feasible solutions feel free to mention them as well.
The text was updated successfully, but these errors were encountered:
I'd go for option 2 as it's most friendly. How the keys will be stored by the way? External database?
Sorry, something went wrong.
The keys will be stored inside the browser. It provides a database for such use cases.
Hmm so it's also worth to emphasize that you still need to keep your keys on disk in case you ever wanted to use another browser/machine.
There will presumably be import/export buttons so that shouldn’t be a concern.
I like option 2 as well.
No branches or pull requests
When migrating from KeySAVe the Electron app to the web application, keys and formatting options should be transferred.
There are multiple ways of going about this
Please comment on which option you would prefer and why. If you can think of other technically feasible solutions feel free to mention them as well.
The text was updated successfully, but these errors were encountered: