popcon should not be used as an example of how to do telemetry, as it is far worse for privacy than the Go proposal: 1. Sends names of private packages to the

popcon should not be used as an example of how to do telemetry, as it is far worse for privacy than the Go proposal: 1. Sends names of private packages to the server, and publishes them. 2. Sends a unique identifier (a UUID stored in /etc/popularity-contest.conf) to the server, which is stored. 3. Doesn't use sampling, so if you use popcon you will be submitting a report once a week (Go's telemetry would average just one report a year). 4. Submits over plaintext protocols by default. popcon may be opt-in (in the sense that the prompt during installation has "No" selected by default) but the prompt doesn't disclose the large privacy risks. People are not appreciating the thought that has gone into the Go proposal to minimize the collection of private data, either intentionally or by accident, such as the client-enforced requirement that the the names of counters be published in a tamper-proof log so anyone can verify that, for example, no private package names are being disclosed. Everyone is focusing on opt-in vs out-out, but to me these other details are far more important.