It's too bad SimpleChat doesn't integrate with nostr. They could change their client to use nostr identities.

Reply to this note

Please Login to reply.

Discussion

Anyone reach out?

The point of Simplex is that there are no identities at all

That is the BS part of it. If you have a list of people in any app, you have identities. It might be a lightweight identity. It might rotate, and it might be different for every other user, but it is still an identity nevertheless.

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.

The work never ends. I’m tired. Does SimpleX need a server though?

Yeah they have relays which are a fancy message queues, you can even run your own. Servers are good. p2p is not reliable, especially for async comms

https://simplex.chat/docs/server.html

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.

Let's not make perfect the enemy of the good.