Nick S. Knutov

@CrazyCoder what's about support for Kindle Voyage now?

What is the current state of this issue? With `borg create --compression auto,zstd,3` on modern hardware (ssd) backup process speed is limited by speed of one cpu core. And it...

Just checked now, with 1.1.17 it also does not work.

@ThomasWaldmann looks great! Will it be released in 1.2 branch?

``` borg recreate --compression auto,zstd,3 -svp --show-rc \ --exclude '*/backup/*.tar.*' \ --exclude '*/*cache/*' \ --exclude '*includes/sessions/sess*' \ --exclude '*livestreet_cache*' \ --exclude '*cache/dbcache*' \ --exclude-caches --exclude-if-present '.nobackup' \ --recompress if-different \...

I'm not sure how it is done internally, but why it should process all snapshots as files instead of recompress chunks as chunks? So it can be only two passes:...

> The next time it looks at it In case of big repos, it takes too much time and it looks like it process it somehow every time. I thought...

ok, so, as far as I understand now it should be enough only single pass of reads chunks from disk if I do only recompress, correct? But with ``` borg...

More thoughts about how it can be better: 1) borg can create index of what must be changed - first pass of reading from disk 2) borg can filter+recompress chunks...

just as an idea - why not to skip support for latin1 and other non-unicode terminals now? latin1 symbols inside utf8 will look the same on latin1 terminal I suppose....