Jakob Borg

I don’t think so. That issue is that when the change is done in the web GUI the device name doesn’t “take” at all - it’s not sent to the...

But I can see how my PR description might be misinterpreted under the circumstances. :D

From a Syncthing point of view there's no real difference to it - you just start it up, point -home towards somewhere suitable, and configure it appropriately. You'll need to...

We already use all CPU cores for hashing, since that issue was closed (six years ago). This is about using more cores in the walk stage, which is only useful...

This is too vague to be actionable, though there is likely a bug *somewhere*. There's another issue that cover potential index transmission issues during initial setup, which may be relevant.

You guys can take the s3fs discussion to some s3fs discussion place, please.

Sure seems like no

Why not just point the other side towards the name directly, skipping the round trip via discovery?

So "tcp://whatever.example.com, dynamic" to first try your host name and then use discovery if it doesn't work. I don't see opposition, really. I see people thinking they need this when...

That already happens by default. `globalAddress:localListeningPort` is announced and tried because that's where any manual port forward would be.