[Feature Request]: Auto-export file timestamps to CSV for Disaster Recovery on "dumb" clouds

[almadorus]

Hi, master Zenju!

I want to request a simple but powerful feature: an option to automatically export local file metadata (Paths, Created/Modified dates) to a CSV file right before synchronization starts. 

The Problem

Many budget cloud providers (such as TeraBox, cheap WebDAV, or object storage) do not preserve file timestamps via their APIs. They overwrite the ModTime with the current upload time. 

While sync.ffs_db perfectly handles this during daily Two-Way syncs, it completely fails during a Disaster Recovery scenario (when the local hard drive dies, and we pull data from scratch): 

1. To download files to a clean drive, the user must switch to Mirror/Update mode (Cloud → Local).
2. FFS downloads the files, but since the cloud has already ruined the timestamps, all recovered local files get corrupted dates (the dates of the cloud upload).
3. sync.ffs_db cannot restore original local OS timestamps in this direction. 

Proposed Solution

Add a native checkbox to generate a metadata blueprint (e.g., ffs_timestamps.csv) in the root directory before the sync begins. FFS would update this file and upload it to the cloud. 

If a local disaster happens, the user can download their files along with this CSV and use a tool (like Advanced Renamer) to easily restore the original Windows/Linux timestamps to the physical files. 

Why do this natively?

While users can technically script this via PowerShell macros `Before Synchronization`, a native cross-platform implementation (Windows/Mac/Linux) would make FreeFileSync a bulletproof disaster recovery tool for any storage medium, no matter how "dumb" the cloud provider is. 

Thank you for considering this request and for maintaining such incredible software!

[xCSxXenon]

This could be done with a batch script or PowerShell script as well, and is more likely than it being implemented in FFS