Yes, you can architect a system that's more difficult to compromise or knock offline, but a better solution would be to remove the need to trust the server or t

Yes, you can architect a system that's more difficult to compromise or knock offline, but a better solution would be to remove the need to trust the server or to have it constantly online. To their credit, the Keybase guys have done this - their client fetches information about a user from the Keybase server, but performs the verifications itself and deposits the public key into your PGP keyring if successful. Once that's done, you don't need Kebase at all in order to communicate with that person securely.