lucash-dev

Oh, I see there's a reference to unambiguous in the README I missed before. Sorry about that. Still, maybe it's worth adding a doc clarifying that the ambiguous grammar will...

> Nostr doesn't want to replace all the other means of communication that have existed since the birth of humanity, these other means can still be used to communicate information....

> Regarding client isolation censorship, I believe the situation is analogous to receiving/broadcasting bitcoin blocks/transactions respectively? We can assume an individual authors publications will make it through some channel without...

Alternatively, the "nonce" tag could have an optional fourth element corresponding to the challenge. Not sure if there's anything against variadic tags though. BTW What's the process for updating a...

> I think once you've done that, you can just focus on the second part -- I have a pubkey A, you have a pubkey B, we both know those...

> @ajtowns I was thinking something similar in regards to two events kinds, a request and then messages. > > @lucash-dev I had a similar thought, looking for messages at...

Simplest incrementally better thing would be to just take pretty much exactly NIP-4, but derive properly three keys from the DH (using prefixed hashes): - encryption key - "fake" author...

> The "location" could be random after the initial DH exchange (e.g Event Kind A). Yes, but that’s harder to specify and implement. I was just trying to spell out...

I don't see how using HashCash directly might prevent a second solution that uses micropayments. Having the ability to provide an anti-spam functionality that isn't tied to also running a...

> Nostr is pretty much re-using bitcoin's PoW, it's a SHA-256 ID that depends on message content, and the content is modified by clients in order to get a certain...