I tried creating a web browser, and Google blocked me

https://blog.samuelmaddock.com/posts/google-widevine-blocked-my-browser/

I'm sorry but we're not supporting an open source solution like this

After 4 months of waiting, that is the response I got from Widevine, Google’s DRM for web browsers. For the last 2 years I’ve been working on a web browser that now cannot be completed because Google, the creators of the open source browser Chrome, won’t allow DRM in an open source project.

The browser I’m building, called Metastream, is an Electron-based (Chromium derived), MIT-licensed browser hosted on GitHub. Its main feature is the ability to playback videos on the web, synchronized with other peers. Each client runs its own instance of the Metastream browser and transmits playback information to keep them in sync.

If someone is creating a browser that wants to playback media, they’ll soon discover the requirement of DRM for larger web media services such as Netflix and Hulu. There are a few DRM providers for the web including Widevine, PlayReady, and FairPlay.

As far as I’m aware, Widevine is the only available DRM for a Chromium-based browser, especially so for Electron. Chromium accounts for roughly 70% market share of all web browsers, soon to include Microsoft’s upcoming Edge browser rewrite. Waiting 4 months for a minimal response from a vendor with such a large percentage of the market is unacceptable.

This isn’t something I’m alone in either, several Electron users have waited months for a response. More prominently, the creators of Brave Browser also had issues waiting for replies from Google Widevine.

“This is a prime example for why free as in beer is not enough. Small share browsers are at the mercy of Google, and Google is stalling us for no communicated-to-us reason.” – Brian Bondy, Co-founder & CTO of Brave

I’m now only left with two options regarding the fate of Metastream: stop development of a desktop browser version, or pivot my project to a browser extension with reduced features. The latter requiring publishing to the Google Chrome Web Store which would further entrench the project into a Google walled garden.

If you know of any way to help out, please get in touch.

See post on Hacker News for discussion thread.

Leave a Reply

Your email address will not be published. Required fields are marked *

Next Post

The MacBook keyboard fiasco is way worse than Apple thinks

Tue Apr 2 , 2019
https://m.signalvnoise.com/the-macbook-keyboard-fiasco-is-surely-worse-than-apple-thinks/