Do what works for you, but dont remove the authorship from the work of others, without consent. And certainly not in 12 hours. That is not an open process.

I think Melvin may be too used to the W3C world where the spec is the only thing that matters and people write tons of specs and then 99% of them are never implemented but they still talk about the specs and spec authors with religious respect and ceremony -- so he thinks the NIPs repo is a very powerful entity.

In fact the NIPs repo is constantly running behind implementations and trying to stay relevant in a chaotic scenario of 32 different clients each with their own priorities.

Yeah I’ve worked with standards bodies and there are problems. In particular there is the way language around inclusivity and support are used to create overly complicated standards that are subject to capture by institutional players. I worked on OAuth and saw how the original vision, elegant security, and simplicity of OAuth 1.0 was lost so we could neet the needs of google.

IETF does a better job than W3C but they’re all operating under a paradigm of big companies making very static systems.

Rough consensus and running code is bettet than a consortium where you need to pay $50k a year and have full time staffers in order to participate in the open standards process.