thinking about adding giftwrap support to nostrdb. then the local relay could query sealed notes like regular ones, maybe with an explicit filter flag to ensure to not mix them up. All it would need to do is periodically sync new giftwraps with negentropy or time-based sync.

This + nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc ‘s ratcheting we may finally have signal-grade comms in damus with no metadata leaks.

Reply to this note

Please Login to reply.

Discussion

Do eeeet. We need universally supported DMs without metadata leak. Once you do it, others will follow. No pressure. 🤣🫂🫂🫂

Yeah. I didn’t go into any detail on how clients will store messages they receive. The other part that isn’t in the nip but is possible is how to do syncing across different devices.

Basically each device/user combo represents an inbox that is tracking its own copy of the conversation (each device/user combo uses completely different keys)

I guess we need some mechanism for adding devices and sending messages to each device/key. Curious how signal does this.

Glad you guys are already talking about this. I hope there’s a solution that can make its way into the NIP itself. Using Negentropy on the client side to sync the missing DMs is intriguing. nostr:note1ul48nsqgw5lmsqmec8tajx8tx6mh78jmtgfqv86v74h4el8us84s8hwajd

That's how I did it on Amethyst. Inner events are just regular notes with empty signatures. You can query them with regular filters. Becuase they are empty, even if there is a bug in the code and they end up being broadcasted, relays won't accept them.

Though if you have support for multiple accounts, you might want to make sure the decrypted conversations of one account are not mixed with another account.

Yes good point. I don’t currently decrypt anything in nostrdb but if I did I should definitely track which key decrypted what.