Jakob Borg

There is a better error message, but a) this seems to be a case where the name badness is in something that isn't synced, perhaps ignored, and just created as...

That's unrelated to the issue, but the discrepancy is (at least) on the computer where the error is printed, so you can fix it there.

Seems to me like this could be part of the normal lookup, that is `tcp://example.com` would look for `_syncthing._tcp.example.com` SRV and if not present do the normal resolution for `example.com`?...

I think this is a decent enough request as-is. Yes it's niche, but we do things that are niche if the cost is low. Simply adding a srv lookup when...

I think this could be configurable, yes. There may be some trickiness as the GUI is involved in ignores.

We do rename detection on the receiving side... such as it is; nonetheless, the versioner (external or otherwise) doesn't get told about the reason a file is being versioned.

The API endpoint is already there though in the form of /rest/system/browse.

Yeah that or the new fancy Windows installer

Or it could mean there's a broken proxy or something in between... I can see that it would be nice with something answering with a 200 OK and a small...

That test tries to establish a connection to itself with the various methods we support, I don't think inotify is involved. Maybe run with -v and try to figure out...