The history of files on google disk is not stored when using encryption
Posted: Fri Dec 02, 2022 9:07 pm
I want to use history of encrypted files when using Google disk folder in Syncovery.
But, for example, if I create a file TestFile.txt with the contents "123", then I get a file TestFile.txt.s3.zip
If I change the contents of the file to "124", then Syncovery will modify the existing file TestFile.txt.s3.zip and Google disk recognizes this operation as a change in the file. So, the history of the file modification will remain in Google disk. And this is the behavior that you expect from program.
But, if I change the contents of the file TestFile.txt to "1235", then Syncovery
will create a new file TestFile.txt.s4.zip and
delete the old file TestFile.txt.s3.zip.
So, the history of changes in Google disk in this case will be lost.
Depending on the contents of the changed file - the history of the modification of files on Google disk is stored or not. This behavior of the program brings confusion. I cannot distinguish a deleted file in a Trash from file, which is just a version of a modified file.
But, for example, if I create a file TestFile.txt with the contents "123", then I get a file TestFile.txt.s3.zip
If I change the contents of the file to "124", then Syncovery will modify the existing file TestFile.txt.s3.zip and Google disk recognizes this operation as a change in the file. So, the history of the file modification will remain in Google disk. And this is the behavior that you expect from program.
But, if I change the contents of the file TestFile.txt to "1235", then Syncovery
will create a new file TestFile.txt.s4.zip and
delete the old file TestFile.txt.s3.zip.
So, the history of changes in Google disk in this case will be lost.
Depending on the contents of the changed file - the history of the modification of files on Google disk is stored or not. This behavior of the program brings confusion. I cannot distinguish a deleted file in a Trash from file, which is just a version of a modified file.