Clarify ruleset statistics

[J0WI]

From the statistics in your article it's not clear whether the lists form HSTS Preload, HTTPS Everywhere and Smarter Encryption overlap or if you have to use all lists to get the full coverage.

Could you provide some more details about the measurement?

I already noticed that HSTS Preload and Smarter Encryption can only contain hosts while HTTPS Everywhere can also cover more complex scenarios where a domain only supports https on an alias (most common case is with vs without www prefix) or only on specific paths.

[zachthompson]

Traffic coverage was from using a single list, not cumulative.

[Freso]

The article does mention that

[…] at least in our large sample, all of the hosts that HSTS Preload and HTTPS Everywhere upgraded, were also upgraded by Smarter Encryption, plus a whole lot more.

As I read that, that means that the lists were not combined, but that all (or far most at least) entries in HSTS Preload and HTTPS Everywhere also exist in the DDG Smarter Encryption one.

[Sholman81]

https://github.com/duckduckgo/smarter-encryption/blob/f22295841e92408fc24dd1b6aaa9dddee2b0a7fd/CONTRIBUTING.md

[Sholman81]

![1467466](https://github.com/user-attachments/assets/f4170a24-f4ff-4367https://github.com/duckduckgo/smarter-encryption/blob/f22295841e92408fc24dd1b6aaa9dddee2b0a7fd/CONTRIBUTING.md