News for hackers. Stuff that matters.
Re:Homebrew 4.0.0 by darkwater on Thursday February 16, 2023 @06:41AM (#34817467)
Then you can either: 1) don't use the software 2) analyze the software source code to understand what it does before using it

I tend and prefer to assume good-will WRT telemetry in well-known and independent opensource projects.

Re:Homebrew 4.0.0 by vetinari on Thursday February 16, 2023 @06:47AM (#34817516)
You forgot 3) Complain at different intensities, up to the shaming, about the unethical dark patterns employed by the software, no matter whether it is open source or not, to make authors of the software aware, that what they do is not welcome by their users.
Re:Homebrew 4.0.0 by predmijat on Thursday February 16, 2023 @06:45AM (#34817498)
Disagree, it should be the norm.
Re:Homebrew 4.0.0 by glenngillen on Thursday February 16, 2023 @06:56AM (#34817576)
I use Little Snitch to alert on any outbound connections and make a decision. The google stuff immediately got a permanent blackhole for Homebrew. Anything I'm uncertain of I'll give a short-term approval (30mins) to not break anything. After a couple of rounds of execution (and sometimes some trial & error) you can usually work out which requests are essential and which are some notifications/tracking thing.
Re:Homebrew 4.0.0 by daneel_w on Thursday February 16, 2023 @07:07AM (#34817664)
So you didn't see the notice brew(1) gives you on first run?
Re:Homebrew 4.0.0 by glenngillen on Thursday February 16, 2023 @07:14PM (#34828745)
I can't recall, though this approach isn't specific to homebrew. I block it permanently at a network/process level rather than having to remember to set a ENV var.