because the people who control the nips repo are mainly client devs and because they didn't merge it they didn't implement it

we need to find a way to move outside of their control, and create a better protocol for propagating new API methods... and this is a big problem, most of the clients are web apps, so it has to be JS libraries for the client side, or you never see it get done, and your service is never providing any use to anyone

frustrating, but IMO the simple fact that Hoyte is not even part of the nips-repo push permitted users says everything