firebreathingduck on Nostr: npub105ve7…9hk8p thanks, that makes sense. But you still run into schema ...

npub105ve72qqmjxz08skum2lkds9qkj67689djwwr2a0qkrxts3hqydqm9hk8p (npub105v…hk8p)

thanks, that makes sense.

But you still run into schema inflexibility risks with natural keys, right? What if a URL moves, or a customer changes their name after a divorce, or a product gets renamed, or a key that was implemented as one field now needs two?