We should aim to have as few NIPs as possible, only what’s necessary

Reply to this note

Please Login to reply.

Discussion

What’s necessary?

🤷‍♂️

More than 2 nipples is just not very natural

Correct me if I’m wrong, but I believe only NIP-01 is mandatory. Beyond that, all the NIPs are à la cart. I honestly don’t see the harm in having a wide variety of choices.

Fr?

Exactly, it’s up the clients to decide which NIPs to support or ignore.

And the relays.

From NIP-01: “New NIPs may add new optional (or mandatory) fields and messages and features…”

Are any of the other NIPs mandatory? I don’t think so, but I did not search very long.

We agree that there should be as few *mandatory* NIPs as possible. I honestly think Nostr is doing this right—a minimal base of mandatory NIPs plus whatever optional features that clients and relays choose.

I like that different clients have compatible features. How do we accomplish this without additional NIPs? (This is not a gotcha. I am sincerely open to other ideas.)