The process is annoying only if your ego is in the way. Once I learned how to avoid that bias, things become just about technicalities: is it the best way of doing it, is it too simple, or is it too hard? Too prescriptive or too broad and vague? Most of those answers are subjective and thus most decisions on the NIP repo just reflect the "feelings" of devs in the debate. Once you understand that, you stop caring about perfection and engineering qualities and start caring more about "are people actually going to code this shit and is it actually useful?"...

Replies (2)

Fine. We'll submit NKBIP-01 for review, since it's been implemented in multiple clients, covers something very basic, and people keep asking us where the spec is because they want to use it, and see how it goes.
Remove the WHY section. No one cares. Keep things as if you were writing a TLDR.. Don't use jargon or your own naming convention for things. "Dumb english" is best. Show an example as soon as possible. Then explain what the kinds do, and the fields in them.