On Keychat, you can create multiple IDs in a very intuitive and convenient way — it’s an underrated feature. View quoted note →

Testing Mutable in Keychat Browser. View quoted note →

@Minibits Hi, when a user pays a Lightning invoice using a Minibits mint and encounters a “proof pending” error, how long will this pending state last?

We are currently fixing issues in the Keychat wallet that may appear when paying Lightning invoices, such as “proof pending” errors and output-related problems. We’ve also received many feature suggestions. After reviewing them, we realized there are two main reasons why users keep requesting similar features: 1. Originally, Keychat was designed as an independent chat app, but many users want it to be more connected with Nostr microblogging—for example, better support for Nostr DMs. 2. Keychat was initially meant for communication among friends, where extensive group-management tools aren’t necessary because trust prevents spam. But as more users imagine Keychat being used for larger community groups, they request more admin tools—like multiple moderators and better group controls. We’ll think carefully about how Keychat can support some of these features—not blindly add everything, but implement what truly makes sense. We will likely revisit these requests after we finish our current priorities: Unified push notifications for Android Keychat, and Voice and video calls (WebRTC-based).

For example, Telegram groups can introduce AI bots to answer questions, which might be a useful feature for Telegram. If an AI bot is introduced into a Keychat group, it would have to know the group’s encryption keys just like any ordinary member. The AI bot would be able to see all the messages. This seems to undermine the purpose of building high-quality end-to-end encrypted group chats, doesn’t it? We should think more about this feature. Additionally, Telegram groups do not offer end-to-end encryption. View quoted note →

Keychat's one-to-one chats and small groups are encrypted using the Signal protocol. Moreover, a small group is a pairwise group; when a member sends a group message, it essentially sends a one-to-one message to the other members. Therefore, the encryption security of small groups is almost equivalent to that of one-to-one chats, but the number of members it can support is limited. Consequently, our large groups are encrypted with MLS. The Signal protocol is more suitable for one-to-one chats than MLS because its post-compromise security (PCS) ratcheting occurs more frequently. Additionally, all Keychat messages (whether one-to-one, small group, or large group) can be intuitively understood using the metaphor of a "letter.” 👇 Keychat uses Signal/MLS protocol to ensure message encryption security and meta-data privacy. The content of the letter can be exposed easily by opening the envelope. Keychat messages are end-to-end encrypted via Signal/MLS protocol, with a unique encryption key generated for each message. Only the sender and receiver can decrypt the message. The addresses of both parties on the envelope can be tracked. In theory, this problem is solved if they change addresses daily. So Keychat reuses Signal/MLS protocol to update sending and receiving addresses for nearly every message. View quoted note →

Testing divine video in Keychat Browser. View quoted note →

If you're also interested in Ark, you can follow this account. 👇 View quoted note →

The Design Psychology of Keychat View quoted note →