Inconsistency in clients is a feature not a bug.

Reply to this note

Please Login to reply.

Discussion

Yep, I use #Plebstr, #Amethyst, and #Iris in different ways based on what I'm doing.

Ehhh yes, but also depends on how those clients adapt to those inconsistencies

Agreed, each is it's own experience. It took some experimentation & time for me to see it that way though.

It's a bad feature.

Why? We’re privileged to even have multiple clients to access one protocol. Developer creativity helps us re-examine the way other clients or other apps outside of nostr do things and whether that’s the right way to do it.

It also serves as a motivator for shipping fast. If your inconsistent behavior is annoying, people switch to something else. It’s a quick feedback mechanism that allows everyone on the protocol to see the optimal way of doing things and find even better ways. Instead of linear learning (do x, observe, adjust), we get a sort of mesh network of knowledge exchange.

It’s only annoying if your notes are not visible or images don’t show - that I can agree on πŸ€—

I'm mostly referring to inconsistencies of NIP implementations. It makes it hard for new users to browse the protocol with too many inconsistencies.

πŸ€” ok maybe I’m not thinking about the things on your mind in this case.