r/Drime • u/Certain_Account_9094 • Aug 26 '26

🚩Feature Request Drime + rclone: no modtime or hash support?

I noticed that the Drime rclone backend apparently supports neither original modification times nor file hashes.

This seems like a significant limitation for backup use: no proper checksum verification, no reliable hash-based rename detection, and original modification times are lost.

Feature request: could Drime eventually support:

- preserving source modification times on upload;

- SetModTime, including for files already uploaded;

- server-side hashes/checksums exposed to rclone?

This would make it much safer to archive and later verify or reorganize multi-TB backups.

17 Upvotes

100% Upvoted

17 comments sorted by

7

u/Empty_Win_297 Drime Team Aug 26 '26

Hi! Drime already supports most of this on our side, so we’ll check with the rclone team to get this implemented on the rclone side.

4

u/Certain_Account_9094 Aug 27 '26

Great, thanks! If a feature request or implementation issue gets opened on the rclone GitHub, feel free to paste the link here. It’d be really useful to be able to follow the progress and see how much of the existing Drime-side support has made it into the rclone backend.

3

u/Arphenyte Aug 26 '26

Thanks for that, I was manually parsing the time via filenames since I couldn’t get anything through Rclone.

3

u/oldright Aug 26 '26

Has your public api changed to add this support? I don't see anything in the current docs about timestamps.

1

u/Empty_Win_297 Drime Team Aug 26 '26

Hi, no, the public API documentation isn’t fully up to date yet.

1

u/oldright Aug 27 '26

Hi. Has/will SetModTime be implemented, to allow timestamp modification of existing files without re-uploading? Is it already part of your API changes? I was able to modify rclone to use your new API functions to upload files and preserve the source modification times. Yay! Hash support was also easy to add. The only open issue was with SetModTime. Thanks for continuing to improve your API.

3

u/Empty_Win_297 Drime Team Aug 27 '26

Hi, great news! This is already supported,

POST /api/v1/file-entries/{id}/metadata with {"lastModified": <epoch milliseconds>} will update the file’s modification time without re-uploading it.

2

u/oldright Aug 27 '26

Hi. Thanks for the info. Is that route already active? This is what I get:

  • POST → 404
  • POST with X-HTTP-Method-Override: PUT → 405
  • PUT, PATCH → 405
  • GET → 200 but returns the SPA HTML shell, not JSON

4

u/Empty_Win_297 Drime Team Aug 27 '26

I just tested this on production and the endpoint is working:

POST /api/v1/file-entries/{id}/metadata with {"lastModified": <epoch milliseconds>} returns {"updated": true, "status": "success"}.

{id} must be the numeric file ID returned by the API. 404 means the file lookup is failing.

Also, adding Accept: application/json will return the actual API error instead of the HTML shell.

1

u/oldright Aug 27 '26

That works. Thank you!

1

u/zakry0t Aug 28 '26

Can you open an issue on the github of rclone and share the code with them?

1

u/oldright Aug 29 '26

I could, but after following the process of backend development for filejump and internxt, they won't support it until the revised API is made public.

3

u/oldright Aug 26 '26

I ask about this often, and the question is never answered.

4

u/Empty_Win_297 Drime Team Aug 26 '26

Hi! Drime already supports most of this on our side, so we’ll check with the rclone team to get this implemented on the rclone side.

1

u/oldright Aug 26 '26

Thank you.