Nicolas Grilly

Thanks!

Same as @deanmax. Commenting `network_mode: host` on all services in our docker-compose.yaml "fixes" it. Any idea about what the root cause?

Ok, I think the proper term in this context is "subtype polymorphism": https://en.wikipedia.org/wiki/Polymorphism_(computer_science)

One more thought: To decode the filename, it seems reasonable to use the charset defined in `attempt_charsets`, instead of the hardcoded ISO-8859-1. But many things make this difficult: - The...

> We might want to just swap the instances of US-ASCII to UTF-8 instead. Swap the instances of US-ASCII **and ISO-8859-1** to UTF-8.

Some valid ISO-8859-1 sequences can be mistakenly decoded as UTF-8, but it's extremely unusual. If you choose one byte between C0 and DF (À, Á, Â, Ã, Ä, Å, Æ,...

> Technically, any utf-8 bytestring is valid iso-8859-1. Agreed. > * This issue of header decoding matters mainly, if not only, for `Content-Disposition`, because it contains a user-supplied file name....

Do `match_recipient` and `forward` accept other parameters, in addition to `dns=True`?

I have the exact same issue, and came to the same conclusion. > This may only occur if you specify multiple docker-compose yaml files that are merged by docker stack...

I think Obsidian is solving this problem without CRDTs, by just merging the server-side and the client-side content using a standard text merge algorithm like the one in `difftools`.