Seafile 12.0’s API supports setting the file’s mtime during upload, but it seems that files uploaded through the web interface still cannot retain the original mtime. I would like to ask if Seafile will support retaining the mtime during web uploads in the future?
For uploading file via web interface, as far as I know, there is no way to determine the file’s real mtime. Setting mtime during uploading does not make sense.
It is possible to get mtime via frontend. I think setting the mtime is quite important when using third-party tools like rclone. Since Seafile does not implement features such as file hashing, we have to rely on mtime to assist synchronization tools (e.g., rclone) for more robust synchronization. If the behavior of uploading files via the web API differs from that of browser uploads, I am concerned that it might cause some synchronization conflicts. By the way, will Seafile provide file hash information in the future?
Seafile first break file into small blocks, the hash value of the each block is calculated and the list of hash value of the blocks will be hashed again and store as oid of a file.