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 snap is truly a marvel of engineering. they truly took the design brief, which I assume was "what if flatpak, but it *never* works" and absolutely crushed the implementation
@glyph "engineering" is a very strong word to use here
@glyph @SnoopJ
And don't forget all the loop devices you can eat. At least until the directory fills up or you run out of inodes. fdisk is now an adventure game!