🚨 NIP ALERT 🚨

After nearly a year of work, NIP 17 has been merged! This replaces NIP 04 direct messages with something incrementally better — it fixes much of the metadata leakage associated with NIP 04 messages. There is still work to be done to create better standards, but this is a huge leap forward.

https://github.com/nostr-protocol/nips/blob/master/17.md

Reply to this note

Please Login to reply.

Discussion

Awesome!

nice!

I may be wrong, but it still doesn’t solve the biggest problem with nostr DMs, i.e., leakage and conductive usage of nsec to read all the DMs sent to them. Again, I may have missed something in the NIP, but if not, it is the biggest problem and more dangerous than metadata leak 🐶🐾🫡

Like Nip-44, but better. paired with NIP-59.. does this mean EE2E? am I reading this right?

E2ee lite basically; no ratchets.

Lite?...that doesn't sound very assuring. That means something is leaking?

Let's tighten the screws w ratchet to make it better!

Also How I know if my client supports NIP-17?

Sorry if that seems like a noob question. There isn't exactly a NIP support list to client sheet

🫡

Fantastic step forward!

Another big one coming soon™. 🔧🔧

great 🤙

well done, was there a reason to have a new nip instead of improve nip 04?

Yes, NIP 04 is terrible, it leaks sender/receiver, tags, message size, etc., plus the crypto is not audited.