Earlier quoted context omitted.
There are too many projects as there are, let them "burn out" and make way for those that aren't spyware. Giving away something for free gives no guarantee of quality, but doesn't justify stealing analytics.
How about try not to assume malice out of people's free software from the very first thing they did that you don't agree with? Its open source. Why not open an issue, contribute a patch to make the process opt-in, start a discussion, start a fork? Oh, of course, why would we do that when we can attack the maintainers, call their software a spyware, and threaten to sue instead? While we're at it, let's use words like…
The maintainer already stated it's not a bug, plus the nature of the message implies opt-out was a design choice.
> of course, why would we do
Why start a fork before "attacking" the maintainer? Are you suggesting we need to audit every code base we use? As reasonable as checking every box of morning cereal for glass shards.
The software is spyware. Words like "spyware" and "stealing" are correct, I don't care how it paints the maintainer to describe the situation accurately, they created that situation.
> calling out this kind of behaviour is the least I could do
by "calling out this kind of behaviour" you attacking critics with poor arguments? That's not support, its fan-boyism.