3 ms·
https://forums.macrumors.com/threads/chromium-legacy-google-chrome-for-os-x-10-7-10-9.2283612/page-16?post=33170934#post-33170934 https://forums.macrumors.com/t
by its-summertime 2y ago
https://forums.macrumors.com/threads/chromium-legacy-google-chrome-for-os-x-10-7-10-9.2283612/page-16?post=33170934#post-33170934 https://forums.macrumors.com/threads/chromium-legacy-google-...
- beretguy 2y agoLooks like this is a step towards Google DRMing the internet. This is bad.
- lxgr 2y agoHow would Google push DRM by filing false [1] copyright claims against various Chromium forks, which presumably wouldn't even contain any hypothetical DRM keys? Regular old Chrome does in fact include a Widevine DRM binary blob, but Chromium doesn't contain the source for it. If Google really wanted to push something like browser attestation (like they potentially did with their Web Environment Integrity proposal), almost by definition that part couldn't be open sourced either and would not be part of Chromium. [1] Chromium is licensed under various open source licenses that Google can't retroactively revoke. Even for code that they own the full copyright on, they can at most release future versions under a closed license; for GPL-ed dependencies, that wouldn't work at all (not sure if Chromium has any).
- deleted 2y ago[deleted]
- DANmode 2y agoWhy couldn't browser attestation code be OSS?
- lxgr 2y agoThe code could be (but often isn't, to frustrate circumvention), but the signature keys can't, just like with all DRM.
- 63stack 2y agoWhat's the point of playing devil's advocate, or giving any benefit of doubt to Google? They have shown repeatedly that they intend to control the internet. Just because we can't see why yet, it's not far fetched to assume that this might be a step in that direction.