Michael Eischer

I don't want to slow your enthusiasm, but I'm wondering whether some proper API would be better suited for your needs. Something like https://github.com/restic/restic/pull/4754 maybe? Introducing wildly different options to...

> Many unix commands support piped input so I'm curious if there's a useful way we can define that for `ls` but understand if that's not inline with restic's design...

> I think keeping the stdin format very simple e.g. simply a datafile that's compatible with essentially (cat containing a list of [strconv.Quote](https://pkg.go.dev/strconv#Quote) escaped strings as a "path list" or...

> WDYT re: flag naming in that case to make it abundantly clear that this is a scriptability feature? Hmm, I'd somewhat like to avoid "interactive" as part of the...

From a performance point of view it would be much more efficient to just keep all save files in a single snapshot. But the unnecessary warning are still a (tiny)...

You can set the environment variable `GODEBUG=http2client=0`. This should result in multiple backend connections. However, using multiple connections by default might be a good idea though.

> 3\. Restore still only uses a single connection. I guess restore does not use multiple backend connections as set by `-o .connections=5`? That depends on the phase of the...

The suggested changes require a major rework of the repository format. That definitely won't happen before the changes planned for restic 0.18 and probably also 0.19 are done. > It...

Before discussing further solutions in more detail, we should first make sure we understand which problems we're actually trying to solve. Right now, those feel rather mixed up.

> Pack files are free to be re-arranged without re-encryption (it just means that key derivation data must be preserved). So essentially a pack header would end up containing multiple...