The times I see in Google Drive are the times it receives the files the source server.
I clarified my understanding to realise the modified dates are preserved (my apologies), however Drive seems to be creating it’s own creation dates since they happen to be non-exist with all files/folders on the server. That’s not a major issue as long as they can be the same as ‘modified’.
Speaking of such, transferring folders (the bulk of my rclone copy work) requires that I recreate the directory on the remote end. Doing so means that the modified time is not the same as the source. Is there really not a means to just copy a directory with rclone, thereby preserving all dates as is?
I then double-checked dates when I download files/folders from Drive to find the modified date is even stripped so the files are dated at the time of download (via browser). Downloading files FTP direct preserves the dates (making the blank ‘create’ equal to modified), yet I did ensure both my clients (FileZilla & Cyberduck) preserved them, and they apparently do for uploads (untested by myself).
I think I have gaps in my understanding of all the technologies here than a limitation of rclone? Google Drive isn’t a service I’ll be using forever of-course, so it’s important the dates aren’t stripped/manipulated inbetween systems. rClone is a godsend, even if I can’t get the dates right
If we transfer data using Google Drive file steam the dates of files and folders are preserved but not with Rclone. I wonder if they have opened up something new in the API since and maybe third party products like Rclone could take advantage?