dtonon on Nostr: Okay, now that JeffG has pulled this very interesting NIP-104 out of thin air, we ...
Okay, now that
JeffG (npub1zuu…c2uc) has pulled this very interesting NIP-104 out of thin air, we need to converge on a single "standard" implementation and ask all clients to implement it as soon as possible. I think this is strategic, because DMs (and small group chats) are a glue factor for keeping friends and family on Nostr after we invite them, so for promoting real life conversations. It would be a shame if new users started trying new apps and found they couldn't see the history or, even worse, couldn't communicate with their contacts. They would go back to the usual messengers of the big-corp and we would lose an important battle, making it difficult to rebuild trust for a new attempt.
So, what's the next step?
E2EE DMs are coming to Nostr 🔒
After being nerd sniped by hearing NVK (npub1az9…m8y8) mention OTR for the millionth time on the Bitcoin Review podcast, I spent the last few weeks digging into OTR, the Signal protocol, and a grab-bag of other cryptography.
The end result is that I (am pretty sure at least) that I found a way to do E2EE (end-to-end encrypted) DMs on Nostr in a way that is both forward and post-compromise secure AND doesn't require any centralized servers.
Demo video: https://share.cleanshot.com/nMKk6cn0
Live demo app: https://drdm-demo.vercel.app
And finally, the NIP (for those of you with bikes in need of a shed): https://github.com/nostr-protocol/nips/pull/1206
Huge thanks to Max (npub1klk…x3vt) and PABLOF7z (npub1l2v…ajft) for the chats while I worked out the details.
Published at
2024-04-30 11:17:37Event JSON
{
"id": "00000031b91482cc3ba20382df3d53760ef6235affb8a2a7518455de8b0f531e",
"pubkey": "7bdef7be22dd8e59f4600e044aa53a1cf975a9dc7d27df5833bc77db784a5805",
"created_at": 1714475857,
"kind": 1,
"tags": [
[
"p",
"1739d937dc8c0c7370aa27585938c119e25c41f6c441a5d34c6d38503e3136ef"
],
[
"q",
"ef9241a1b4aabfc8a044b25c971a950b58d48b122f08da3935be019b6d0201d4",
"wss://nos.lol/"
],
[
"nonce",
"16602069666340016193",
"25"
]
],
"content": "Okay, now that nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc has pulled this very interesting NIP-104 out of thin air, we need to converge on a single \"standard\" implementation and ask all clients to implement it as soon as possible. I think this is strategic, because DMs (and small group chats) are a glue factor for keeping friends and family on Nostr after we invite them, so for promoting real life conversations. It would be a shame if new users started trying new apps and found they couldn't see the history or, even worse, couldn't communicate with their contacts. They would go back to the usual messengers of the big-corp and we would lose an important battle, making it difficult to rebuild trust for a new attempt.\nSo, what's the next step?\n\nnostr:nevent1qqswlyjp5x62407g5pztyhyhr22skkx53vfz7zx68y6muqvmd5pqr4qpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tce322ee",
"sig": "02d223c09e2c4b402527e42224a2a59ec167e15a2e5ede3ca142d14e345d696b9c86cf371f9cb397603fe7dc082221ed23f84e4c199a2037c68e965c008e85eb"
}
