What can we do to protect ourselves from this?

#Nostr #nip04

#ProtectMetadata

Reply to this note

Please Login to reply.

Discussion

??

"Private" DM's on Nostr seem to be not so private. Not a techie, but apparently the contents remain encrypted, but the fact that you can know who spoke with whom and when is quite problematic.

Yep

C'est le graph de nos échanges privés (nip04)

Not sure what I'm looking at. Please explain?

This is the graph of our DM (nip04)

To defeat the NIP-04 metadata leakage, just have everyone DM everyone constantly with throw-away messages. That is, content that undecrypts to identifiable garbage.

Saturate the graph with noise.

Spammy solution. I think there were better solutions suggested as NIPs in nostr NIP repo.

Yes, this is spam by design. 😂

And yes, there are better solutions already proposed. Onion routing was one. Chain-of-ephemeral-pubkeys was another. I could imagine something based on NIP-26 delegation, etc.

How did you create the graph?

Some custom python script with networkX

just use a pseudonym dawg

Some people will use this to dunk on Nostr.

Nostr is a great idea. But we need to enhance privacy on DM.

I would love to see an implementation for a better DM specification.

nostr:nevent1qqsg0qcqxn99mmugj7jkktzer9cqysmz5h33q4uk0kmzk5t8zwhq28cpz9mhxue69uhkummnw3ezuamfdejj7q3qr34nhc6nqswancymk452f2frgn3ypvu77h4njr67n6ppyuls4ehsxpqqqqqqzsc9d8t

I agree, we need better solutions. I tend to think we should look beyond Nostr for private DMs. For example, there are other privacy preserving protocols. Just for example, take something like Signal. Couldn't a Nostr DM be used to perform a handshake between two clients so they can then switch over to Signal? Perhaps a client could use Nostr for public-facing messaging, then switch to another protocol for private comms.