Grorge
My feedback
15 results found
-
6 votesGrorge
supported this idea
·
-
37 votesGrorge
supported this idea
·
-
48 votesGrorge
supported this idea
·
-
20 votesGrorge
supported this idea
·
-
220 votesGrorge
supported this idea
·
-
249 votesGrorge
supported this idea
·
-
292 votesGrorge
supported this idea
·
-
294 votesGrorge
supported this idea
·
-
685 votesGrorge
supported this idea
·
-
704 votesGrorge
supported this idea
·
-
1,088 votesGrorge
supported this idea
·
-
2,857 votesGrorge
supported this idea
·
-
206 votesGrorge
supported this idea
·
An error occurred while saving the comment -
24 votesGrorge
supported this idea
·
-
103 votesGrorge
supported this idea
·
I don't think I am adding anything new here, everything below has already been mentioned by multiple other users in this thread. I am merely trying to present a consolidated view on how I would imagine this to work.
This, IMHO, is
a) critical and, one could argue, a likely barrier for people who want to adopt Proton,
b) goes beyond photos but should cover standard file storage and
c) goes beyond google but should cover other cloud storage services (Dropbox, OneDrive, Google Drive/Photos, iCloud Drive/Photos, Mega, pCloud, whatever, etc).
At the moment, there are two ways to transfer files from from a different service (let's call it "Source" to Proton Drive:
* Download, then re-upload
* Use a third intermediary direct cloud transfer service. Mixed opinions on the web, but some claim to work.
The former is slow, impractical, scales poorly for large volumes of files/photos, requires a fair bit of manual intervention and, generally speaking, a pain.
The latter requires allowing a third service provider to access files/photos so they can execute the transfer from Source to Proton (assuming it works in the first place). Which implicitly means trusting this third service provider with your data. Which is something I don't want to have to worry about.
What we need IMHO is a way for Proton Drive to use the "Source" cloud provider's APIs to import files / photos directly, not dissimilar to how Easy Switch works for mail, contacts, calendar.
I think we are looking at the following features:
* Support for multiple cloud providers. WIth the more widely used ones to be supported first (Google, iCloud, Dropbox, OneDrive, Mega, maybe pCloud would be my shortlist)
* Selective import. Users would be presented with an interface that would allow them to choose what to transfer (Directory, Album, Month or Year, Individual files/photos. As opposed to a "transfer everything" only function.
* For photos in particular, it would be great if metadata (date, album, location) could be preserved if at all possible.
* I am imagining a "one-off" model where a user initiates the transfer on demand, as opposed to automatic synching.
I was unable to find this on the roadmap.
I'd be adding multiple +++ votes here if I could.
Thank you for the consideration.