Really well written. Kudos to whoever wrote your copy!
Keybase raises $10.8M
41–50 of 126 posts
Re: Keybase raises $10.8M
#42I have a small question here for the people who use keybase and it's been difficult to find answers for this. How do you encrypt per email address ? is that even possible ? I would like to use it for a personal project of mine and that would be the use case. (Sorry to hijack this thread, it might be interesting for other people).
Congratulation to the whole team for your hard work !
Re: Keybase raises $10.8M
#43From my limited following keybase.io it seems like this is mostly hobby project. How does one get investment for this kind of projects? Do you need to know someone already? Or do you decide to pull a plunge and create business plan and present it on one of these demo days organized for investors? I feel like there is a huge gap between potent, but still hobby, project and series A funding.
U jelly? I imagine you walk up to Marc and say, "Hey, we are building PGP for the world." Some days later, $10,000,000 pops in to your bank account. Edit: Would be considerate if the down-modders would provide an alternate scenario.
Edit: Would be considerate if the down-modders would provide an alternate scenario.
I'd imagine you're being downvoted more for the "U jelly?" childishness than the (im)plausibility of your (completely out of touch with reality) notion of how Keybase got their funding.
That's why I downvoted, anyway; I saw your opening line, clicked the down arrow, and moved on to the next comment without further thought or consideration.
Whether you agree with the mod-supported position that downvotes can legitimately be used as a form of disagreement or not, they're explicitly also meant to be used to discourage the kind of discourse that brings down the tone of the site. "U jelly?" certainly qualifies as that.
Re: Keybase raises $10.8M
#44I wish we didn't push outdated crypto protocols such as PGP. So many companies seem to want to invest money or development time into making PGP "better" - with one exception: they can't make it forward secure, which I think is absolutely critical in today's world of companies and individuals "losing everything" in a hack.
Investing in a protocol that will last another 20 years and doesn't even have forward secrecy seems like such a wasted opportunity. It feels like one of those things where 20 years later you think "I wish we hadn't done that then".
Re: Keybase raises $10.8M
#45Awesome! I hope some of this $ will help to shorten the waiting list queue...
I've still got six invitations - ping me.
Re: Keybase raises $10.8M
#46I have a small question here for the people who use keybase and it's been difficult to find answers for this. How do you encrypt per email address ? is that even possible ? I would like to use it for a personal project of mine and that would be the use case. (Sorry to hijack this thread, it might be interesting for other people). Congratulation to the whole team for your hard work !
I don't know what you mean by "encrypt per email address." Who is doing the encrypting, and to who? Do you want to have multiple keypairs associated with a single keybase account?
Re: Keybase raises $10.8M
#47> The Node reference client to our PGP directory will be retired. (PGP support will continue, of course.) Can anyone from Keybase shed light on the reasoning behind this? It sounds like you are moving away from programmer-friendly API libraries and into GUI apps. Even if they're open source, as a developer I really liked your up-front API. Will you still be providing those APIs?
Oh, a clarification: the Node client will be replaced by the Go version. The `keybase` command line app will be a superset of what's available in the Node client now. Sorry. So yeah - still providing those API's. PGP support will continue, always, it's just that you won't need to have PGP on all your devices -- just the ones you use PGP on. Your PGP key will be part of a family of keys you're known by. If you install…
Very excited for your repos to go public! I'd love to contribute :)
Re: Keybase raises $10.8M
#48Congrats! Increasingly pessimistic as a British subject that I'll ever be able to use something like this without attracting the attention of my own government though.
Maybe you'll be okay in the UK? Still avoiding the UK like the plague right now... http://www.businessinsider.com/uk-government-not-going-to-ba...
Unfortunately the headline for that article doesn't, to me, reflect the letter that's published at the end.
They say that they're not targeting encryption directly, but they still say that they essentially want a back door into all communications systems, which is going to necessitate either getting technology providers to give them one, or banning of those that don't.
(of course it also won't even come close to achieving their goal, but I somehow don't think that'll stop 'em)
Re: Keybase raises $10.8M
#49Earlier quoted context omitted.
U jelly? I imagine you walk up to Marc and say, "Hey, we are building PGP for the world." Some days later, $10,000,000 pops in to your bank account. Edit: Would be considerate if the down-modders would provide an alternate scenario.
Edit: Would be considerate if the down-modders would provide an alternate scenario. I'd imagine you're being downvoted more for the "U jelly?" childishness than the (im)plausibility of your (completely out of touch with reality) notion of how Keybase got their funding. That's why I downvoted, anyway; I saw your opening line, clicked the down arrow, and moved on to the next comment without further thought or considera…
Thanks for your opinion.
>"U jelly?" certainly qualifies as that.
I'd argue that maligning keybase as a hobby project qualifies as much as "U jelly?".
At least it is discourse, rather than an anonymous downmod.
Re: Keybase raises $10.8M
#50Keybase is the wrong way to do a PKI directory.
First, people should have multiple keys/identities by default; multiple identities should be the normal thing everyone does. Single identities will be used by governments to control people. They'll also work against normal communication patterns where people speak differently to different groups (think parents, friends, coworkers.)
Second, matching a name with social media is the wrong way to lookup others. It only works if people put enough personally identifiable information (PII) on their social media accounts, otherwise we won't be sure we found the right person. This matching system encourages PII, works against multiple identities, and associates multiple accounts on disparate systems. Everything you told Facebook, you've now told Reddit and Github, etc.. because the companies can also lookup your (single) Keybase identity and connect the accounts, as can advertisers and governments.
Third, leaving people to manage their own private keys is worse for security than having them managed by others. Software changes, glitches and upgrades should be overseen server-side and managed; there should be a help-desk to contact and backups should actually be done, etc... Multiple identities would make it easy to let an employer manage an 'employee' identity, and Facebook manage -or consume- a public 'personal' identity, and Twitter manage a private 'political' identity. (A PKI version of OAuth and 'Sign in with Facebook'; strong crypto can't fix the UX problem.)
I think the winning solution will be: a distributed, server-side PKI system that individuals and companies can host themselves; a DNS-like distributed registration and searching system; a host-provided web UX for managing accounts. Moving private keys to the client will work better if the local key is signed by a hosted key, rather than leaving all the private keys in the hands of end-users.