You don't trust the NYT to verify its own reporters?
Also, why do you say that in any circumstance? Who do you trust?
What happens when those individuals stop being NYT reporters? Does @nytimes.com leave them verified? Or does that account yank the verification? And who's to say @nytimes.com is only verifying NYT reporters?
> Also, why do you say that in any circumstance? Who do you trust?
People I've met in person, for one. Bluesky has an opportunity to make the old-school web-of-trust idea mainstream, with UI around "Is this someone you've met face-to-face?" and then extending that with multiple levels of checkmarks based on how many degrees of separation exist between a given user's verified personhood and your own.
Organizations actually accountable to the general public, for another. Not some corporation, even if it's a publicly-traded one like the NYT. This is the exact sort of thing that government agencies could be implementing independently as a service to their residents (like I mentioned elsewhere). Or private-sector non-profits; Associated Press would be much more trustworthy than the NYT by that virtue alone, and yet @apnews.com ain't even verified at all, let alone given the magic "trusted verifier" powers. Why?
Barring that, I trust nobody. A blue checkmark doesn't convince me someone's "real". It just convinces me someone got a blue checkmark. I'd rather see that checkmark actually mean something that I can independently verify. Keybase had the right idea there, with the ability to add proofs to your various online accounts to assert "yes, these belong to the same person"; that would be something worthy of some checkmarks. I'd be thrilled to see little icons for "yes, there's a bidirectional connection between @foo.bsky.social and github.com/foo / reddit.com/u/foo / news.ycombinator.com/user?id=foo / etc.".
Hilariously, it's kind of less centralized than I expected: there's no "Bluesky is the web of the root of trust" here, only "Bluesky chooses which records convert to UI" which leaves the whole system open for others.
It would be better to lean into BlueSky's feature set than to mimic Twitter.
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.
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.
The second, yeah, it's that the UI doesn't expose it. But the underlying APIs exist.
I’m on Bsky as well but haven’t seen any such updates.
I think this makes sense, because 1. most people want this sort of feature for news and 2. the kinds of people they verified technically are likely to play around with it and see how sound it is, which is who I'd want to be kicking the tires.
I'm not sure when they'll verify more people, but this is only the beginning, for sure.
I hear you. I haven't investigated every account that got the badge, but it feels to me like they picked people who are both technical and engaged with the protocol, so not entirely arbitrary. That naturally will have some correlation with "I know someone at bsky". I know I've seen accounts that I think are cooler than I am who didn't get verified yet! I'm sure they'll be expanding soon, which will dilute this sort of association.
The concept of verification and Bluesky's original mission of decentralization are two very at-odds concepts, and I think they've bridged that pretty well and left a lot of options for themselves to expand it in the future. I'm just worried about the very visible parallels to the Twitter ecosystem emerging.
My opinions on this will change if I join the verified elite, in case any bsky employees are in the thread.
Not necessarily. Consider the PGP Web-of-Trust model. Centralization of trust is choice, nothing inherent in verification as such.
If I want to hear what a journalist has to say, I would go to their official website like NYT or Tagesspeigel and read it there. Should we be interested in what Kim Sang yun or Sebastian Mustermann has said few minutes ago?
The problem of spam and impersonation goes way beyond Blue Checks.
You are borderline arguing that information is bad (because that's all a verification is).
Your words not mine.
I questioned why sites like X or BlueSky or Reddit can be sole in charge of who is "verified" and Real™. We can listen to what the Journalists, UN officials etc have to say on their own media websites, right?
Too much news is bad for us anyway [1]
Are they the sole arbitrator if they simply use a DNS record?
That's the same tech used to verify their official website.
Before that it was: "Someone will give you the checkmark if they like what you say enough and/or if you are deemed 'popular enough' according to an obscure committee; likely a combination of both. But there is a certain threshold above which it does not matter what you way, and you will always be verified". You could loose your checkmark on the whim of some dude who got his latte order wrong in the morning. No one was ever given the rulebook. In fact there was no rulebook. Checkmark just meant "I went to a bar with a Twitter employee and we agreed on a lot of things".
The same thing will happen to Bluesky. The system is akin to how CA and SSL does work with a critical difference. To get an SSL certificate, there is a clear step-by-step guide on how to get it. And after it has been granted it isn't revoked regardless of wether DigiCert agrees with the content of your website.
except then he was also randomly giving out checkmarks to people who didn't want them and specifically told him to remove them
Verification should always have been "This is who they say they are", not an endorsement.
The "algorithm" boosting tweets from verified accounts also showed it was an endorsement rather than verification.
When people lost verification for being distasteful, it reinforced the blue checkmark as being an endorsement.
The takeover sold-out the "value" build up from blue checkmarks by just straight up selling them. It explicitly made the platform "Pay for reach".
Why? Accounts can be sold/hacked, and there is a lot of that on social media. A verified account may even be a higher value target for some of the reasons you're bringing up, like algorithm boosts, verifications being considered an endorsement. In either case, unverification not only makes sense, but should be expected.
I'm talking about people, who are still verifiably the same people, becoming unverified.
Yes, where accounts have changed hands, or changed identity, they should be unverified.
That's actually one of the cases where twitter did not un-verify. Accounts "earned" the blue-check then changed identity to something else, appearing "verified" as that new identity.
> Verification should always have been "This is who they say they are", not an endorsement
Such things could be ripe for abuse. Although to be fair a social media platform might be able to push some of the blame onto the corporate registries.
Even trademarks only cover a company's particular domain. See the long history of Apple Corps vs Apple Computers
https://en.wikipedia.org/wiki/Apple_Corps_v_Apple_Computer
In my view this is how verification ought to work:
- A user writes a bio / about field
- A trust provider verifies that bio is factual
- Any change to that bio will cause their bio to become unverified until it can be re-verified. ( The bio change can be held back until verification can complete. )
- An appeals process exists
How "trust providers" are established without leading to excess centralisation is a difficult problem. This is especially true given that like moderation, it's an expensive thing to do.
There is the possibility of trust-chains such as the way Lobsters works, but there's a exposed to the masses I suspect that people just mass-verify everything without any checking.
In reality you'd be left with one or two central pillars that people trust, and everything else which people don't.
There's also the danger that too much verification leaves new users in the cold. If 90% of genuine users are "verified", then a brand new user doesn't have much chance of making it through filters to become known enough to hope for verification, and will find themselves ignored and effectively locked out. ( This is already the case for some platforms where you're effectively required to give your phone number else end up in the "probably a bot" pile and de-facto shadow-banned. )
In short: originally the purpose was nothing more "this account belongs to the person they claim to be and we've directly verified this with them". Unfortunately, people habitually misinterpreted the checkmark as not just being verification but also a tacit endorsement of the account by Twitter the company. Which isn't great when you get a high profile controversial event and it's lead organizer has a verified Twitter account.
After that, they appended an "in good standing" qualifier, and it quickly devolved into a "you know a person who knows a person who knows a person" situation since they also announced a public pause of the program. (Notably, the ID check, while it existed, was pretty much abandoned. Twitter at some point began demanding ID scans to report things to their support, but that obviously never actually translated to a blue check.)
Musk's version of it is hilariously simplistic, but also robs it of any and all value: just pay money for it and you'll get it. It works in the sense that it confirms the poster has a bank account (although this probably doesn't confirm much in and of itself), but any and all value of said verification is minimal because any old hack/scammer can do that.
Verification is a difficult system to get right and people have all sorts of pre-baked in ideas on how it should work versus how it actually works and the use of a checkmark played a part into how Twitters version was perceived over the years. (As well as Twitters own unreliability in being consistent about what it means.)
[0]: https://blog.giovanh.com/blog/2022/11/01/the-failure-of-acco...
Oh you could also pay Twitter employees $20K under the table to be verified too.
On a technical level, this sort of works like a Root CA: anyone can verify anyone by publishing a `app.bsky.graph.verification` record to their PDS. Bluesky then chooses to turn those from trusted accounts into the blue check, similar to browsers bundling root CAs into the browser.
* https://pdsls.dev/at://did:plc:z72i7hdynmk6r22z27h6tvur/app.... <- bluesky verifying me. it's coming from at://bsky.app, and therefore, blue check
* https://pdsls.dev/at://did:plc:3danwc67lo7obz2fmdg6jxcr/app.... <- me verifiying people I know. it's coming from at://steveklabnik.com, and therefore, no blue check.
I am not 100% sure how I feel about this feature overall, but it is something that a lot of users are clamoring for, and I'm glad it's at least "on-protcol" instead of tacked on the side somehow. We'll see how it goes.