Replying to Avatar ChipTuner

I don't want nips to tell me how to design my data structures and API. Too many of you OOP devs leaking code abstractions into the protocol specs IMO. nip44 was a lot of work to abstract away from the API into an architectural blueprint. I enjoy reading scientific white papers and RFCs way more because it doesn't tell me how to write code. Even NIP01 couldn't explain the spec without code.

I'm just grumpy when reading

https://github.com/nostr-protocol/nips/pull/1494

Avatar
MichaelJ 1y ago

I figure explaining the spec in terms of JSON is fine, since JSON is the structural framework of the protocol messages. But yeah mixing implementation details leads to confusion.

Less code examples, more Gherkin acceptance criteria.

Reply to this note

Please Login to reply.

Discussion

Avatar
ChipTuner 1y ago

I agree on JSON, I may be confusing it with another nip, but I believe nip01 used to have psuedo java-script all over the place, specifically when describing schnorr signatures. I just re-read it and it looks like all the code snippets are gone

Avatar
MichaelJ 1y ago

NIP-01 has been updated several times.