Sophie Herold

@yaahc > from my initial digging it seems like what they may actually want is to switch to `OUT_DIR`, which is already stable `OUT_DIR` is read only if I understand...

@ThomasWaldmann This is very high on my wishlist. Does this need any conceptual considerations for 2.0 or is it rather independent?

@ThomasWaldmann I would suggest removing the b-fields from 2.0 because they can deliver invalid JSON. Potentially add base64 or something like that instead.

At first glance, this seems redundant to [message ids](https://borgbackup.readthedocs.io/en/stable/internals/frontends.html#message-ids). Pika is already making use of them. Therefore I don't see the use case yet. (I would like to add msg...

It's not unusual to have different warnings like "File changed during borg create" or "File not found" during one `create`. I'm not sure how return codes would handle that. Overall,...

A more general solution might be to add [`msgid`](https://borgbackup.readthedocs.io/en/stable/internals/frontends.html#msgid)s to the messages that should be filtered and add a general option to filter message ids. (This one is orthogonal to...

> seems most of them are hard errors True, with the current set of msgids this would barely make sense.

Sound like I have two (#6038) different issues with `check` that only occur with my remote backup which are not reproducible for others? I will try to find a different...

Both issues seem to be exclusive to my Hetzner Storage box. Unfortunately `ssh backup-server borg serve --show-version --debug` does not give me any output which is already strange I guess?...

> I'ld suspect hetzner runs `borg serve` as a forced command from `.ssh/authorized_keys` - this might influence what commands / options you are able to invoke from your side. Sure....