Ben
My feedback
27 results found
-
16 votes
An error occurred while saving the comment Ben
supported this idea
·
-
417 votesBen
supported this idea
·
-
2 votesBen
shared this idea
·
-
3 votesBen
shared this idea
·
-
5 votesBen
supported this idea
·
-
604 votesBen
supported this idea
·
-
41 votesBen
supported this idea
·
-
143 votesBen
supported this idea
·
-
1,487 votesBen
supported this idea
·
-
14 votesBen
supported this idea
·
-
32 votesBen
supported this idea
·
-
2,101 votesBen
supported this idea
·
-
1,164 votesBen
supported this idea
·
-
32 votesBen
supported this idea
·
-
2,028 votesBen
supported this idea
·
-
100 votesBen
supported this idea
·
-
26 votesBen
shared this idea
·
-
569 votesBen
supported this idea
·
-
2,910 votes
Proton and Standard Notes are joining forces: https://proton.me/blog/proton-standard-notes-join-forces
Ben
supported this idea
·
-
3,929 votesBen
supported this idea
·
*Feature request*
Please add a setting that lets the user choose where Proton Drive's macOS cache and/or mount root lives — for example, a folder on an external volume rather than the system disk.
*Background*
The macOS Proton Drive client uses Apple's File Provider framework. This forces both the visible mount (~/Library/CloudStorage/ProtonDrive-…-folder) and the underlying blob cache (/private/var/folders/<hash>/T/com.apple.fileprovider.ffp/…) onto the boot volume, with no documented way for the user to relocate either.
*Why this matters*
For users on Macs with a small internal SSD and a large external drive for media, documents, and archives, this is a hard blocker. Every file synced to Proton is duplicated locally as cache on the internal disk, so the practical sync ceiling is "whatever fits on your boot volume" — not "whatever you have on the external drive you actually store data on."
iCloud Drive, Dropbox, and OneDrive all have the same limitation because of Apple's File Provider design. Proton has an opportunity to differentiate by offering control here, which would directly benefit users with external-storage-based workflows (creatives, developers, archivists).