macOS: Why /Volumes (or / root) and not ~/ User's home?

First of all, this `/keybase` folder 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/` 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 `/keybase` at 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?

The issue concerns the macOS client's mount location, but names no file, test, or entry point. Start by locating the code that chooses /Volumes/Keybase and creates the /keybase symlink, then establish whether mounting at ~/keybase is supported; done means the behavior or its rationale is clearly documented.

Written by the indexing model from the issue text.