i don't know who needs to hear this right now but read and respect the NIPs, don't blindly copy other people's code. all nostr clients need to be interoperable and the spec we agreed upon is on the NIPs. there are mistakes, bugs and leftovers from experimentation in some clients.

Reply to this note

Please Login to reply.

Discussion

🤝

agree with u

Agreed, and for anyone trying to do something non-standard, NIP 78 is your friend. You can often experiment there with your own custom namespace, then upgrade user data to a standard version when it exists.

nostr:note1ey7yudl8pudn05yjn588jf0tpamefrqu99aztx5w9nlp8rjckjpq4hj45g

#nostrdesign #nostr #plebchain

“In some clients…”

I think we’re all guilty. 😂

Because everyone would simply like to prove the efficiency of their app.. Not the operability of Nostr protocol..

And so, relays are monetized & bugs laying over users interoperability with client or lack of professionalism in Nostr client building…

NIP’s are a hoax to attract users’s attention. So as to fool them.. Enough pleasures, rotten ideology!

I must confess I haven't looked at anybody else's code yet. I'm too busy for that.

Respec muh authority!

Bro tell that to Damus or Amethyst. Loads of things they do contrary to existing NIPs, then their thing becomes the new standard cause other clients implement it as well to be compatible with the big boys.