Just push a commit with the following message:
tweak UI UX, ready for nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac
It will be awesome to get your feedbacks one day 🙂
On GitHub https://github.com/jinglescode/nostr-password-manager/tree/v1.0.2
Or wait for 1.0.2 published
Ignore the logo though, a new one is coming.
I still don't know how do I feel about storing (encrypted) passwords on public relays...
🙄
I’ll go first.
Also, I would like to put out a few bounties, for hacking and finding vulnerabilities.
Maybe with these efforts, with time, it can gives confidence.
I often wonder what I should do if my private key is leaked. I will lose my identity. The more I use it, the more I lose. Anyone who has my private key can see the encrypted content I have sent to nostr relays. My DMs or whatever.
It's not like Bitcoin private keys. When my Bitcoin private key is leaked. I can quickly transfer the money to reduce the loss, or just lose some money.
Don’t use nostr dms for anything private.
Yes, you just lose your npub. Make another, problem solved.
I’m half joking.
It’s true. For social accounts, it’s great to have one account, for everything communication related, and works between the various clients. Yes, losing it, people can see your DMs.
For other use cases, there’s no harm using a new key. For example, you can use a different key for highlighter, to keep notes. Another key for listr, to keep list of items. Another key for password manager like this, to keep passwords.
And for this password manager, leaking your key still keeps your data safe, it’s using similar encryption to other password managers to encrypt your data the second time.
