<oembed><type>rich</type><version>1.0</version><title>Luxas wrote</title><author_name>Luxas (npub16j…733sv)</author_name><author_url>https://yabu.me/npub16jdfqgazrkapk0yrqm9rdxlnys7ck39c7zmdzxtxqlmmpxg04r0sd733sv</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Nymchat&#39;s group chat feature was the first fully functioning NIP-17 group chat that didn&#39;t expose metadata related to group membership. &#xA;&#xA;It was then upgraded to support roles and moderation within the group chats, also a first.&#xA;&#xA;It has now been upgraded further, patching a few bugs and allowing the ephemeral keys to be encrypted at rest when using the &#34;encrypted identity&#34; feature (setting a password or passkey or face/touch ID lock on the app). And the group chat owner can now decide to allow backfilling of chat messages for new members who join.&#xA;&#xA;If you&#39;re unfamiliar, Nymchat&#39;s group chat feature uses a different ephemeral key for every sent message, with the next planned key advertised inside the encrypted rumor. To an outside observer, there is no possible way to correlate group membership.&#xA;&#xA;There is no shared key for the group that could be compromised and leak all previous chat history. There is no re-keying of the entire group if a user gets kicked or leaves. Nymchat&#39;s group chat is a very streamlined and privacy-focused group chat implementation, which should probably be spun off into its own &#34;protocol&#34; or NIP or just how NIP-17 should be for groups tbh. &#xA;&#xA;https://nymchat.app</html></oembed>