keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.83k stars 1.22k forks source link

Fosstodon Proof broken, and replace not working #24706

Open gbschenkel opened 2 years ago

gbschenkel commented 2 years ago

Keybase start fail to validate my identity proof, I tried to replace it, but Keybase are trying use a invalid link. I think Keybase is using an outdated API from Mastodon. I wounder is other instances are with problems too.

Keybase are trying to open this URL: https://fosstodon.org/settings/identity_proofs/new?provider=keybase&token={TOKEN}&provider_username=gbschenkel&username=gbschenkel&user_agent=linux:5.8.1

scarhead7 commented 2 years ago

My proof for Fosstodon has been broken for three days too.

pinheadmz commented 2 years ago

Same here. On bitcoinhackers.org

jonhoo commented 2 years ago

Same thing here. Link to Keybase profile. Link to Proof.

dallemon commented 2 years ago

this seems related https://github.com/mastodon/mastodon/pull/17045

jonhoo commented 2 years ago

Oh, that seems very sad indeed. https://github.com/mastodon/mastodon/pull/17045#issuecomment-988135764 does state that that change hasn't made it into production yet though (unless fosstodon adopted it eagerly?).

wiktor-k commented 2 years ago

I guess quite a lot of instances use unreleased Mastodon code and that's why it broke eagerly. It seems the official way is to use link verifications (adding profile link to GitHub or Twitter should automatically verify). As for something that uses cryptographic proofs for social sites there is https://keyoxide.org/ and it provides link verification out of the box (so it will work with Mastodon).

gbschenkel commented 2 years ago

As described in #24760, will be good to have verification like the one working on Twitter.

glenn-sorrentino commented 1 year ago

+1