> That binary blob was inactive and had to be proactively turned on in the settings screen. So was it really an issue? No, but ... Just to be clear about a thi

> That binary blob was inactive and had to be proactively turned on in the settings screen. So was it really an issue? No, but ... Just to be clear about a thing, there was an issue. The automatic download of the extension occurred in Chromium, the FLOSS software around which Chrome is built. Chromium is shipped in a multitude of linux distributions, including Debian. Debian takes their FLOSS standards very seriously. The automatic downloading of a binary blob by Chromium was a FLOSS ethics issue. Google went on to address the issue by not just removing the automatic download, but ensuring that the remaining hooks to enable the audio search feature were removed. That's the entirety of the actual, real controversy. The rest is made up assumptions by people that fail to understand Hanlon's Razor: never attribute to malice that which is adequately explained by stupidity.