Borg is definitely not the holy grail of backups, unless one has very loose requirements. Desktop backup solutions have typically a set of functionalities to c

Borg is definitely not the holy grail of backups, unless one has very loose requirements. Desktop backup solutions have typically a set of functionalities to compare against (block-based, safe on untrusted repositories, with realtime backup, compression-efficient, and optionally, with a functional GUI), that show how open source solutions are strangely lacking, each in a way or another. > produces remotely encrypted backups that the provider has zero insight into. If you're implying an untrusted repository, this is not entirely correct. From https://borgbackup.readthedocs.io/en/stable/internals/security.html https://borgbackup.readthedocs.io/en/stable/internals/securi...: > in a multiple-client scenario a repository can trick a client into reusing counter values by ignoring counter reservations and replaying the manifest The last discussion on HN was actually significantly more critical: https://news.ycombinator.com/item?id=18952839 https://news.ycombinator.com/item?id=18952839. Borg also has no efficient compression, as it doesn't use multithreading. There are multiple GitHub issues on this subject; I've just checked, and they're closed.