Keybase launches encrypted Git
Keybase team member here.  Interesting fact: git doesn&#x27;t check the validity of sha-1 hashes in your commit history. Meaning if someone compromises your hosted origin, they can quietly compromise your history. So even the fears about data leaks aside, this is a big win for safety.<p>From an entrepreneurial perspective, this is my favorite thing we&#x27;ve done at Keybase. It pushes all the buttons: (1) it&#x27;s relatively simple, (2) it&#x27;s filling a void, (3) it&#x27;s powered by all our existing tech, and (4) it doesn&#x27;t complicate our product.  What I mean by point 4 is that it adds very little extra UX and doesn&#x27;t change any of the rest of the app. If you don&#x27;t use git, cool. If you do, it&#x27;s there for you.<p>What void does this fill?  Previously, I managed some solo repositories of private data in a closet in my apartment. Who does that? It required a mess: uptime of a computer, a good link, and  dynamic dns. And even then, I never could break over the hurdle of setting up team repositories with safe credential management...like for any kind of collaboration.  With this simple screen, you can grab 5 friends, make a repo in a minute, and all start working on it. With much better data safety than most people can achieve on their own.