Cris - 2026-02-22

Most backups use file time and file size being changed
to determine that a file was updated, and therefore to update a mirror.

This is reasonable behavior. Doing checksums is much more time consuming.

Now, I use a preallocated size for a veracrypt container.
Given the DEFAULT option: "Preserve modifications timestamp of file
containers"
in place...

I will get NO-MIRRORING of my container,
even if I DO change the contents.

I get why you do it. But it's a high price to pay (not having a backup) if
something goes wrong.

I think users have to.... at least be aware of the tradeoff.

Please make this option EXPLICIT, show a big warning somewhere.
Ask user to confirm it.

Because privacy is important, but backups are important as well.

The default behaviour is dangerous for backups and is 100% implicit/silent.

That said, thanks for the great product.
Thank you

 
alternate