Paul Miller

migrating from sha3 to `@noble/hashes` would make it easier. it's also smaller and audited

@dawsbot what do you mean by "not as flexible"?

Any effort to improve DMs is good. I didn't do the ratcheting/hierarchy of keys in NIP-44, because it's too complicated and has many non-obvious caveats. I have been discussing this...

@mleku just take a look at RFC 9420 and try to comprehend it. It's complicated beyond any reasonable means. Which means it won't be implemented simply by volunteers. Which means...

Initial thoughts: 1. This is, as mentioned in doc, scheme unique to device pairs. User won't be able to read his messages on PC when a conversation was made from...

Signal doesn't allow multiple devices. Their web version proxies stuff from phone, which acts as a main device. It doesn't seem like syncing could be solved in a simple way....

@erskingardner what is the threat model you’re trying to work in, with this improvement? Is it different than the previous one?

Thanks, that’s thoughtful. What do you think about incorporating ML-KEM aka Kyber to gain additional pq security? I wanted to do it as v3 of nip44 at some point. Signal...

This is still an issue. The merged implementation is limited to 100 blocks, which makes it useless, compared to Erigon.

PoC: ```js const braces = require('braces'); const maxRepeats = 1; for (let repeats = 1; repeats