[malgorithms]

Oh, wow, this jumped the gun for us. We weren't expecting to announce this until next week! It's also in a bit of a draft form, and we expect to improve this integration guide as we add partners.

Keybase's view: identity on the Internet should not be just about Twitter, Facebook, and the other superpowers. Your membership to any site might be meaningful to other people, whether that membership is to something small like a phpBB forum about motorcycles, or something big like LinkedIn or Etsy. Often, the smaller the community, the more meaningful and close-knit membership is. And the more that community might want access to secure tools such as Keybase. If you're on the forum, you might _really_ need to reach out to another user of that forum, securely.

It might be a good time to mention that Keybase is looking to hire an Identity Evangelist[1]. This would be someone with a tech background (i.e., from the HN crowd), who has great presentation skills and experience, and who wants to help other sites and apps integrate with Keybase.

[1] https://keybase.io/jobs#evangelist

[ocdtrekkie]

I'm really glad to see opinions like this that are strongly tinged against the centralized web, coupled with engineering work to enable more independence. Thank you.

A highlight point for me is that services should support both those superpowers and smaller entities, as yours does. Rather than isolating the open web from these entities, we need to make bridges between them so people can cross.

[eridius]

Why does Keybase allow a single remote identity to link to multiple Keybase accounts, but does not allow one Keybase account to link to multiple remote identities (on the same service)? If I run multiple Twitter accounts, I don't see why I shouldn't be able to link them all to my Keybase profile.

[gervase]

I think this might be a side effect of the Keybase UI, not the service itself. If you interact with the APIs directly and look at the JSON, you can see that at a high level the proofs are a dict, with each service as the key, and the value is an array aggregating several proofs. You could therefore potentially have several Twitter proofs associated with different accounts ("nametags") that could then be presented all together if someone wanted to tie all those accounts to your identity.

I only skimmed TFA, so I'm not sure what the process would be like for actually validating those proofs, but the backend datastore seems like it wouldn't have a problem, at least.

[eridius]

The new Proof Integration Guide explicitly says that a Keybase account can only be linked to a single identity on your identity service (but that you can link multiple keybase accounts to that same identity if you want to).