Mylio also doesn’t overwrite files in-place. We will move the old file to the Recycle Bin first, then copy in the new file. That means if a file is being overwritten, you will still have older copies on all of your other devices for some time (often years).
We do have a mechanism though that we use for Office docs which is to save off previous versions of a file into a “older versions” folder before we replace them, and then in the details panel you can get to each of the older versions and inspect them. (This is a local folder and not replicated - so not subject to a URE propagation.) This is more permanent compared to the recycle bin, but of course documents are a lot smaller than pictures. But I could maybe optionally enable a mechanism like this for photos if that sounds interesting? This won’t really work for a workflow if you very often modify photos outside Mylio since each edit/save will create a copy, but it does work for other workflows.
Thanks for the quick reply! The “Recycle Bin” you refer to is the system’s trash folder, right? I don’t fully understand the first paragraph here. If a file is overwritten (by Mylio)… in what cases, what operations does Mylio overwrite images? Edits are non-destructive, so… what do you refer to?
Then the old file is put into the trash, but the old file remains in other devices?
I understand and agree that versioning Office type document files makes sense. Versioning images would eat up a lot of storage over time, but it would be definitely a useful optional feature for people who have enough space to burn (at least on my NAS vault, not my iPad…). Perhaps it would be a good compromise to allow versioning of the X most recent versions of images? Mylio could possibly present a statistic of currently versioned images and how much space they take. The user could define a number of versions in preferences, like, from 0-9 or such.