bt90

@tomasz1986 are you still working on this? Would love to see this merged.

As we're adding a proper loginpage (yay!) could we also fix the favicon for password managers while we're at it? https://github.com/syncthing/syncthing/pull/7676 tl;dr provide a static /favicon.ico without requiring authentication

At least for Bitwarden it should be enough to have the initial favicon in the HTML without requiring JS and the image to be reachable without authentication.

> but it seems out of scope for this PR. All good :)

I might be murdering someones baby for asking but can't we shrink the current About page? The list of contributors could be maintained on the Github readme for example.

At least for docker you could switch to the host network mode.

That and we should improve the discovery section in our docker documentation: https://github.com/syncthing/syncthing/blob/main/README-Docker.md#discovery Interface IP discovery is also solved by switching to host network mode. I'll create a PR later.

Maybe we should discuss this in the forum. There's also https://github.com/syncthing/syncthing/issues/8453 which also hits the same note of "what do we want to publish".

caddy and mongodb also use these kind pseudo URIs. e.g `srv+http://example.com` or `mongodb+srv://example.com` which roughly follows this IETF draft: https://datatracker.ietf.org/doc/html/draft-jennings-http-srv-05 But i wouldn't want to hardcode protocols like `tcp+srv://` or...

The discovery server is not a silver bullet as for example discussed in https://github.com/syncthing/syncthing/issues/8445#issuecomment-1193862633 With the SRV approach we'd target a middleground of not having to hardcode addresses when the...