Its just formalizing the wot verification that already happens on a single kind 1.
I don't disagree with you that it works in the same way, but you have to see that it is way more complicated to implement for the exact same result.
OTS alone is not even coded by 99% of nostr apps.
Login to reply
Replies (2)
It's not just that. It's a model for identity continuation. Using Kind 1s for this is the wrong approach by far. They are overloaded and can easily get lost in the feed. A specific kind for identity checkpoints would have cleaner semantics and could be rendered in a feed. There's also no hard requirement for OTS, and if it is used, clients can always rely on a client that renders it with a rich UI/UX, like NIP-89 does. In any case, I'm not here to convince anyone. I've never liked politics.
People are using all kinds for this, not just kind one. It's not about kind 1 at all. They use whatever kind is available in the app they use.
It's about ease of use and integrity of identity across all apps and all relays.