Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
respect DO_NOT_TRACK env var per consoledonottrack.com #6745
I would rather see the different packager managers sit together and work on that standard.
I have also the same opinion as syncthing/syncthing#6158 (comment),
I also take the opportunity to remember to all our users that we have been really transparent about our analytics strategy: https://docs.brew.sh/Analytics.
@grxnola if you think there is any GPDR violation here, I would like you to give us the exact articles from the regulation which you think we violate. Please open a new issue for this (to not clutter this discussion). We are open to learn and improve what needs to be improved. But I do not think we are doing anything wrong right now, and already have reviewed this topic internally.
Also, if we really need a more formal decision on this, we can involve the Homebrew Technical Steering committee (https://docs.brew.sh/Homebrew-Governance).
I am personally not in favor of adding this env variable.
Most other package managers do not send analytics by default (or even have the capability of doing so at all) - especially distribution package managers. I'm from the Arch Linux team and we e.g. do not even have rough info on the amount of installed systems, because there is no official data collection at all. Brew and other community-effort or domain-specific package managers are the outliers in that methodology i think.
I for one would really enjoy seeing analytics collectors like brew make this change, to allow for a more standardized and unified way to opt out of data collection. It is a change that will require adoption, and i think getting it introduced into brew & co is a great opportunity to get wider adoption in software like this.
We shouldn't accept a future where spyware is the norm and rely on this environment variable. We know how that turned out with HTTP Do Not Track. As long as spyware is bundled with Homebrew, Homebrew shouldn't be used or recommended or normalized. The solution is for Homebrew to remove its spyware by having explicitly opt-in telemetry only.
@sneak None of the PRs you have opened have been merged yet. As-is: this is not a "standard", it is a webpage you have made with some links to PRs.
Currently it has no adoption. It's not on Homebrew to change that.
Thanks for implying legal threats against volunteers who spend their free time making software you use for free!
Run your package manager how you want/need and we'll do the same.
No, you've said the solution: you can stop using or recommending Homebrew.
Everyone who comes to this thread should take time to (re)read https://docs.brew.sh/Analytics and note that we tell people about our analytics and direct them to documentation which describes opt-out before we ever send anything (on initial installation or on
@4n3w a few things:
No-one from Homebrew has made that claim.
This conversation is not a good use of anyone's time at this point. When more projects have adopted this: we will reconsider it.