Yes, nostr developments are really fast to catch up 😅
Also, Good luck with your Geyser fund proposal, hopefully you can get some support there
Nice.
Yes, some relays implementation have supported NIP-42 authentication which protecting event from unauthorized read (only whitelisted pubkey can read). We can check their support based on NIP-11 information. I think nostr-tools library already suppport NIP-42, so for certain relays you can probably utilize it to make it more secure.
Introducing...
Vault - NOSTR Password Manager
A free, open source, and decentralized password manager.
Download extension:
https://chrome.google.com/webstore/detail/vault-password-manager-on/namadahddjnkmjgdnncdlhioopmjiflm
Source code:
https://github.com/jinglescode/nostr-password-manager
-- == --
More info:
Vault utilizes zero-knowledge encryption to safeguard your data while storing it on NOSTR network for enhanced resilience.
Vault saves all your passwords and notes securely by encrypting your data twice; once with your secret key and once with your passcode.
Your data are not stored on any centralized server, but rather on a set of relay servers. This means that it is resilient to attacks and that you are the only one who can access your passwords.
Security experts recommend that you use a different, randomly generated password for every account that you create, and Vault makes this easy. Vault can generate passwords and store them for you, this means that you only need to remember one password, your passcode.
Looking to store and swiftly retrieve your data? Vaults facilitate searchable items, allowing you to effortlessly copy the desired information with a single click.
Vault is free, open source, and decentralized; and will always be.
-- == --
Status and questions:
- Version 1.0.0 approved on Chrome Web Store. Version 1.0.1 is the real version I wanna push to you guys, might have to wait for 24 hours for approval
- Enhanced Safe Browsing? - Apparently for new developers, it generally takes a few months to become trusted.
- Read history? - not really, just that need to read what page you are currently on and paste the URL when you add new items
-- == --
nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx
nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m
nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424
Great works nostr:npub1alpha9l6f7kk08jxfdaxrpqqnd7vwcz6e6cvtattgexjhxr2vrcqk86dsn doing "other stuff" in Nostr :)
Maybe this is just a bit of idea, you can probably offer dedicated relay as server (like BitWarden) and also with custom relay setting for user who want to self host on their own private relay. Additionally, you can also use NIP-42 auth if the relay support it to make sure only specific user can access safely. :)
Thank you for all the hard work. Hopefully, You nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z and other Nostr devs can solve this Nostr DM issue completely. 🙏
Iris now supports secret chats that don't leak metadata, implementing the https://hrfbounties.org/ bounty #3. It works also for group messaging.
It's a quick & dirty solution, but works. A shared nostr account is created for the secret chat / group. Its nsec can be shared via link, qr code or invite message from a single-use anonymous account.
Users can then communicate using the shared account's messages-to-self. Iris signs the inner messages with your own key, but the arrangement could be used for anonymous group messaging as well.
I'll also add inner message encryption at some point, so you can ensure that only certain group participants can read the message.
This arrangement doesn't introduce any new event kinds and works also in clients that haven't implemented a special UX for it. You can just log in with the nsec and message yourself.
I had to disable the Iris social graph filter to let invites through, so now Iris DMs are open to spam again, but I'll try to figure out a better solution.
As always, the UX needs a lot of attention, but I believe here's an MVP.
Screenshots:
Alice wants to message Bob:
Alice sends a secret chat invite to Bob:
Bob automatically follows the invite from Alice. They can now message each other in the secret chat:
Here's how the invite looks in another client. I will add an "nostr:ninvite" URI in addition to the nsec.
Is there any written spec for this? Is it similar to https://github.com/nostr-protocol/nips/pull/686 ? Cc nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
I think it is like this. This is in Nostrmo, client side keywords filtering. Blocks tab is pubkey block, while Dirtywords based on keyword block list.
