Oh cool - wasn't really expecting to see this one on HN! The changes here are all a result of "iterating" on our product. Since we work in cryptography, it's not usually the case we can move fast. But this mini-blog post outlined some quick changes we could make. Stuff we learned from testers: (1) In many ways, Keybase's chat is like Slack (except encrypted!), but unlike Slack, our user database is public and connect…
While this was an iteration, you nailed a feature I really need with open teams -- I was about to start looking at Slack or Discourse because I'm in need of that right now. And the team management interface will be very pleasant -- I don't have to add people to my private teams often enough that I can ever remember the exact command-line without using "--help" (that's not a knock to your CLI; it's way more intuitive than a lot of the tools I use).
Thanks, so much, for this product and the support that the team provides. I ran into an issue over the summer that affected Windows 10 Insider Fast Channel builds. It ended up being Dokany, not keybase, but your team was as involved as the folks were over there and you were the only Dokany down-stream that provided any help in resolving the problem. Having been in this industry longer than I'd care to admit, I've come to expect that support tends to have no correlation to the price paid for the product, but I fully expect "free" to mean "good luck" (though, paid often means the same thing)[0]. Your team treated it with urgency and was friendly to boot (a characteristic that can be rare in software development but is virtually non-existent in the crypto- space). Love it -- and you have the dubious honor of being the first thing that I install afte I load/reload a Windows / Linux machine/VM.
[0] And couple that with the fact that I was running Insider Preview builds ... I'd have probably thought "well, what did you expect?!"