rclone: Improve native rclone backend support: hashes, modtimes, and server-side copy/move

[r3nor]

Hi,

Thanks for adding native rclone support for Internxt Drive. I am not sure if this is the right place for this issue, but the rclone repos do not allow opening issues.

I’m using the native internxt backend with rclone, and there are a few missing features that make synchronization and versioned backups much harder than they need to be.

From rclone backend features <remote>, the backend currently exposes:

• Hashes: []
• unusable modtime precision
• Copy: false
• Move: false

In practice, this means:

1. No checksum-based sync/bisync

   • rclone bisync cannot safely use --checksum
   • we are forced to fall back to --size-only, which is less safe..

2. Modtime is not usable for reliable comparisons

   • this makes sync logic weaker

3. --backup-dir cannot be used

   • because server-side copy/move is not supported
   • this prevents an easy “sync + keep remote versions of deleted/overwritten files” workflow

Requested improvements

1. Expose file hashes

Please support at least one standard file hash through the native rclone backend, for example:

• SHA-256
• MD5

This would allow reliable checksum-based sync and bisync.

2. Expose accurate modification times

Please provide usable file modtimes with normal precision.

This would improve sync correctness and reduce the need for size-only comparisons.

3. Support server-side copy and move

Please add support for:

• server-side copy
• server-side move

This would enable useful rclone workflows such as:

• --backup-dir
• efficient remote-side version retention
• faster reorganizations without re-uploading data

Nice-to-have improvements

These would also help a lot:

• recursive listing support (ListR)
• better metadata support where possible
• documentation specifically covering limitations of the native backend vs other rclone backends

Why this matters

Right now, users who want:

• reliable bidirectional sync
• safe change detection
• versioned backups
• efficient remote-side operations

have to use workarounds or give up features that rclone normally provides on more complete backends.

Improving hash support, modtimes, and copy/move would make Internxt’s native rclone support much more practical for real-world backup and sync workflows.

Thanks!