TW
@jungle-boogie for distribution (in the debian / fedora / ... sense) it matters whether zstd is available as package there (we can't just pull it via pip and compile it)....
moved from suggestion by @infectormp in #45: alternative to zlib from Apple LZFSE - https://www.infoq.com/news/2016/07/apple-lzfse-lossless-opensource
@sjuxax forking an external program is expensive, esp. if you have small data sizes. borg compresses chunks (~2MB for big files, or as small as the file is for smaller...
@enkore I'ld put it into 1.3. We can do it earlier in case we get bored. Yes, guess that a mandatory flag for read. And the manifest better does not...
Put it into 1.3, so we have it on the radar. Maybe we can also do it earlier, let's see.
About zstd: I am working on an updated PR #3411 based on @willyvmm's work in PR #3116, addressing some of my own feedback from back then.
zstd support is now in master branch (#3411) and a 1.1 backport is pending (#3442).
zstd support in borg was released with 1.1.4.
@henfri yeah, I also noticed that - it was there before we actually implemented that.
Why do you think so? lz4 is quite good for high speed, while zstd covers a wide range of compression ratios with good speed. We don't need to add anything...