Please, it's the standard location.
Also, Keybase cannot mount if the user already has a folder named /keybase. See log:
c8415a0342b70365ddfb6a1c
We'd like KBFS paths to be shareable (e.g. in scripts) between Linux and macOS, so using a place that is only standard on the Mac wouldn't work for us.
@cjb But what about working for the community?
👍 from me to use the standard place to mount filesystems on Mac OS: /Volumes.
@cjb What about automatically adding a symlink /Volumes/keybase → keybase? 😃
I was also quite surprised to have a mount point of /.
@MattiSG Ah, maybe try it and let us know how it works?
Great idea from @MattiSG about the symlink!
I'd like to expand that idea and suggest that to me it would make more sense to mount KBFS in the OS directory of choice (/mnt/keybase on Linux, /Volumes/keybase on Mac) and create a symlink of /keybase to provide the common cross-platform KBFS location?
I agree that compliance should come first, and convenience second. Both are crucial to adoption, but let's make that symlink a nicety to users and hard links an unambiguous point for the system (should especially come in handy for system upgraders).
I'd be in favor of a system-specific prefix for the keybase mount point, and a /keybase symlink pointing to the proper mount point for portability.
Most helpful comment
I agree that compliance should come first, and convenience second. Both are crucial to adoption, but let's make that symlink a nicety to users and hard links an unambiguous point for the system (should especially come in handy for system upgraders).
I'd be in favor of a system-specific prefix for the
keybasemount point, and a/keybasesymlink pointing to the proper mount point for portability.