"there are too many NIPs, I liked when the protocol was just a half-dozen NIPs"

"we will need hundreds of thousands of NIPs in order to standardize all forms of human communication"

Reply to this note

Please Login to reply.

Discussion

Edited post? Really?

The nips will multiply until morale improves.

I believe only the base protocol needs to be standardized. After that, a standard for creating application-specific events or event types should be established, allowing for unambiguous numbering for each subprotocol or application. Each application can then create its own standards, separate from the base protocol.

Isn't that how you loose the interoperability after time?

we already lost interoperability

see this thread? nostr:nevent1qqsys0tx38hmj27mtyase9m6hn5ejlvk8cqgcfvq69mscrhd0vghg0cfuc4lj

0xchat and amethyst are in conflict because both are using the protocol in different ways. Interoperability is already compromised;

Oh crap 😮‍💨

so either you simplify the main protocol and any fancy stuff clients implement must be done in optional events or fields, or you make anything into nips everyone has to follow and the protocol becomes bloated and new clients will never be able to keep up.

Agree 💯

I’m a bit confused. 0xChat doesn’t use @npub, which is not the standard practice.

What do you mean? 0xChat is built on Nostr, and your account is based on your npub. Can you explain a bit more?

Oh, I see what you're saying. I missed the @ in your reply and thought you were referring to to npub in general. Yeah, that's kinda weird. @npub is supported on pretty much every client I've used other than 0xChat. Perhaps they'll add it in a future relase?

the thing, some clients are using it, others are not. so interoperability was compromised by clients implementing non standard features.

It's always frustrating when a client decides to buck the standards in favor of some unique implementation. I wish interoperability was prioritized more often than it is.

What I’m referring to here is the implementation of mentions :). Some clients use @npub, but the standard practice is nostr:npub.

Sorry 🤦‍♂️

I’ll make a NIP just lemme learn to code first

I am always fascinated by the variety of nips