-
Notifications
You must be signed in to change notification settings - Fork 57
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
Proof request: Mastodon #72
Comments
I would like to support this and note that because of the distributed nature of the Mastodon network, Keybase verification would be very helpful. This mitigates that new accounts with the same name but hosted on a different node are confused with the "real" account. In addition, while imperfect on Twitter, Mastodon cannot replicate the blue-check mechanism. So Keybase would be the only reasonable verification system. It helps that it should be relatively simple to modify the existing Twitter verification code. I think :) |
Yeah.. a "keybase verified" icon would be nice.. :) It seems the main discussion is happening in the issue keybase/keybase-issues#2948, where the main developer (Gargron) has apparently gotten involved in discussions with keybase staff. |
I think that this can be closed. |
Not to whine, but I'm on a public mastodon instance that isn't in the keybase proofs list, |
Keybase integration has been removed from Mastodon since Keybase got acquired by Zoom and abandoned the project. |
Please add support for verifying one's self on tootsuite/mastodon instances.
The text was updated successfully, but these errors were encountered: