TIL that the directories that `snapd` binds are just hard-coded, right in the guts of the thing

https://github.com/canonical/snapd/blob/aad0536a921429dd7759f9654ea7503fc4f6a875/cmd/snap-confine/mount-support.c#L935-L950

snapd/cmd/snap-confine/mount-support.c at aad0536a921429dd7759f9654ea7503fc4f6a875 · canonical/snapd

The snapd and snap tools enable systems to work with .snap files. - canonical/snapd

GitHub
"no user would ever want to access files in other places than these" - apparently, some number of people at canonical
user programs only rarely need access to files except in these specific places
copying every fucking file that I might want to share on Slack from my NAS into my Downloads directory *first*, to appease the petulant god-child `snapd`

@SnoopJ
I literally moved my home directory because using Ubuntu is advantageous for my job (vs any other distro), and snaps/apparmor cannot handle the possibility that a home directory is anywhere other than `/home/`

I'm not un-generous feeling towards the Canonical people. Packaging and distribution are hard. But this is relatively important stuff if you want the project to be taken seriously.

To me, snaps are about as important as upstart (read: I look forward to it being dead).