Another Great Proton User
My feedback
47 results found
-
137 votes
An error occurred while saving the comment Another Great Proton User
supported this idea
·
-
81 votesAnother Great Proton User
supported this idea
·
-
103 votesAnother Great Proton User
supported this idea
·
-
236 votesAnother Great Proton User
supported this idea
·
-
107 votesAnother Great Proton User
supported this idea
·
-
270 votesAnother Great Proton User
supported this idea
·
-
329 votesAnother Great Proton User
supported this idea
·
-
231 votesAnother Great Proton User
supported this idea
·
-
184 votesAnother Great Proton User
supported this idea
·
-
486 votesAnother Great Proton User
supported this idea
·
-
478 votesAnother Great Proton User
supported this idea
·
-
229 votesAnother Great Proton User
supported this idea
·
-
621 votesAnother Great Proton User
supported this idea
·
-
242 votesAnother Great Proton User
supported this idea
·
-
1,132 votesAnother Great Proton User
supported this idea
·
-
473 votesAnother Great Proton User
supported this idea
·
-
1,162 votesAnother Great Proton User
supported this idea
·
-
73 votesAnother Great Proton User
supported this idea
·
-
20 votesAnother Great Proton User
supported this idea
·
-
45 votesAnother Great Proton User
supported this idea
·
Maintaining the E2E encryption is more important to me than allowing rsync or rclone.
To me, a Drive bridge is a better idea than a direct API to my data. Maybe using a VPN-like structure from a local service to Proton. Then rsync or rclone could connect to localhost at an arbitrary port.
Of course, if you have an official bridge, that bridge could also have a sync option/setting so that the user would not need to drop to CLI and use a third app.