Nostr Archives

@Keychat Jumble now uses a NIP-17 version of NIP-4E (https://github.com/nostr-protocol/nips/blob/per-device-ke…). Would you consider this approach, or would you stick with the traditional NIP-17? I believe this NIP-17 specification would make DMs much more secure.

💬 11 replies

Replies (11)

Keychat8d ago

Does Jumble have support for Nostr DMs? I’m not seeing any DM section.

0000 sats

Flowey8d ago

It's still in beta: beta.jumble.social Separating the Nostr identity from the cryptography seems more efficient to use bunkers or remote servers, and it enables secure message synchronization.

0000 sats

Danny, the cyber guy6d ago

I don't understand the benefits of this over marmot protocol. https://github.com/marmot-protocol/marmot

0000 sats

Flowey7d ago

So what is your opinion?

0000 sats

Keychat7d ago

We hope that users of NIP-17e who also want to send and receive DMs in Keychat can sign into Keychat with their encryption keypair rather than their ID keypair. This way, Keychat wouldn’t need any changes, and we could avoid compatibility issues with standard NIP-17.

0000 sats

Flowey7d ago

Although Keychat uses NIP-17, it already suffers from compatibility issues with other clients that use the same NIP due to the signal protocol. Synchronization is a major advantage for increasing the adoption of Nostr messengers; furthermore, the NIP-17E approach is much better than the current one, and i believe the same effort was made to replace the NIP-4 should be done. Cody is still developing the NIP-17E, i believe you two could help each other, you're my two favorite Nostr clients.

0000 sats

Flowey6d ago

If you say that, you have no idea at all.If you say that, you have absolutely no idea how Keychat works. Furthermore, the marmot protocol doesn't offer any solution to what NIP-17E purports to solve; did you read what I wrote?

0000 sats

Keychat7d ago

@Cody 🫡

0000 sats

Keychat7d ago

Perhaps we can summarize it this way: Old Nostr DM (NIP-4) integrates four capabilities into a single Nostr key—it serves as an ID, an encryption key, a receiving address, and a sending address. New Nostr DM (NIP-17) integrates three capabilities into a single Nostr key—it serves as an ID, an encryption key, and a receiving address. Newest Nostr DM (NIP-17e) integrates two capabilities into a single Nostr key—it serves as an ID and a receiving address. I’m not sure whether the receiving address of NIP-17e messages is the ID key or the encrypiton key.

0000 sats

Cody6d ago

Only the encryption and decryption use a separate key. The recipient is the same as in NIP-17. https://github.com/nostr-protocol/nips/blob/per-device-ke…

0000 sats