Hey, I really like the application, but I often feel the need to display not the maximum amount of space a directory/file has consumed in a snapshot, but instead the amount of data that was aggregated in the different snapshots for that directory/file.
For example (but not limited to that use case, I have multiple) I have a backup of my personal PC. There I have configured a bunch of exclude rules for the different applications caches, but I have missed some smaller cache directories. Some of these applications write ~30MB of data in each and every backup, which adds up quite a lot, but is barely detectable with the current feature set, as this directory will never get bigger that these ~30MB.
I have thought about implementing this feature myself, but I'm not even that sure, how to tackle that from a technical perspective, as that would probably require to count the data blobs themself to check after the de-duplication? And to do that in a manner, that could be speed up using a cache would also help immensely, as the rest of the application is doing.
Hey, I really like the application, but I often feel the need to display not the maximum amount of space a directory/file has consumed in a snapshot, but instead the amount of data that was aggregated in the different snapshots for that directory/file.
For example (but not limited to that use case, I have multiple) I have a backup of my personal PC. There I have configured a bunch of exclude rules for the different applications caches, but I have missed some smaller cache directories. Some of these applications write ~30MB of data in each and every backup, which adds up quite a lot, but is barely detectable with the current feature set, as this directory will never get bigger that these ~30MB.
I have thought about implementing this feature myself, but I'm not even that sure, how to tackle that from a technical perspective, as that would probably require to count the data blobs themself to check after the de-duplication? And to do that in a manner, that could be speed up using a cache would also help immensely, as the rest of the application is doing.