News for hackers. Stuff that matters.
Re:Goodbye Mac OS Forge, hello GitHub by Buge on Sunday August 21, 2016 @04:59AM (#12330060)
It's not that they want to send it to Google, it's that they want to send it to homebrew, and google is an intermediary. Sending it to homebrew allows them to know what features are being used, so they know what features they could remove or improve.
Re:Goodbye Mac OS Forge, hello GitHub by s_q_b on Sunday August 21, 2016 @06:08AM (#12330257)
If homebrew is transmitting the packages you install across the internet, through Google's servers, and through homebrew's system, it is very possible that information could be swept up in a dragnet or stored on a server that could later be subpoenaed or searched with a warrant.
Re:Goodbye Mac OS Forge, hello GitHub by semi-extrinsic on Sunday August 21, 2016 @06:40AM (#12330321)
The analytics issue aside, how can a package manager not transmit what packages you install across the internet? At some point it has to request the package(s) you're installing from somewhere on the internet.
Re:Goodbye Mac OS Forge, hello GitHub by s_q_b on Sunday August 21, 2016 @01:10PM (#12331669)
Yeah, over TLS, and I generally presume that a simple request for a package won't be logged and recorded for posterity.
Re:Goodbye Mac OS Forge, hello GitHub by cocotino on Sunday August 21, 2016 @07:59AM (#12330590)
So don't use Google as an intermediary. Debian runs popcon, for example. They could run something similar.