NIP-17 DMs fact sheet 
Discussion
missing fact: they don't work.
Find a better client, then. They work great on Amethyst
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.
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.
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?
Tell us more - which apps are involved?
Would like to document here: https://github.com/nostrability/nostrability/issues/169
thanks a lot, ill take a look and share my experience there.🫡
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.
How should the client display messages chronologically?
yep, but by the date inside the chat message, not the public one
nip17 is nice, especially the relay stuff. people pretend they dont DM, but guess what the #1 thing i hear people complain about why they cant leave a diff platform, is their DMs. they want to slide into DMs.
for christmas i hope primal or damus (the iOS dominators) can find it in their schedules to implement nip17.