NIP-17 DMs fact sheet 
Login to reply
Replies (18)
missing fact: they don't work.
Find a better client, then. They work great on Amethyst
Random key is generated at group creation and shared with all members?
What is process of removing/adding group members? Simply new group creation?
Different random keys, one for each one.
Add members, you can just add new receivers in the inner message.
Its like an email. You add more receivers, they receive it.
sometimes we have to send automated nip-17 messages, using codes. for example in nostr-tools on npm, we tried a lot but when we try to decode it we get invalid mac for no reasons.
or sometimes a client event amey won't show some of them. i believe this one is because of invalid outbox model usage on some clients.
also, are they energy efficient? when i look at the spec we do a lot of cryptography.
Sry I’m still stuck on the random key. One for each what? One random key for each “dm”? One per group member? Unclear, trying to piece that bit together.
Each wrap has a new random key. In this picture, there are 3 new random keys.
Tell us more - which apps are involved?
Would like to document here: 
GitHub
Direct Messaging (DMs) · Issue #169 · nostrability/nostrability
Summary in quote form from a nostr DM User I gave up. Either it works, but is not encrypted - or it doesn't work for me, in which case I just give ...
The ones with invalid mac I get are very old. Probably from clients doing tests. But we should keep an eye on it.
Outbox model is irrelevant as NIP-17 has its own relay model. It doesn't use NIP-65 at all.
They are not supposed to be energy efficient. They are supposed to be private at the expense of more energy.
How should the client display messages chronologically?
yep, but by the date inside the chat message, not the public one
1. so, i think we had some issues with typescript crypto package. we just switched to nip04.
2. yes, i meant the dm preferred relay lists, i can see most clients don't care about it.
3. do we have any energy efficient alternatives?
Most clients are removing NIP-04 these days. It will start to not work anymore.
Amethyst's will remove in the next version.
thanks a lot, ill take a look and share my experience there.🫡
we will open an issue on nostr-tools and try to migrate to nip-17 again soon. 😵💫
Is it possible to encrypt DMs with own PGP key?
Possible? Yes. Does it do anything new? No.
Have you ever been thinking about implementing such an option into the app maybe? One could connect own key and automate the process.