> To send us the config, you can send us the public URL for your config file or attach it directly in a Keybase chat message to @mlsteele or email miles@keyba.se. In our example the file is hosted at https://keybase.io/.well-known/example-proof-config.json.
Will this always require manual step (sending config by e-mail) or is there some automation planned?
Good q - this step will likely be automated soon. Still, there will always be one final step of our approving any integration, otherwise there would be 10,000 pr0n sites or ad sites. (We mention this in the FAQ.) But we can automate everything up to turning it on.
For now, we want to talk to everyone working on integrations, so we can see what steps are working and what are confusing, what could be improved, etc. So we're talking to everyone doing an integration.
I still don't get it. You have always been able to get a keybase proof for ANY website/domain without being approved first. Why do you need to whitelist mastodon instances? Why not just let people type in the domain name for their instance and get rolling?
Again…why? who cares? Why is picking from a pre-approved list better than just letting people type in their instance domain name and allowing every instance by default?
Agreed. Not to mention Mastodon could've a linkback to Keybase with all data pre-filled (username + instance name). For example in Settings a link "Connect with Keybase".
> otherwise there would be 10,000 pr0n sites or ad sites.
There's a middle ground: you can add integration so that it's available from CLI (`keybase prove ...`) but don't show it in GUI ("select integration") so it's not advertising that site.
The proof integration guide looks neat by the way.
Assuming my understanding of this is right, I can't see Chris and team publishing an automated platform for proof integration until they find a solution against impersonating established platforms.
For now, we want to talk to everyone working on integrations, so we can see what steps are working and what are confusing, what could be improved, etc. So we're talking to everyone doing an integration.