Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

They do have different semantics, but the more I think about it, the more I think that's better.

The blue check on your account doesn't tell me what about the account has been verified. It probably means you're the Steve Klabnik that shows up a bunch of places in a web search, but that would mean much less if someone else also had that name and a web presence.

Your verified domain name tells me much more, but I recognize that's not the right verification approach for everyone. What I think would be more meaningful is labels like "@rust-lang.org says @steveklabnik.com is a Rust core developer" or perhaps a label with some metadata given special treatment in the UI showing mutual affiliation, e.g. "@rust-lang.org and @steveklabnik.com say they're affiliated with each other".

Edit - a further refinement: instead of verificatiions, allow accounts to feature labels placed on them by others for special treatment in the UI.



That’s how this feature works. If you click on the blue check, it even shows which account did the verification.

It’s true that it’s not generally exposed yet. We’ll see if they do. I think that would be neat but I also am unsure if that’s what non-power users truly want.


It's close, but it falls short on two points: verification doesn't tell me what the verifier is asserting about the account, and the current implementation doesn't embrace decentralization, at least in the UI.


Yeah, the first is true, it only asserts that there is a "relationship" between the accounts.

The second, yeah, it's that the UI doesn't expose it. But the underlying APIs exist.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: