A specification or standard should solve a problem - not just provide implementation detail.
Usually, a problem and solution can be described in a paragraph or less. If you can't figure that out from reading a standard/spec, you're just reading someone else's implementation detail.
Excellent presentation by Nick Szabo from last year.
What jumped out at me what the concept of the promissory note that came to serve as the function of money in China, and spectacularly failed due to counterfeiting.
What an extended master nostr public key might look like in bech32 xpub1qjyty8sqqqqqqqqqqqqqpestkmv2wj7alfetfewqp03e677a4d9fk9uer224rajwxz28xekmqw2ys2wgjthl0xwq4cnjk3j5prywm7hnj55uslx7eh07zek75c9zykj7wd4
The two biggest technical pushbacks against nostr from the normie-world are:
1. Lack of key rotation
2. Quantum resistance
Until I get satisfactory answers to both, despite all the benefits of nostr, it’s impossible to get past vendor FUD.
As for non-technical (ideological) pushbacks, it’s just a case of building better solutions.
Any help would be appreciated.