Woo-hoo! I'm a fan of Keybase (although, I'll admit, I've received barely any encrypted communication from the outside world). The first version of their product did a whole lot to open up secure communication to "the masses," by simplifying strong encryption into an easy-to-use app.
I'm glad that the Keybase team decided that they didn't want to stop there. I'm not sure that I'll use the new keying system (my use case isn't very risky), but I do think that a lot of people will.
In my opinion, the more people that have access to easily-used crypto, the better.
> "I'm not sure that I'll use the new keying system (my use case isn't very risky)"
To be clear, you'll be using this system automatically if you install Keybase on your phone or desktop. It'll just work, and you'll have a private key on that device. As you add devices, you'll collect keys. If you remove a device, that public key will no longer be a part of your identity.
If you want to use PGP on one of those devices, you can. And you can strongly connect it to your other keys, as the graphs in the post show.
This should be easier. From a "regular" non-PGP user perspective, you needn't think of this as managing keys, or adopting a more advanced key system. Instead you would just be managing your devices and installing Keybase.
That's our hope anyway. (Disclosure: I'm one of the people working on the project - https://keybase.io/chris - thanks for the kind words about the project)
That's awesome -- and thank you for the clarification. I'm primarily a user of the webapp, although I have the CLI application on a server (hence not using mobile stuff, multiple machines, etc).
I'm a big fan of your product, and recommend it broadly -- great work so far!
I'm glad that the Keybase team decided that they didn't want to stop there. I'm not sure that I'll use the new keying system (my use case isn't very risky), but I do think that a lot of people will.
In my opinion, the more people that have access to easily-used crypto, the better.