hodlbod's avatar
hodlbod hodlbod@coracle.social 1 year ago
🚨 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.
GitHub
nips/17.md at master · nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

Replies (14)

The Fishcake (nostr.build)'s avatar
The Fishcake (nostr.build) _@thefishcake.com 1 year ago
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 🐶🐾🫡
Default avatar
npub18jvy...qqu3 1 year ago
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
Don't Believe The Vibe 🌱🍋🍊's avatar
Don't Believe The Vibe 🌱🍋🍊 _@nostrdvm.com 1 year ago
GM. 🤘
hodlbod's avatar hodlbod
🚨 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.
GitHub
nips/17.md at master · nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
View quoted note →
1 replies ↓
Default avatar
npub18jvy...qqu3 1 year ago
Lite?...that doesn't sound very assuring. That means something is leaking?
↑