Jakob Borg

My thinking is that the compat file would be a download among the release files, https://github.com/syncthing/syncthing/releases/tag/v1.27.10, like sha1sum.txt.asc or similar. It would contain the compatibility requirements for that release specifically....

> Also, I'm assuming the runtime is for documentation purposes only. We aren't gonna verify the binary was actually compiled with that version of go, correct? We should verify that,...

For what it's worth, we've leaked this in the health endpoint since a few versions as well, but I agree we should not. ``` jb@ok:~ % curl -i http://localhost:8081/rest/noauth/health HTTP/1.1...

Yeah, that's [protocol.ReceiveTimeout](https://github.com/syncthing/syncthing/blob/8edd67a569594bec06c395041acb7eb18f8e3b13/lib/protocol/protocol.go#L239) in action. The root cause here is that the connection is never closed, the other side just disappears from the network, so the timeout is the only...

I guess 🤷

Didn't look at any code yet, but I can say that exposing config values in the range of millions of seconds in the non-advanced GUI certainly doesn't seem ideal. Humans...

Maybe we could have a time picker of some kind. 

I don't particularly follow what you say happened here. There's no "reverse sync of partial files", partial files are stored as (ignored) temp files until they're complete.

What do you mean, "by mistake I shared the partially synced file", how did you do that exactly?

I think this is an effect of newly created folders on Android being set to send-only, and then an unfortunate sequence of button presses. I don't think it's a bug...