Threads will occasionally be incoherent, yes.
And adding complexity is one of the things we've been upset about because we're trying to get more developers making clients and now the hurdle has been raised in a big way.
As a friend said, we've now officially passed the Lone Wolf Threshold, where one developer can easily spin up a minimal K01 client within a week. Especially as this additional kind is (theoretically) not mandatory and the spec will be prone to frequent alterations.
One issue is that the inconsistency will be between clients that only support NIP-01 and clients that support edits.
This should never be the case. NIP-01 is the core of Nostr, so a client that ONLY support NIP-01 should never be wrong about anything.
Consider the integration with payment systems, for example. You are free to not implement it in your client (I won't in mine) and that will never lead to any inconsistency, just a missing feature.
People who aren't developing a client probably don't even get what a big deal that is.
It's a big deal.
I'm not sure it's a huge deal, but it does inevitably lead to having to compromise on efficiency.
Thread collapsed
Thread collapsed
Thread collapsed