NAP + reserve its kind IDs.
(Nostr Application Proposal)
Not something that needs protocol-wide support / implementation.
#[2] #[3]
NAP + reserve its kind IDs.
(Nostr Application Proposal)
Not something that needs protocol-wide support / implementation.
#[2] #[3]
Most NIPs are not protocol-level proposals. They are just guidance for clients to implement the same features everywhere.
I'd like to Amethyst to interact with this proposal, for instance.
The NIPs are getting kind of overwhelming to follow. I think a lot of these app-level NIPs are almost more akin to an open API that could just be discussed and documented in their own repo/site.
Keep a master listing of reserved kind IDs, but then point elsewhere for the details.
Meanwhile the more protocol-level NIPs remain as NIPs but with less clutter to sort through.
Also, given where we hope this all will go, it's not really reasonable to think that every possible use case can or should be defined in one place.
I find itβs good to take a break from nips for awhile
And sometimes the irl nips take a break from us. π
Our discussions at #nostrica have really inspired me to take a deep look at NIPs... writting down my conclusions and will ask both of you for review & counsel.
that's kinda the problem though. nips should just be protocol level stuff.