I don’t see what people’s problem with this is. It’s not like it’s anyone can just buy a blue check (unlike X). It’s just confirming that the account belongs to who it claims to be (like old Twitter verified users). I don’t know if that requires any payment, but it’s definitely not “Here’s $5 – okay, here’s your blue check”.
During this initial phase, Bluesky is not accepting direct applications for verification," the company said.
“As this feature stabilizes, we’ll launch a request form for notable and authentic accounts interested in becoming verified or becoming trusted verifiers.”
If I remember correctly, that’s pretty much exactly how old Twitter rolled out its original user verification.
From a de-centralized perspective, I’m not sure how that would work. I guess each instance would be in charge of verification and setting the “verified” flag for the account? The alternative would be some kind of central authority. Granted, I know little of Bluesky (microblogging is not my cup of tea), so I may be way off on my guesses there.
From decentralised perspective the verification data is stored in the verifiers PDS rather than having the verified-certificate in the subjects PDS which means this particular check is always for the official BlueSky server only and won’t be federated anywhere else. Other potential servers are free to implement their own (potentially different!) local verification scheme with it, but it’s never going to be network wide and it never federates anywhere except the server where it’s implemented.
This is why I commented earlier about their decision to move to ”traditional” social networking space and away from decentralised networking
I don’t see what people’s problem with this is. It’s not like it’s anyone can just buy a blue check (unlike X). It’s just confirming that the account belongs to who it claims to be (like old Twitter verified users). I don’t know if that requires any payment, but it’s definitely not “Here’s $5 – okay, here’s your blue check”.
If I remember correctly, that’s pretty much exactly how old Twitter rolled out its original user verification.
From a de-centralized perspective, I’m not sure how that would work. I guess each instance would be in charge of verification and setting the “verified” flag for the account? The alternative would be some kind of central authority. Granted, I know little of Bluesky (microblogging is not my cup of tea), so I may be way off on my guesses there.
From decentralised perspective the verification data is stored in the verifiers PDS rather than having the verified-certificate in the subjects PDS which means this particular check is always for the official BlueSky server only and won’t be federated anywhere else. Other potential servers are free to implement their own (potentially different!) local verification scheme with it, but it’s never going to be network wide and it never federates anywhere except the server where it’s implemented.
This is why I commented earlier about their decision to move to ”traditional” social networking space and away from decentralised networking