#[0]

did you watch our #nostrica NIP panel with #[1] and #[2] ?

We discussed the idea that it would be nice to have a separation of NIPs that are more protocol-level stuff (relay<>client comms, proxies, tag indexing, key delegation, etc) and higher level stuff (kind-x's format).

atm it's all intertwined and makes it hard to keep track of the important stuff.

thoughts?

"NAPs"?

Reply to this note

Please Login to reply.

Discussion

very glad that #[0] now supports NIP-36, now I can add a trigger warning for this note 😂

#[1]

Eventually there is going to be a reorganizing

For those that want to watch and reference the session: https://www.youtube.com/watch?v=9GB7nGIhyCA&t=21600s

6 hours (0m0s) in if link doesn't autoskip

I'm afraid that would make the "protocol-level" stuff be assumed to be mandatory by default, that would cause the protocol to get bloated very easily. I've merged NIP-15 into NIP-01 to make it clear that NIP-01 is the mandatory "protocol-level" thing and nothing else, should probably also merge NIP-20. Aside from these, there is hardly any other NIP that is "protocol-level", I think.

Let me know what you think about this: https://fiatjaf.com/4c79fd7b.html