This is better than twitters nonsensical verification but still does not close the loop all the way. I think what is needed are a set of equivalency verificatio

This is better than twitters nonsensical verification but still does not close the loop all the way. I think what is needed are a set of equivalency verification's. Sort of like the domain verification used in getting a TLS certificate. Something like bluesky user X is equivalent(has control) to domain A(domain verification) to youtube account B (youtube verification) to mastodon account C (mastodon verification) to D@nytimes.com (email verification) So logically I would expect a protocol that allows cross domain verification. Best I can come up with is something that works sort of like domain verification extended to user@domain verification. that is, a better engineered version of "make a youtube video with the string 'unique uuid code' in the comment" so that we can verify you own that youtube account" The problem is that some domains would have no problem standing up this sort of verification. The Times only benefits from verifying it's employees. However I can see fellow social media sites balking as this equivalency weakens their walls that keep people in.