strib
commented
6 years ago We originally planned on making it ~/keybase, but it turns out to be a really bad idea because it means that backup software that crawls your home directory, or commands like du that users often run in their home directory, end up getting hosed because it starts crawling not only your private data, but the entire contents of the public and team folders you might have previously visited. /Volumes seemed like the safest, semi-standard place to put it.
We expect most people will continue to access it via the /keybase global path, which lets you share paths between Linux and macOS users.
First of all, this
/keybasefolder share has been awesome. Awkward, but awesome. I've used it with several private and team members and I am building up a public version with a number of items to share. It's awkward as accessing a root folder for a personal share seems weird. Everything on my machine is within my/Users/<username>directory. However, keybase is in the/root system? I know it was in beta and subject to change. So we waited...Now I just received an update to the macOS client, and the mount has been moved to
/Volumes, and softlinks created for the previous root location of/keybase.That a little better than root
/keybase, but now requires I supply an Admin password to mount in/Volumes/Keybase(and now the directory is a capital "K" instead of lowercase "k", like previous muscle memory is used to).One question: Why have it in
/Volumes/Keybase, or root/keybaseat all? Why can't we have it in our home~/directory like Box and other sync tools?E.g.
~/keybase?I know Google Drive mounts in /Volumes`, which is annoying. I'm hoping that wasn't the only reason?