-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verified users #8276
Comments
I think the best way to deal with it would be self hosting, if you trust my website to be mine and trust me you can trust everything that is through my website to be either mine or somehow endorsed by me unless stated otherwise. Of course that requires a lot of work but there are many services which will do the heavy lifting for you, and if you're a public figure you probably have enough money to do all that. |
keybase.io exists for the purposes of online identity verification |
I second the keybase.io suggestion. I have my own DIY proof pinned to my profile. You can check it against my Keybase profile. |
Seems like Wil has accomplished what was needed without any code. Development resources are better spent elsewhere than on solving this "problem" which can be handled informally very easily as this example demonstrates. |
I don't think that we should elevate users above other users with a "verified" tag of any kind. |
This has been hashed out before (see for example #913). |
Verified status is a marketing ploy from Twitter, and the one that has backfilred -- i.e. they have verified a bunch of Nazis. Even if it were a good idea in theory, from the technical standpoint in the de-centralized system like mastodon there's no real center authority for verification, so you would have to trust the admin of the instance to 'verify' users. Also there's nothing prevents any users to start their own instances 'verify' themselves on it, and confuse or impersonate every. Currently it's possible to just add keybase.io or gpg idenity or any kind of identity verification link into profile metadata or pinned toot with no changes required to code database. |
you can already put verified checkmark emoji on your name |
Sorry to be blunt, but… why is that a needed feature? I'm pretty foreign to twitter and facebook and the like and maybe I missed something. |
Here's what to do:
|
Here's the thing about this (and any other "verification" or claim of authenticity or provenance): it's inherently a matter of trust. Twitter's "verified" checkmark is nothing more than a claim towards Twitter's authority. Asking to verify a Mastodon profile is like asking to verify any web page in existence. You simply substitute Twitter's authority with some other authority -- perhaps you share your profile in person, or you have a presence somewhere that is trustworthy. Wil Wheaton has wilwheaton.net, his Twitter, his Facebook, and so on -- any of these can do. For someone who does not have any of those, they will have to find some other way to make their followers trust that they are who they say they are -- and there will never be any guarantees. The fundamental problem of trust is entirely societal and not strictly technological. Even in person, you can claim to be someone you are not. |
@avolkov I see your points about the decentralized nature of mastodon. However I think account verification could be beneficial for certain specialized instances that have good reasons for it. As an example, there could be an academia instance where you could easily get verification that you are a researcher with e.g. a university mail address (this is all GoogleScholar requires too). Then it would be great if the interface allowed to show messages by verified accounts only. Given the toxicity of angry, anonymous Twitter users I often wish that a basic filter like this existed over there, as it would make their service much more useful for staying up-to-date in research. It would be great if this could be considered open-mindedly. Setting up rules that avoid toxicity and any kind of distraction economy is where (I believe) the real potential of Mastodon lies. |
Mastodon should offer a way to support verified users. See that toot of Wil Wheaton: He uses his verified Facebook account to verify that a specific Mastodon user belongs to him. That's obviously a subpar solution.
Years ago app.net had a html based validation for your website and domain validation (with text entries added to your dns). You created the code in your profile and added it to the website or dns server and you got a little checkmark in your profile and it also showed which domain was used to validate that account.
The text was updated successfully, but these errors were encountered: