Proton Drive through Proton Unlimited. I have my e-mail setup through Proton already, so the plan was going to be to consolidate, and use Proton for cloud storage as well. I have since downgraded back to Mail Plus. The reason being a pretty bad experience with Drive.
I honestly don't remember the fine-grained details, sorry, but it had something to do with waking up one morning to my remaining storage being consumed by every file in Drive being duplicated, with a title "(overwritten 21h4m)" or something like that appended to each one.
I can't remember what caused it, but what I do remember is that there was no way to remediate it through the Drive app itself. Meaning, if I wanted to return my drive back to its original state, I would be burning my own time to write the script to do it, or I would be burning my own time to research some other solution. I couldn't believe the feature was shipped in that state.
In my opinion, if there exists a feature that leads to all of my files being duplicated, then it shouldn't be released unless there has been thorough testing against that feature's ability to remediate the fubarred status that it has enacted to "protect" my files. In this case, I think the feature was version history.
So the three conclusions I could come to were that there was little to no testing, inexperienced engineers, or a project manager that isn't managing the project particularly well. In any case, I don't want to feel like I'm beta testing features with my most important files, so I went back to Dropbox and its more mature app. Haven't looked back since.
I honestly don't remember the fine-grained details, sorry, but it had something to do with waking up one morning to my remaining storage being consumed by every file in Drive being duplicated, with a title "(overwritten 21h4m)" or something like that appended to each one.
I can't remember what caused it, but what I do remember is that there was no way to remediate it through the Drive app itself. Meaning, if I wanted to return my drive back to its original state, I would be burning my own time to write the script to do it, or I would be burning my own time to research some other solution. I couldn't believe the feature was shipped in that state.
In my opinion, if there exists a feature that leads to all of my files being duplicated, then it shouldn't be released unless there has been thorough testing against that feature's ability to remediate the fubarred status that it has enacted to "protect" my files. In this case, I think the feature was version history.
So the three conclusions I could come to were that there was little to no testing, inexperienced engineers, or a project manager that isn't managing the project particularly well. In any case, I don't want to feel like I'm beta testing features with my most important files, so I went back to Dropbox and its more mature app. Haven't looked back since.