Federation

As long as Keybase is a single source of authority, it's a target for attack and coercion. That's a problem. Like SKS, email, Jabber, or any other large-scale piece of infrastructure, Keybase should federate.

This means that anyone should be able to run a Keybase server and have it be just as authoritative as the one at . When someone uploads new or changed info to any keybase server, it should sensibly propagate between them.

This requires design changes. Right now, Keybase (presumably) stores a bunch of user-related data in an unauthenticated database. Keybase has user accounts, where Keybase authenticates users to allow them to change things. These are dangerous design features, but they can all be fixed.

The issue names no files, tests, or entry points. Begin by documenting the current authority, account-authentication, and data-propagation design, then establish the federation protocol and security model; done would require an agreed design before implementation.

Written by the indexing model from the issue text.