Keychat’s current support for Nostr DMs works like this: if you log in to Keychat with your Nostr ID — more precisely, your Nostr microblog ID — and someone sends you a DM, whether it uses NIP-4 or NIP-17, you’ll receive the message (along with a notification) and can reply using the corresponding DM format. Of course, this requires that you and the other party share at least one common relay. You can add relays in the Keychat Chat Settings. One limitation for now is that when you log in with a Nostr ID, you can’t initiate a DM(NIP-4, NIP-17) yourself — you have to wait until someone sends you a DM first, and then you can reply. View quoted note →

Keychat Browser will continue to be optimized for audio and video Mini Apps, such as enabling playback in the background. View quoted note →

We use Nostr IDs and relays as the foundation for Keychat — not because we’re blind Nostr maxis who think it’s a hammer for every nail, but because our analysis shows it’s a pragmatic and well-reasoned choice. View quoted note →

You can think of Keychat’s design as snapping together open-source protocol blocks, like building with Lego. In our hands we already have a set of mature open-source “blocks”: A Nostr block for identity (ID) and chat relays; A Cashu protocol block for message stamps and small payments; A Lightning protocol block for the wallet; Signal and MLS protocol blocks for end-to-end encryption of chat messages, and for deriving a unique receiving address for each message; A Web App protocol block for hosting and running various Mini Apps. By combining these open-source blocks, we’ve created a work that is both structurally clear and robust—Keychat. View quoted note →