Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 4
Generated: 12:15:15
The new version of Keychat we’re working on can receive Nostr DMs (NIP-4 and NIP-17) and reply to them. However, the end-to-end encryption scheme for Nostr DMs always uses the Nostr ID’s private key for encryption and lacks both forward secrecy and post-compromise security (PCS). If the private key is ever compromised, all past and future messages are at risk of being decrypted by others. Because of this, Keychat labels Nostr DMs as “weak encryption” and displays a danger warning in the top-right corner. image image
2025-11-19 20:43:28 from 1 relay(s) 2 replies ↓
Login to reply

Replies (4)

I wish it weren't necessary; other messaging clients need to improve their encryption. Could this be an optional feature, allowing us to choose whether or not to download it? So people like me who have no intention of less private conversations would not have to have heavier clients, even if the difference was minimal.
2025-11-19 21:39:26 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
Agreed. We’ll add an option in the Chat Settings to enable or disable Nostr DMs. Also, we strongly recommend using multiple IDs — ideally, create a dedicated ID just for chat. Your microblogging ID can then be used exclusively for public notes.
2025-11-20 00:32:34 from 1 relay(s) ↑ Parent Reply
nostr:nevent1qvzqqqqqqypzpwleyw4fy3sxt7yvgrran0mpenxqlululur94r9jlax0hd3q3rc7qqs0jhyvnakyceyj5drwdqnsdyy86pgl0jzkl2cjtl05ph5h3f99mvsfw4ank
2025-11-20 23:32:40 from 1 relay(s) ↑ Parent Reply