If I may use this as a way to publicly suggest some features that I would love to see: - Client should support looking at my existing trust.db. I already have

If I may use this as a way to publicly suggest some features that I would love to see: - Client should support looking at my existing trust.db. I already have a number of signatures I collected pre-keybase, and I have verified a bunch of identities. I'd like to use these, and in fact be able to tell keybase.io that I have more than just social web proof that these are who they say they are. - Ability to use email addresses instead of just keybase names when referring to users. - Autocomplete when typing handles/emails on the client's command line. Using the Node client currently without this feature. - When I tried to encrypt a file using keybase recently, it gave me an obscure error (#100) instead of telling me that I was logged out. - encrypt should not silently create a new file by default. It should not overwrite an existing file either. Do `keybase encrypt joe@example.com foo.txt` twice, and have foo.txt.acs overwritten the second time. Instead by default it should output to stdout, and let you specify a file as an optional argument. - Lastly, and this is way outside the scope of what keybase currently does, I'd love a built-in tool for exchanging encrypted files. Currently, I use chunk.io + curl + gpg to do this: function send-encrypted() { gpg -o - -aer "$2" "$1" | curl -T - http://chunk.io } I am not suggesting that you guys host any type of file sharing tool, but perhaps integration with a service like chunk.io or similar would be nice. Otherwise, the process of sharing a secret (say a file with API keys, etc.) with a co-worker is to encrypt the file, then email it, which is annoying. Thanks so much for the great work you are doing!