Describe the bug

We are using rclone for archiving of large amounts of data and have users browse the archive either with a cli tool or with Cyberduck. We use that special profile called s3 (timestamps) that is supposed to show posix mtime metadata instead of the S3 object creation time using s3.listing.metadata.enable=true . If you are archiving a file that is 5 years old, the object creation time is less relevant and users want to see when the file was last modified (in fact many users do not understand the object time at all)

Unfortunately, there seems to be an issue with the correct display of mtime metadata. When I check https://www.unixtimestamp.com/ for that number in mtime I get April 20th 2023 which is correct but Cyberduck with S3 (timestamps) profile shows a time in 1970

The timestamps were created with Rclone but that is perhaps less relevant since Unix time is clearly defined as seconds since 1/1/1970 and it may be a float if you want to include milli or nanoseconds.

Also, it would be lovely if the timestamp listing could be a simple option in the S3 preferences instead of having to go the detour through the profile settings (I realize there is an additional head request for each object required but the slower performance is not issue for us)

Desktop (please complete the following information):

• OS: Windows 11
• Version [e.g. 8.5.9]