It doesn't show all of the kinds. Not all kinds have a merged NIP.

Reply to this note

Please Login to reply.

Discussion

Most new kinds going forward will not have a NIP in the NIP repo.

People need to adjust to the new reality that they can't manage 5 gazillion NIPs and many future NIPs will be for use cases that the repo owners can't understand or evaluate.

Let it go. Move on.

An open protocol doesn't need a Central Committee to run it.

nostr:nevent1qqsxrwk7d8lzhcn8hturxdl22n43ru8n9mdkekyhfrwealej6wxhmkcpramhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjsygxavex4usqkgvage45lqpdwzjqgqs630zd4nhj67p38dhn9vv7nrypsgqqqqqqs7adu4l

Yep. There’s NIPs for core functionality, then there’s everything else

Yeah, things like npubs/nsec, how to define a relay, how to structure a note, how to delete a note, etc. made sense in a centralized place.

Trying to explain to some Twitter-clone devs why I need some particular NIP for transmitting EU export papers, to cover them with transport insurance for dangerous goods in flight...

Not gonna happen.