Nostr Web Client

The idea I like of creating different “addresses” for incoming messages, and then dumping that if it gets too spammy. Not having a long-term pubkey as your address has that benefit.

You could probably do something similar on nostr, but you still get metadata leakage.

I came to the conclusion that nostr is way too public in too many ways to be a serious private message protocol.

Vitor Pamplona 2y ago

I agree. It was one of my early beefs with Nostr in general: having one key for everything is pretty bad.

We could do the QR code thing they do. When meeting a friend you can generate a new QR code for a super private chat. Metadata still leaks but it's not associated with your main Nostr identity.

We could even use NIP-06 key derivation (say one key per friend) to reduce metadata leakage if that is the only concern. In that proposal, only the seed can rebuild a friend's list. Apps could rotate keys by just asking the Nostr Id for a new one.

Reply to this note

Discussion