The number of nips are getting out of hand. the nostr ceo needs to shut it down. #stopthenips
Discussion
I love nips
🤙
How dare you.
looking forward to hear you on nostr:npub10atn74wcwh8gahzj3m0cy22fl54tn7wxtkg55spz2e3mpf5hhcrs4602w3
Let the fax in 
The NIPs will continue until Damus launches on Android. And then they'll still continue.
These are the rules. We didn't make them.
The nips will be the death of us
death by nips. honestly, it's not a bad way to go.
Been thinking about how to navigate stuff like that structure for nips on github is to rigid to navigate and gives off a vibe that you need understand a majority of the content before you can get started on your own project.
(1) should probably move to a knowledge base format (wiki-like, wikifreedia) with (2) modular articles: being able to compose a new article from other article fragments/section. my spec for that is a blend of the long form content and lists
hyperlinked, composable, remixable.
- Describe your client by composing fragments of implemented nips, pointing to the original content.
- Apply a transformation to the nip44 definition - you don't need/care to write the original definiton, but you want your readers to read it alongside the implementations in different clients.
If a fragment comes from an existing article, you can navigate to the source within the KB
Nipsplosion 💥
Good idea, lets stop people from improving things
more nips leads to more divergence between clients, it becomes harder and harder to sell nostr’s primary use case: interoperability. my nostr hot take is that people should literally stop writing nips and just focus on solid, dumb, and highly interoperable clients. More and more stuff doesn’t necessarily make nostr better.
Maybe instead of letting people post nips, we should ask them to propose whole boobs.
The number of nipples are get out of hand… #totalrecall
I thought they were capped at 21 M....