myolxid1

3 ms·

1. 1.▲
   by myolxid1 5y ago

   It is likely that you'd have seen it anyway, as `brew update` loads casks whether or not installed. Note that this happened only to people who tapped the cask repo. Turning off the autoupdate is highly not recommended - you don't
2. 2.▲
   by myolxid1 5y ago

   I imagine that having an additional server for a (somewhat understaffed) project run by volunteers introduces additional costs and additional maintenance burden. The current process is already convenient and all you need is a GitHub account
3. 3.▲
   by myolxid1 5y ago

   Fine on the unauthenticated part. But about private data - it's literally anonymous and just counting the number of installs of a package and the number of build failures. All the data they collect (and the code that handles it) is pub
4. 4.▲
   by myolxid1 5y ago

   Analytics are an invaluable resource for a volunteer-run project. To their credit, they issue a noticeable warning with the command to turn it off. It seems to me your issue is more about using Google Analytics - if there's a better al
5. 5.▲
   by myolxid1 5y ago

   The automated pipeline doesn't exist any more. More than donations I think this requires volunteering to review pull requests, as they mention in the disclosure.
6. 6.▲
   by myolxid1 5y ago

   I'd rather call it smart engineering that makes it easy for anyone to contribute. `brew bump-formula-pr` etc. are huge drivers behind Homebrew having among the largest number of contributors on GitHub. It would help them a lot more if