> I don't buy this explanation. In fact, it is very inconsistent with the fact > that widevine is enabled and binary blobs are downloaded. This is incorrect. Enabling Widevine support in the browser will not do anything unless the Widevine shared object is downloaded and installed manually. This is documented in README.debian: https://salsa.debian.org/chromium-team/chromium/-/blob/7810576a1215c28d5daff0e0fbd0e3687fc43d72/debian/README.debian#L32
> In summary, if one is going to disable hangouts/etc, at least be consistent > and disable widevine... I agree in the essence of this point. I would also like to re-iterate the point I made last message about how Sign-in is disabled via a patch even though Google API keys are included. Disabling Sign-in makes the API keys effectively useless. Overall, I think Philipp, Josh, Rogério and I all agree that Debian needs to clearly define expectations/guidelines on how the chromium package will interact with Google. Right now, Debian's stance seems inconsistent at best, and that is creating a confusing user experience. Regards, Eloston
