Earlier quoted context omitted.
I have invites as well.
Thank you!
Keybase.io
41–50 of 117 posts
Re: Keybase.io
#426 first-come, first served invitations. I love the idea of Keybase and wish more people were using it. While it's not a replacement for keysigning parties, it's a nice probabilistic model for casual security.
If you run out of invites for HN folks, email me. (I'm https://keybase.io/chris ). We're working pretty hard on Keybase. For the last year it was just 2 of us (me and https://keybase.io/max ) , but some amazing people just joined the cause and we're building a much better service. Our Go client, for example, is almost on feature parity with the old Node reference client, and we've started working on a nice OSX GUI. A…
- 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!
Re: Keybase.io
#436 first-come, first served invitations. I love the idea of Keybase and wish more people were using it. While it's not a replacement for keysigning parties, it's a nice probabilistic model for casual security.
If you run out of invites for HN folks, email me. (I'm https://keybase.io/chris ). We're working pretty hard on Keybase. For the last year it was just 2 of us (me and https://keybase.io/max ) , but some amazing people just joined the cause and we're building a much better service. Our Go client, for example, is almost on feature parity with the old Node reference client, and we've started working on a nice OSX GUI. A…
Re: Keybase.io
#44Another one with 8 invites. Send me a mail if you want one.
Re: Keybase.io
#45Love the service. I've invited few friends (from the IT industry) and nobody ever joined. I guess there aren't so much paranoid/gpg-aware people. So I have 10 invites to give. Let me know.
Re: Keybase.io
#46Re: Keybase.io
#476 first-come, first served invitations. I love the idea of Keybase and wish more people were using it. While it's not a replacement for keysigning parties, it's a nice probabilistic model for casual security.
I'd also love an invite if you have an extra one. I'm joshcincinnati at gmail dot com. Thanks!
Re: Keybase.io
#48Re: Keybase.io
#49Re: Keybase.io
#50Been on Keybase for a while and love it. Used it with a few coworkers.