2 ms·
You're wrong. The obsidian flatpak ships by default with access to /home. https://github.com/flathub/md.obsidian.Obsidian/blob/5e594a4dc925b3edd928dd2ce6d9899b
by s_ting765 1y ago
You're wrong. The obsidian flatpak ships by default with access to /home.
https://github.com/flathub/md.obsidian.Obsidian/blob/5e594a4dc925b3edd928dd2ce6d9899b477e551f/md.obsidian.Obsidian.yml#L20 https://github.com/flathub/md.obsidian.Obsidian/blob/5e594a4...
- TomaszZielinski 1y agoI „love” such sandboxing defaults. Apps like Docker Desktop also share the whole home by default [1], which is pretty interesting if a big selling point is to keep stuff separated. No idea why node_packages need to have access to my tax returns :). Of course you can change that, but I bet many users keeps the default paths intact. [1] https://docs.docker.com/desktop/settings-and-maintenance/settings/ https://docs.docker.com/desktop/settings-and-maintenance/set...
- eli 1y agoNeeded for volume mounting to work easily I assume.
- TomaszZielinski 1y agoYeah, I forgot there’s the intermediate VM level, and user folders are shared there so that folders could be mounted to the individual containers using host paths.
- esseph 1y agoInteresting, I thought I had to turn that on for Obsidian! The first time I started installing flatpaks I ran into a bit of permission / device isolation trouble and ever since then, I use flatseal after installing an app to make sure it actually has access to things. I guess I misremembered in the case of Obsidian.