Now compare this to the original nostr description of nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhkcmmrdd3x77pwve5kzar2v9nzucm0d5hszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tc4rdlnm from November 9, 2020:

https://github.com/nostr-protocol/nostr/commit/bdeb03aeaf2d44db954e0eb1356a3f585ee7c50d

nostr:nevent1qqsqp3seup9kqz8xawavqd2jff6v627s63l4xwut9hjcphdnr5r3h5gpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsq3ppke5pel7ysw3rgl5e8lt8ky7zwavm5jrs2zx9tnu2vn5nydnqrqsqqqqqpax6l5c

Reply to this note

Please Login to reply.

Discussion

“therefore it has weird and unnecessary quirks like signing a JSON string which must strictly follow the rules of ECMA-262 6th Edition”

It's hilarious how many things the original nostr readme was clearly wrong about. Round-tripping is such an obvious problem to anyone who has ever worked on crypto codebases, and it has caused lots of problems for nostr implementations.

nostr:nevent1qqs85rwpnwlpdp02z466x25cdy2xuags24lcfrxlnqctujay6juem6qpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg9ha45tqck7dd9p9egl6559c8s7pmgw2y5vm2f6kyd5z594tmfjlspsgqqqqqqsuppqax

Interesting, I did a quick read on it and will read it again later. Perhaps there are some good ideas I can adopt in Nostria.