NIPs that pretend to do one thing and they don’t are harmful to nostr and innovation; it’s hard to identify this during the NIP process but we should work on bringing this when reality emerged its head.

NIP-26 is a good example but not the only one.

Reply to this note

Please Login to reply.

Discussion

Few understand.

What are the other ones? :) Now I am curious

The NIP seemed awesome when we wrote it, But its real world Utility is Doomed. Better NIP it quick in the BUD.

πŸ€ͺπŸ€ͺπŸ€ͺπŸ€ͺπŸ˜‚

I think that's the case for all NIPs πŸ˜…

I don't understand. It's there anything wrong with NIP-26?

I don't understand either but here's a link to it in case someone wants to provide a fresh perspective. https://github.com/nostr-protocol/nips/blob/master/26.md

Yeah, I already read that NIP. But I can't find anything wrong.

I dunno the NIP contrib stuff. What if you add template in GitHub to force listing the negative outcomes first hahaha