NIPs are fine. Most people take them way too seriously though. It's just a place to interoperate. We need a place for that.
To me, NIPs are a reflection of usage. If that is what we want to do, we can create a portal where each client/relay declares their support for NIPs and the most supported one become an official nostr list. If clients drop support over time, they disappear from the list. A backwards way of developing specs, but one that trully represents what Nostr is about.
I agree, that's why I want to get rid of them.
The way they exist now gives too many wrong impressions. People see a central registry of NIPs and think that is "the Nostr protocol", when in fact many of those NIPs are not used already (or most people agree they shouldn't be used) and we can't touch anything on the list because it is a very serious list. At the same time there are many kinds being actively used with multiple implementations that aren't merged on the repo, and, most importantly, the way in which each kind is or should be used is not in the repo either.
Once the "official NIPs" aren't a thing anymore someone (or actually many people) can create independent registries that track implementations or do the job the current NIPs repo is doing, but much better and in a more fluid, opinionated way.
I don't know... I was hoping we could have a better portal for NIPs inside of Nostr. But all implementations for that kinda suck.
Yes. Probably because NIPs are the wrong abstraction. But also because we're stretched too thin trying to make all the things "on Nostr" at the same time.
