τέχνη's avatar
τέχνη 3 weeks ago
It’s very different from NIPs. For one, lexicons have no pretense that there is or will be interoperability. They assume that there isn’t, in fact. But lexicons do assume that at least one developer is using them (it’s under their namespace). NIPs are the opposite. They assume interoperability, but in reality zero apps are using them. There is only hell if we impose it upon ourselves. Basically, it’s all about expectations and ownership. Nostr does both terribly.

Replies (1)

τέχνη's avatar
τέχνη 3 weeks ago
Also, the app developer should be the one that owns the lexicon functionality. AtProto has that right. They are the ones that want to use the lexicon. So let them support it for their users. Meanwhile, the expectation of NIP functionality is forced onto relays. Insane because Nostr relays were supposed to be dumb.