3 ms·
Played with it a bit just now. Less and more, very nice. When returning to the page, it will allow you in with the wrong password and without any complaints. T
by huhtenberg 7y ago
Played with it a bit just now. Less and more, very nice.
When returning to the page, it will allow you in with the wrong password and without any complaints. This is confusing.
Also, I think it's a bit counter-intuitive that the local copy is encrypted, but the online (published) copy is public. I would expect there's more need to access-restrict an online copy (i.e. to require a password to read it) rather than safeguarding the local one.
More specifically, I was expecting the password to be used for backing up local notes to the server and for restoring them later (say, on another machine). Which would be in addition to being able to publish notes for everyone's view.
But, again, nicely done in terms of keeping it strictly focused on a single simple purpose.
- qrv3w 7y agoThanks. I'll think about the password. Right now more than one person could claim a username but they will only decrypt what they can with their password. Because of that it's hard to check password validity.
- huhtenberg 7y agoJust take a random string, encrypt it with the password and save both plaintext and encrypted version in localStorage, stuff a username in one or another if needed. This will allow you to check if the username/password combo is valid.