I think you would be able to write NIP-01 much better. It‘s considered risky. But it‘s necessary.

Reply to this note

Please Login to reply.

Discussion

I would revamp the entire repo, to be honest. The current structure doesn't scale well and is too difficult to change and everyone is always squabbling over stupid stuff and shifting passages around because there's no clear architecture.

But there's no way that such a big change would go through, especially from some chick they don't even like. LOL

You could start writing Cucumber specs for the NIPs. I‘m trying, but I‘m struggling.

So far I‘ve got the server side of NIP-01 covered as sending, subscribing, filtering and notices.

they're probably missing a lot of info.

Theoretically, hear me out, hold up. 🤔

Anyone who used the NIP could adopt this as their acceptance test. Amiright?

And you could identify breaking changes with this?

Where are you writing these? On a private repo? Only found an archived cucumber repo, in your GitHub account.