Feature suggestion: Precaution levels

There has been a lot of discussion whether Keybase should provide convenience by storing (encrypted) private key online or security by discouraging online storage of private key.

I would like to suggest a solution for this dilemma - precaution levels. There could be three levels:

• Extreme: disables use of Keybase clients other than web; disables online storage of private key
• High: disables online storage of private key
• Low: enables all functionality

Precaution levels could normally be only decreased, increasing would be allowed only when publishing new public key. Keybase could offer only functionality corresponding to user's precaution level (e.g. if precaution level is set to extreme Keybase.io should never offer storing private key online or using Keybase command line client). Precaution level could be signed by user's key and stored on Keybase servers (to prevent changing behavior of non-compromised Keybase command-line client by compromising Keybase servers (or communication with them)).

Start by reviewing the Keybase client, web, and server behavior around private-key storage and command-line access; the issue names no files or tests. Define how the three precaution levels are represented, signed, stored, and enforced, then verify that each level permits only its stated functionality and that increases require publishing a new public key.