hodlbod

Was thinking about this last night, there are two things that can be done to reduce the number of events that have to be fetched to get up to date:...

Right, exactly. And because of the nature of nostr you don't know. But as long as you don't publish a new `set` you won't break anything. You'll be working off...

If you want to reconcile conflicting list updates you have to expand them into operations and rebuild anyhow. And in either case you've got to handle missing events. The two...

Sorry, I think I led you astray. `a` doesn't have anything to do with what we're talking about, it's just the group's address. So there's no linking of events at...

> Nice! But very long haha Yes, @vitorpamplona could we remove one of the two examples? DMs seem like a special case of group messages.

I built a test implementation [here](https://inbox.coracle.social), source code is [here](https://github.com/coracle-social/inbox) — I had to make some tweaks to the example code to get it working (a decrypt example would also...

@vitorpamplona checked your test cases, they decrypt on my end. Here's one from me: Recipient private key: `7dd22cafc512c0bc363a259f6dcda515b13ae3351066d7976fd0bb79cbd0d700` ``` { "content": "{\"ciphertext\":\"PGCodiacmCB/sClw0C6DQRpP/XIfNAKCVZdKLQpOqytgbFryhs9Z+cPldq2FajXzxs3jQsF7/EVQyWpuV8pXetvFT9tvzjg4Xcm7ZcooLUnAeAo2xZNcJontN4cGubuDqKuXy5n59yXP1fIxfnJxRTRRdCZ2edhsKeNR5NSByUi+StjV10rnfHt8AhZCpiXiZ/giTOsC4wdaeONPgMzMeljaJWLvl6n11VjmXhkx1mXIQt43CNB1hIqO3p89Mbd9p+nlLrOsR+Xs0TB4DCh4XTPbvgf7B7Z+PgOfl3GZfJy9x6TciLcF4E3Ba1zrPe4f79czCIEiJ1yrIKrzzYvv+it35DZQ8fgveFXpyHnNL29hml8PNjyOsFbCHVYLMGw88evI5PijOcpe1TtdoioX8kX5kVEQSKJXuoSjTorvbRPCgGzaa1m0J0uTpzri5VD22a/Jh2CcAnubg6w4JDdUWCogdSV3NqiJllo7ZF7WnZ3apPdRD23MEfphVBJrcLBUNlmwajnY5IvVTKTkZOP50r9dBapvMWXIo6M6zhy/5vVWJz57863pelYCRG4upaXZuNK9sMBtbiphxmFR83i8RML8KN8Q391Cd/xBN7TxJNo5p2YU25VeGZUAmHY8DYlMQDm8Br0nStAXp3T+DzTRL8FTECa8DJV+KTAPoCxqhv3B28Ehr0XAP75CsHoLU00G48cR7h3vQ0CnfKh6KXU6nnDA5OWfpMYpirACCpsnpSD0OaCQ3gkQp3zZNMS3HcOpnPK/IY7R0esbzgAkvNhkyxaIfPDdf+eRUSOA9+2Ji28MwjjY8Dw3SLdUqCOzIDjQeR/T5oNmaQJm3lZ8G0FxxC6ejD4VJX/NI/x+STeB9jWHWmHZvqKzV6JHNh6qmZb6TKSIPOHpafWFoeJFOmiiigf46sju9vRXmVEAx59HXWnvnvCBNJg877yCMulB6xyQuSdVDuotQU4tQZwCKedTHJ6GqjesM98UlJrDtdWQURwwW1qc7N8tS6PukmUVEf0jmbIWVIBmUlkcVuiSs1g1h1kjt8c4MnGTz3CSgpOd1MqxLrl9WwrTqM+YnE+yeZYUjFoewyKZIQ==\",\"nonce\":\"OdCZczJiUGR4bOGIElQ4UUH4dQmG5U/3\",\"v\":1}", "kind": 1059, "created_at": 1690772945, "pubkey": "e01475e87896800b7285eb0daf263c59f811c8fc5bc8daa105d2c98b6d7c4952", "tags": [...

@vitorpamplona I was working through this topic this morning [here](https://gist.github.com/staab/f8284af12450dbbdcead6e0c3ed95e2c), I think it would be worth separating encryption/wrapping/key exchange from use cases, since small and large groups will probably work...

> This PR tried to do the opposite That's fair, I was mostly just asking about splitting the concepts out described [here](https://gist.github.com/staab/f8284af12450dbbdcead6e0c3ed95e2c) into different NIPs, but keeping them in a...

> Do you have a more specific proposal? Yeah, and it's pretty similar to what you're suggesting. The benefit would be to reduce the number of identifiable recipients by one...