As an old hand who was around when homebrew started, I feel obliged to let people know there are alternatives. If you find brew's take-over-your-system-and-youll-thank-me approach off putting, and/or you value stability over the coolness factor, MacPorts is still alive and well ( https://www.macports.org ), and in-fact has basically all the same packages brew does. In 18 years of using MacPorts, it's never messed up…
I've been trying Nix devenv[0] and nix-darwin[1] on Mac recently and having a blast. Definitely better than the stuff I had to build around Homebrew to make development environments consistent across machines. Nix-darwin even has support to install Homebrew packages. [0] https://devenv.sh [1] https://github.com/LnL7/nix-darwin
Homebrew 4.0.0
271–280 of 403 posts
Re: Homebrew 4.0.0
#272Earlier quoted context omitted.
Read your own cite: nothing about the UUID in question is associable with an identified or identifiable natural person, which is what the GDPR concerns. We do not have the ability to correlate your package installs (again, we do not know what you install) with your browsing history, and we do not store any information that would allow us (or an adversary) to do so.
Read your own cite: nothing about the UUID in question is associable with an identified or identifiable natural person, which is what the GDPR concerns. This is false and a misunderstanding of the GDPR. It is not about whether it is currently possible. But whether it would be possible if it was correlated with other data. What differs pseudonymisation from anonymisation is that the latter consists of removing persona…
We do not store anything else that could correlate with that UUID. We don't expose it to anybody else and it's unclear how, even if we did, it would result in personal correlation.
Re: Homebrew 4.0.0
#273Earlier quoted context omitted.
That’s not the point. I don’t want any software sending analytics unless I specifically allowed it.
Agreed, I was shocked when I installed the Dart programming language and found out it sends analytics by default. A programming language!
Re: Homebrew 4.0.0
#274Earlier quoted context omitted.
I find this very invasive and I am glad I never used homebrew and always used Macport instead.
Well I have bad news for you there too https://ports.macports.org/statistics/faq/ I really do think that people who are concerned about telemetry should install Little Snitch and also look at each of these programs documentation. Telemetry is called out for most of them, as well as how to disable it. It’s also not inherently bad as it can be a valuable tool to improve their systems, though obviously could be abused t…
Re: Homebrew 4.0.0
#275> 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…
In your .bashrc or similar: export HOMEBREW_NO_ANALYTICS=1
Re: Homebrew 4.0.0
#276Earlier quoted context omitted.
Yes, you don't get to decide to violate your users' rights and surveil them because you think it will improve your product.
1 it is their choice what soft they use, isnt it? Its not like chromium on android being pushed on you 2 there is "reasonable" / "good faith" data that in my opinion can be sent e.g crash log, stats like e.g package popularity etc. You just create drama over nothing. Ive used data like this to improve my soft countless times and there is nothing shady at all, everything is about what you collect. Theres difference be…
Yes. More evidence for an observation I've been having that ultimately the software is always about what the creator of the software wants, and not the user. I'm working on moving to running only my own software for that reason.
Re: Homebrew 4.0.0
#277There's so much thankless toil that goes into maintaining package infrastructure that we all just take for granted. Thank you!
Re: Homebrew 4.0.0
#278Earlier quoted context omitted.
[flagged]
Several phrases yet zero actual counter-arguments. Everyone from 6 years old and above can swoop in and insult. Maybe you were lost on your way to Reddit?
If you think a package manager is nothing more than a file server, I'd suggest you learn more about what a package manger does or just go live in Reddit land with all of the other willfully ignorant types. It is not for us to convince you otherwise. It's such lame comparison that even searching for "file server vs package manager" doesn't even autofill because nobody searches for it because probably nobody would ever even sanely think to make the comparison.
Re: Homebrew 4.0.0
#279Earlier quoted context omitted.
Read your own cite: nothing about the UUID in question is associable with an identified or identifiable natural person, which is what the GDPR concerns. This is false and a misunderstanding of the GDPR. It is not about whether it is currently possible. But whether it would be possible if it was correlated with other data. What differs pseudonymisation from anonymisation is that the latter consists of removing persona…
Apply the counterfactual: what would have to be the case in order to correlate the UUID in question with user data? We do not store anything else that could correlate with that UUID. We don't expose it to anybody else and it's unclear how, even if we did , it would result in personal correlation.
We do not store anything else that could correlate with that UUID. We don't expose it to anybody else and it's unclear how, even if we did, it would result in personal correlation.
You can argue against this, but it's simply how the GDPR defines personal data, and if you violate it, someone could report you to their data protection authority.
Secondly, the GDPR does not just do this to protect citizens against direct use of their personal data (I think most Homebrew users would be immediately convinced that you wouldn't misuse this data, including me), but also scenarios that are outside of your control. Such as: Google decides to violate the GDPR against your will and correlates the data. Or: Google Analytics gets hacked, the data set becomes available on the black market or wherever and people correlate the data with other leaked data.
Re: Homebrew 4.0.0
#280Earlier quoted context omitted.
Homebrew can detect a lot of things during normal maintenance work: there are extensive tests and checks during compilation and bottle building, for example. However, we can't catch everything: Homebrew has millions of users, and those users have all kinds of different setups. We can't predict every possible host and software interaction; basic failure analytics help bridge the gap there.
Okay, I'm sold, and I'm sorry for being blunt. Where can I learn more? Can you point me at the right place in the source? I'll not be banning Homebrew telemetry.
I've linked Homebrew's analytics data and the source code that collects it elsewhere in this thread.
And, to be absolutely clear: it is perfectly fine for you to disable Homebrew's analytics. There are an infinite number of legitimate reasons for doing so, including the most basic one of "I just don't want to." My sole goal is to dispel the small number of inaccurate beliefs about what Homebrew collects, why we collect it, etc.