These benefits can be obtained by sharing a remote encrypted filesystem , in which sits an ordinary git repo. Then simply check out that git repo using a file://path/to/repo reference, creating a clone on a local drive out of the encrypted volume. The encrypted filesystem can then reside on an untrusted server in the cloud. Ultimately, this is a cleaner solution than the whack-a-mole approach of hacking every applica…
This question has a FAQ entry near the bottom of TFA: > Why not just make a bare repo in KBFS? The Keybase filesystem journals changes and syncs them after writes, kind of like Dropbox. Which means you and another team member could be fighting each other and make a conflicted HEAD, where there'd be 2 copies side by side. Similarly, you shouldn't put git repos in Dropbox. Keybase's git prevents this by locking. Also:…
Keybase launches encrypted Git
141–150 of 277 posts
Re: Keybase launches encrypted Git
#142Re: Keybase launches encrypted Git
#143Earlier quoted context omitted.
So I love Keybase unconditionally and if you guys weren't rolling in physical offices (and not one in Boston) I'd have been beating down your door to come work there--I think what Keybase is doing is important and it's something I'd love to work on. But I have a serious question that maybe you can answer, and it's something everybody who I've showed this to has asked me: How is Keybase gonna make money? How am I assu…
We believe the right long-term answer for Keybase is finding a way to charge large corporations and offer pretty much everything else for free. Obviously there would have to be some paid tier if you really wanted 10TB of storage or something, but very few people want that right now. We're still just getting started. Of course to achieve our goal, we'll also have to find a way to distinguish communities - which we'll…
Thank you, thank you, thank you.
Re: Keybase launches encrypted Git
#144My first initial gut thought is, could this be as a good ol cross platform method of password management? I've never been able to properly manage keepass due to syncing between different platforms being a pain.
Re: Keybase launches encrypted Git
#145In case you're wondering... > ~ Anticipated q's ~ > What if we're living in a simulation? > Keybase offers no guarantees against sophisticated side-channel attacks by higher-level entities.
It appears that this may no longer be an open question: http://www.pbs.org/wgbh/nova/next/physics/physicists-confirm... There was a Hacker News post about this a few days ago, likely from a different source, but I can't find it.
Re: Keybase launches encrypted Git
#146Should be the epitaph of the current era of computing.
Re: Keybase launches encrypted Git
#147Earlier quoted context omitted.
Putting up a fake sales page isn't a sales strategy and wouldn't prove anything. If anything, it could add to the distraction. Sales and being around long term are more complicated and won't simply be proven to you because it's what you want. It requires more vision and coherence than that.
It doesn't have to be a fake page, talking about a mvp where they can gauge who is interested in paying and what their problems are so they can concentrate in those areas. When confident they could even setup a simple paypal re-occuring sale system too.
It could be an option when you log in to the UI. I wouldn't mind it, as long as it isn't being e-mailed to me every week/month.
Re: Keybase launches encrypted Git
#148Re: Keybase launches encrypted Git
#149Re: Keybase launches encrypted Git
#150Keybase, please just support web of trust already. In some way. Not everyone I want to be able to authenticate necessarily has public social media accounts.
#1. Host a file on your site
You can host a text file, such as yoursite.com/keybase.txt. This is preferred, if you have a website.
#2. Set a DNS TXT record
Instead of hosting a web page, you can place a keybase proof in your DNS records.