I 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.
Introducing the Keybase filesystem
381–390 of 501 posts
Re: Introducing the Keybase filesystem
#382Re: Introducing the Keybase filesystem
#383Re: Introducing the Keybase filesystem
#384Earlier quoted context omitted.
Zcash is an actually anonymous cryptocurrency (BitCoin is not, since senders and receivers are public). The crypto is definitely impressive (which it is, it uses zero knowledge proofs -- which are really cool math -- for a lot of its sending operations).
I see, thanks! I'll look more into it, it sounds interesting. By the way, how did you manage to install Keybase FS? It won't work for me at all.
Re: Introducing the Keybase filesystem
#385Any idea how to get this working on Arch? The latest version looks to be about 2 weeks old.
How about the "keybase-release" package from AUR?
Re: Introducing the Keybase filesystem
#386Re: Introducing the Keybase filesystem
#387Re: Introducing the Keybase filesystem
#388I have 8 invites if any other stragglers (6 hours after the story was posted) are still reading. I'm heading to bed but will send them during morning coffee, GMT -5. (please make sure your email is in your profile)
I would greatly appreciate an invite as well (ben[at]jelled.com).
Re: Introducing the Keybase filesystem
#389About 4 years ago I was involved with a commercial software project attempting to do exactly this. What we built worked but it wasn't positioned in a way that interested our target audience (Enterprise customers). First, bravo for making it happen in a way that is getting people excited. Second, I sincerely wish you the best luck in getting people to pay for it in a way that is sustainable for a business. We built a…
Could someone with more expertise explain how Keybase protects against MitM attacks please? Does it simply rely on the difficulty of compromising the SSL certs of multiple assertions (twitter.com, github.com, etc)?
As far as I can tell, if someone was able to 'pretend' to be Twitter, ie, MitM an HTTPS connection to twitter.com, they could 'pretend' to be someone who only has their Keybase info on Twitter. Of course, putting your key data in more places makes it harder to appear as you.