Bluesky already has domain based verification which solves that perfectly, I guess people just don’t want to use it.

Sure, but until it actually gets used significantly in that way, we might as well just say it’s centralized.

It’s the username so already quite visible.

For example someone at say, NPR, could use a name like @bob.npr.org which is only possible by verifying ownership of the npr.org domain name, so there is no need to vet anything.

How come they don’t use the already built in domain verification? It’s basically fool proof to certify that an account is owned by a specific entity.

It already has domain verification which is better IMO. Its more reliable and safer as you have to own the domain to use it.

Nope, it’s 100% centralized.