-
-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep modification date of original file #239
Comments
This comment has been minimized.
This comment has been minimized.
Thanks for this report. There is already a related issue in our iOS-repo which provides some more information about the difficulties, see cryptomator/cryptomator-ios#26 TLDR; This will be a Cloud-API specific implementation because not all APIs does support setting the creation/modification date. |
@SailReal at the moment which Cloud-API provides this feature? |
@JustFanta01 currently this is not implemented for any cloud. Or was the question for which cloud it is possible to implement? |
@SailReal Yes, I meant the second question. |
Sorry for the late response. This should be possible to implement for
Clouds that do not support providing the modification date @JustFanta01 are you willing to implement it? |
@mawi675lr81 @Chistex @woolclew @ghost @zwentastic @sjgriffiths @wu4339 @emilsenan @philthynz @uhLydn @myns23 @joelcieslar @jwsp1 @serialpotato @a-rekkusu @Shihabus-Sakib-Rad @T81 @MTH607 @LearningAsIGo71 @skariko @iam0day @eylenburg Hi everyone, you are all the people who have commented or opened issues about the implementation of two fundamental features in my opinion:
Since they are not in the priorities of the developers, I ask you if, in the name of the open source philosophy, can we (or by asking acquaintances/friends) be able to implement these features? Obviously for the first point it would be possible to implement this feature only for the clouds that support it but better than nothing. The closed source competitor (www.boxcryptor.com) already has these features, I have never written code in Kotlin but there's no way we can't implement them! |
Hey @SailReal 👋 This one is particularly useful when dealing with photos and the auto-upload. Three questions:
// [*] https://docs.pcloud.com/methods/file/uploadfile.html Thanks in advance |
Hi @SailReal, I don't know anything about android but I'm trying to implement this very important feature by myself. But I wanted to ask you for some advice because I don't know if it's feasible. |
Hi @JustFanta01, It would be really awesome if you could implement that! The best place to start is to have a look at #285, where @bpavot has already made a good start. IMO it should work like that. Feel free to ping me if you stuck somewhere or need some input. |
Fixed in #528 |
Description
After uploading a file into a cryptomator tresor the timestamp of the file is set to the current timestamp. For uploading I use the Add-button (+) in the cryptomator app.
System Setup
Steps to Reproduce
and
Expected Behavior
File is shown with the origin timestamp of the file.
Actual Behavior
File is shown with the current timestamp.
Reproducibility
Always
Additional Information
I use a webdav connection from strato hidrive.
With the original app from strato it works like expected: After uploading a file into the the hidrive cloud (without cryptomator) the origin timestamp is used.
The same applies when a file is exported to the local storage of the device. If possible, the modification date should be preserved.
The text was updated successfully, but these errors were encountered: