fidelity_controllable_compression VS BorgBackup

Ok. I tried compressing an image of waldo as far as I could (using this neural network) and searching for it in PI. Couldn't find it in the first 1 billion digits in hexadecimal (I actually couldn't find much much smaller sequences as well. 1 billion is simply not enough digits). I think I'm done for the night, if someone has an idea how to get a few trillions of digits of PI in binary/hexadecimal - I'm listening. For what it's worth, here's the smallest representation of waldo's face in binary I could create (at 728 bytes, I'm sure a smaller image can be created with some effort) -

i use - and recommend - "borgbackup": for example with the "vorta" graphical frontend

* https://www.borgbackup.org/

* https://vorta.borgbase.com/install/windows/

just my 0.02€

I used this many, many years ago but switched to Borg[0] about five years ago. Duplicity required full backups with incremental deltas, which meant my backups ended up using too much disk space. Borg lets you prune older backups at will, because of chunk tracking and deduplication there is no such thing as an incremental backup.

[0] https://www.borgbackup.org/

Currently, I'm auto-backing it up with borg (push mode) through wireguard tunnel to NAS behind ISP's CGNAT. The borg takes care of deduplication in SQL file, so incremental update (even in append-only mode) is very small for PostgreSQL dump.

Borg 2 has been in development for nearly a year and a half [1] and may probably be released early next year, i.e., early 2024 (just a guess, seeing that even RC1 is not yet released and seems to have a lot of work to be done).

Does anyone know how Borg 1.x and 2 would compare to Kopia?

[1]: https://github.com/borgbackup/borg/issues/6602

You could use borgbackup.