Live data from Hacker News

Homebrew 4.0.0

brew.sh

291–300 of 403 posts

Re: Homebrew 4.0.0

#291

Earlier quoted context omitted.

Opt-in analytics are useless, unless a large part of your userbase just clicks through the entire wizard without thinking; there’s little overlap with Homebrew’s userbase

Not my problem. They don't have a right to spy on users.

Stop it. They are not spying on users.

Re: Homebrew 4.0.0

#292

Earlier quoted context omitted.

They'd be well advised to make this opt-in only for legal reasons. This is not going to go down well in a lot of places and they might get exposed to law suits.

Opt-in analytics are useless, unless a large part of your userbase just clicks through the entire wizard without thinking; there’s little overlap with Homebrew’s userbase

"The alternative is useless" is not a valid legal defense.

Re: Homebrew 4.0.0

#293
post #209
post #118

Earlier quoted context omitted.

Homebrew should support the DO_NOT_TRACK environment variable. https://consoledonottrack.com/ It doesn't look likely though. I don't think it looks good that comments pointing out that Homebrew's existing behaviour (collecting analytics without obtaining informed consent from users) violates the law have been classified as abuse and hidden! https://github.com/Homebrew/brew/pull/6745

In retrospect (consoledonottrack operator here) I never should have pushed an opt out standard; it legitimizes opt-out which is indefensible and unethical. Opt-in by advance consent is the only way. Homebrew devs are unethical jerks. Use nixpkgs and don't look back.

I appreciate you changing your mind on this.

Re: Homebrew 4.0.0

#295

Man there are a lot of complaints about this free software no one is forcing you to use. I would start with a thanks to the people who spend a lot of time on this, and probably not for much wealth. I know I greatly appreciate the existence of homebrew.

This is the ugly side of HN in my opinion. Discussions here are usually very reasonable, except for a few subjects such as telemetry.

I guess to the hacker heads of HN, telemetry is as political as religion for regular people.

Re: Homebrew 4.0.0

#296
Didn't the author sunset this project to become a web3 advocate and pivot to a new project where some dubious NFT would be exchanged for package installations? I guess 2022 came and went since then...

Re: Homebrew 4.0.0

#297
post #268

Earlier quoted context omitted.

Homebrew doesn't "report" anything to Google, much less anything of yours (implying unique identification). This is an unnecessary editorialization. You can see exactly how Homebrew does analytics here[1], and you can see the sum total of the information collected here[2]. No identifiable information is collected or retained. [1]: https://github.com/Homebrew/brew/blob/master/Library/Homebre... [2]: https://formulae.b…

>You can see exactly how Homebrew does analytics here[1], and you can see the sum total of the information collected here[2]. No identifiable information is collected or retained. If my computer is sending data to Google then Google has my IP address and can correlate that data however they want. You simply can not claim that identifiable information isn't collected or retained unless you work for Google. I don't kno…

> I would be much more comfortable if they used something like Plausible for analytics

Their intent is to migrate entirely away from Google to the San Francisco based InfluxData, which I guess is marginally better in some ways but seems to entirely miss the point of people's objections in spirit. Other than people's personal subjective trust of one US company over another, there's no inherent difference between Alphabet & InfluxData from a technical standpoint.

InfluxData do collect IPs per https://www.influxdata.com/legal/privacy-policy/

Re: Homebrew 4.0.0

#299

Earlier quoted context omitted.

What kind of decisions do you make based on the analytics? Do you drop unpopular packages? To me, one of the advantages of a package manager is having a huge database of long-tail packages that are just one command away. If you kept only the popular packages you might as well just have an installer that installs them all together in bulk.

> Do you drop unpopular packages? Yes: Homebrew deprecates and/or disables packages if we see evidence that they're unmaintained and not actually supported on the platforms we support, or only used by a tiny fraction of users while also requiring disproportionate maintainer time (e.g. due to complex or flaky builds). The goal is to balance conflicting user interests: 99% of users want maintainer effort focused on the…

So if a package has a small community of users and is well-maintained upstream but not popular overall you'll keep it around?

Re: Homebrew 4.0.0

#300
post #2

> Homebrew’s analytics are now sent both to Google Analytics and our new, self-hosted InfluxDB instance hosted in the EU. > If you had previously set HOMEBREW_NO_ANALYTICS because you didn’t like Google Analytics and/or data being sent to the USA: please consider unsetting this and setting HOMEBREW_NO_GOOGLE_ANALYTICS instead, allowing analytics data to be sent to our new InfluxDB host. My package manager was reporti…

[deleted]
Post reply on HN