Earlier quoted context omitted.
> As for collisions, a "conflict" is handled as you would expect on file syncing services I'm not sure what to expect though. Does it rename subsequent files by appending _##? Or does it overwrite? Or does it allow 2 files with identical filenames, like Google Drive (at least on the web) does?
Oh I see, sorry for not fully answering. Keybase does not merge files or anything source-control like that. In fact, if that's what you want, you can actually init a bare repo inside of Keybase and clone into and out of it. We do this all the time as we're dogfooding. It's cool that every push is signed automatically, and every pull or clone is verified. The conflict resolution Keybase does do is simple and much like…
Introducing the Keybase filesystem
331–340 of 501 posts
Re: Introducing the Keybase filesystem
#332Re: Introducing the Keybase filesystem
#333About 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…
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
Re: Introducing the Keybase filesystem
#334Re: Introducing the Keybase filesystem
#335Re: Introducing the Keybase filesystem
#336Re: Introducing the Keybase filesystem
#337Earlier 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
Is it JavaScript crypto you don't trust, or in-browser crypto you don't trust?
Re: Introducing the Keybase filesystem
#338Please either reply with an email address or have one visible in your profile if you want one.
Re: Introducing the Keybase filesystem
#339Just was granted 5 more invites (Thanks Chris!) if anyone else is late to the party. Please either reply with an email address or have one visible in your profile if you want one.
Edit: Thanks a lot for the invite !