4 ms·
I have another suggestion: keep a public database of linked accounts: someone@gmail.com == someone@twitter == someone@keybase. Let people append to their set of
by fiatjaf 9y ago
I have another suggestion: keep a public database of linked accounts: someone@gmail.com == someone@twitter == someone@keybase. Let people append to their set of linked accounts only if they prove to control at least one of the accounts in the set plus the account being added.
How do you prove you control something? I don't know.
- niftich 9y agoYou mention Keybase as one of those accounts, but isn't this one of the goals of Keybase? See: https://keybase.io/docs/command_line https://keybase.io/docs/command_line
- fiatjaf 9y agoNo, Keybase uses these social network proofs to verify the ownership of the public key so you can encrypt messages to it, like what a "web of trust" would do in traditional public key directories. Since they need public proofs, email will not be supported, for example. Also, they're very slow[1] in adding more providers, or perhaps they don't want more providers. But yes, I think the database Keybase is building can be used for a login system somehow. [1]: https://github.com/keybase/keybase-issues/issues/518 https://github.com/keybase/keybase-issues/issues/518