I've got a few Keybase invites, email me if you want one!
I got some invites left, ping me if you want
Introducing the Keybase filesystem
451–460 of 501 posts
Re: Introducing the Keybase filesystem
#452Earlier quoted context omitted.
prod·uct \ˈprä-(ˌ)dəkt\ 2.a.1 Something produced ; 2.b Something resulting from or necessarily following from a set of conditions. This book is the product of many years of hard work. ( http://www.merriam-webster.com/dictionary/product ) There's another sense (not listed) in which "product" specifically refers to prohibited drugs. I know, and you should know, that quadrangle wasn't using that sense. As regards the po…
He is not "plainly wrong" if the first definition of the word in question is literally supporting what he is saying. Your assertion of his correctness is what is plainly wrong.
The bit rburhum objected to says "We're not trying to make money. We're testing a product right now." This is correct idiomatic use of the word "product" (in the sense "something we make"), and it's a relevant answer ("we don't have one") to the question "what is your business model?".
Re: Introducing the Keybase filesystem
#453Re: Introducing the Keybase filesystem
#454Earlier quoted context omitted.
I don't think Keybase is glossing over security at all. First of all, you don't have to use the browser app at all. I personally don't trust Javascript crypto and hence don't do anything in the web app. They're also acutely aware of the dangers of centralization and all the Keybase crypto is based on minimal trust. Check the documentation: https://keybase.io/docs/server_security
Personally, I don't want someone else storing my private keys; which is a pre-condition for doing anything you'd have to worry about in the browser anyway.
Re: Introducing the Keybase filesystem
#455I have 9 invites and I do not particularly want to trawl through all of the existing comments to find people who may or may not have been invited since having posted their comments hours ago. So, reply to me here or email me (wanda {at} teknik.io) and I will send you an invite. First co-- actually, first noticed, first served.
I'd like an invite if you have more to spare. (johnsonwesleyt {at} gmail)
Re: Introducing the Keybase filesystem
#456I have 9 invites and I do not particularly want to trawl through all of the existing comments to find people who may or may not have been invited since having posted their comments hours ago. So, reply to me here or email me (wanda {at} teknik.io) and I will send you an invite. First co-- actually, first noticed, first served.
I'd like an invite. The email address is in my profile.
Re: Introducing the Keybase filesystem
#457I have 9 invites and I do not particularly want to trawl through all of the existing comments to find people who may or may not have been invited since having posted their comments hours ago. So, reply to me here or email me (wanda {at} teknik.io) and I will send you an invite. First co-- actually, first noticed, first served.
Keen as, would love an invite. (daniel {at} protonome.com)
Re: Introducing the Keybase filesystem
#458I have 9 invites and I do not particularly want to trawl through all of the existing comments to find people who may or may not have been invited since having posted their comments hours ago. So, reply to me here or email me (wanda {at} teknik.io) and I will send you an invite. First co-- actually, first noticed, first served.
I'd love an invite. bhbatha {at} gmail.com
Re: Introducing the Keybase filesystem
#459Re: Introducing the Keybase filesystem
#460I have 9 invites and I do not particularly want to trawl through all of the existing comments to find people who may or may not have been invited since having posted their comments hours ago. So, reply to me here or email me (wanda {at} teknik.io) and I will send you an invite. First co-- actually, first noticed, first served.
I'd like an invite.