Modern OSes designate special locations to place application data, caches, and logs.
For example on macOS application data goes to Library/Application Data, logs go to Library/Logs and caches to Library/Caches. It’s a standard and expected system wide convention that other apps rely on. For example, Time Machine skips Logs and Caches folders.
Furthermore, transient data on macOS must be marked with a special extended attribute to prevent time machine from picking it up.
Today default installation of duplicacy-web does none of that: it dumps everything into a single hidden directory and does not mark anything for exclusion.
This, among other things, results in data loss: when turbulent stuff that does not need backed up gets backed up other, important data stays unprotected longer and due to limited space on the target drive results in version history shortening.
This is at least one easy to understand tangible reason for following OS guidelines. There are many more ways how duplicacy_web behaves and feels foreign on that OS.
Similar deal on Windows.
Can’t speak for other OSes.
With duplicacy_web users can fix those issues manually in settings and command line.
But for that users need to:
- understand their OS design.
- understand duplicacy design.
- know to do that in the first place.
Most therefore won’t do it. And even if 100% of them did — asking thousands of users to do work that can be fixed once in the app is of questionable utility.