Open Max-7 opened 2 weeks ago
@touilleMan suggests that security should also be taken into account when thinking about a solution: having many workspaces mounted by default could unnecessary expose sensible data that the user does not need at a given time.
In this sense, we should think about how can Parsec help the user to reduce the perimeter of exposed data as a best practice.
We have discussed this many times, with some ideas that does not quite convince us.
V2 had a mount/unmount buttons, but this was hard to explain to users
One possibility will be to propose the same functions behind actions that have more sens to the user:
Parsec creates a single mountpoint and each workspace is mapped to a directory inside the mount point (/P/wksp1
, /P/wksp2
, etc.).
This solution is rather tricky but has been implemented in V2 (for Windows): https://github.com/Scille/parsec-cloud/issues/4668. It worked fine but had some limitations on such as the "read-only flag" who can only be set at mountpoint-level. That said, this should not be a problem for Linux (it should be possible to set read-only per directory).
Comparison with other solutions (such as Dropbox or Google Drive) are not very just: in Parsec, users do not have a single "data unit" that can be mounted in the OS. Instead, workspaces are "isolated data units" not shared by default between all users of the organization.
Linux treats Parsec mountpoints as any other mountpoints and file managers will tend to display them as other devices like usb drives, which can be annoying for a huge number of mountpoints.
Find a solution to hide them or display them as one.