Furthermore this literally gives google the power to shut out competing browsers “I’m sorry but we’re not supporting an open source solution like this”: Īs far as I know youtube itself doesn’t use DRM (maybe on youtube red…?) Anyways it wouldn’t be difficult for google to enable it if it wanted to, and obviously it wouldn’t be difficult for google to block firefox and chromium if it wanted to either. Obviously being dependent on 3rd party binary blobs from google causes new challenges when a browser needs to be ported (as in the case of ARM M1 CPU). This is provided in the form of binary blobs that are needed by firefox.
Sadly, apple and google successfully campaigned for DRM to be included in the HTML5 standard and firefox was given an ultimatum: support hollywood DRM or become irrelevant for commercial streaming services. Since then, Widevine use has become widespread across the Chrome web browser, Android, and content streaming services including Google Play, Amazon Video, BBC, Hulu, Netflix, and Spotify. The acquisition was seen as Google’s strategy to placate Hollywood and content owners. You’re not gonna like this, but google DRM is already a thing…īack in 2010, Google acquired the DRM and video optimization company Widevine. By the time people realise why YouTube has limited resolutions in Firefox, it will be too late. It will be silently phased-in for 4K or 8K videos in the YouTube app, and will move downwards to more resolutions and eventually expand to the website. It will not have a name (like AACS and SecuRom have).
This is what we in the business call a “dick move”. There is no good reason for Google to do this, other than to force people to use Chrome. Or to put it bluntly, they do not want you to access their Google API functionality without using proprietary software (Google Chrome). The reasoning given for this change? Google does not want users to be able to “access their personal Chrome Sync data (such as bookmarks) … with a non-Google, Chromium-based browser.” They’re not closing a security hole, they’re just requiring that everyone use Chrome. It is noteworthy that Google gave the builders of distribution Chromium packages these access rights back in 2013 via API keys, specifically so that we could have open source builds of Chromium with (near) feature parity to Chrome. This will make the Fedora Chromium build significantly less functional (along with every other distro packaged Chromium).
Google has announced that it is cutting off access to the Sync and “other Google Exclusive” APIs from all builds except Google Chrome.
0 kommentar(er)
