Caddy's build are reproducible as per https://github.com/golang/go/wiki/Modules. The downloader offers you to extend Caddy with plugins, and this will change the hash of the binary compared to a straight build from the source code. Keep in mind that Telemetry is enabled by default in the source code, unlike @ the downloader, this changes the hash too.
Caddy 2 is under internal development, and will be open source as per https://caddyserver.com/blog/announcing-caddy-1_0-caddy-2-ca... Ofc, the thread has been locked, because it is off-topic, the linked issue is about listeners, not the development of Caddy 2.
> Who cares about the depth of certificate chains? What value does it bring?
The data will be used to analyze the Internet from the server perspective, similar to e.g Mozilla collecting data from the clients perspective. It can/will be used by e.g researchers to improve the Internet (security, speed etc.)
Who are these researchers? Does Caddy have the kind of market share that would make that information useful?
I could sort of understand it is this was being pitched as a way to improve Caddy by reporting back crashes or misconfigurations. But what I've heard makes no sense to me.
