[Cyberduck-trac] [Cyberduck] #11783: Mountain Duck last modified date retention S3

[Cyberduck]

#11783: Mountain Duck last modified date retention S3
--------------------------------+--------------------------
 Reporter:  wanderer            |         Owner:
     Type:  enhancement         |        Status:  closed
 Priority:  normal              |     Milestone:
Component:  s3                  |       Version:  7.10.2
 Severity:  normal              |    Resolution:  duplicate
 Keywords:  last modified date  |  Architecture:  Intel
 Platform:  Windows 10          |
--------------------------------+--------------------------

Comment (by wanderer):

 Three years ago, in ticket #10381 (https://trac.cyberduck.io/ticket/10381)
 you, @dkocher, deemed this issue important enough to put date modification
 retention into the following release of Mountain Duck 2.6.0. S3 not having
 the native ability to date retain has received a good deal of attention
 (https://forums.aws.amazon.com/thread.jspa?messageID=738308). Other
 software such as S3 Browser, Rclone, and MSP Cloudberry write metadata
 that retains this last modified date so it can be compared on a sync to
 other data sets and allows a restore or download to a file system to
 retain that aspect of the file. Your software incorporates this option for
 other storage systems besides S3. Why not allow the user the option for S3
 knowing it would degrade performance? I would certainly utilize software
 that transferred at half the speed for full functionality. It'd be similar
 to an Internet Service Provider saying we provide 80% of the internet at
 double the speed. I'd go for the slower ISP. Understand some users may not
 care that their file dates change upon upload with your software, but
 there are many that do.

--
Ticket URL: <https://trac.cyberduck.io/ticket/11783#comment:2>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows