(Replying to PARENT post)
This doesn't invalidate any of the author's points, and they're right to be upset. But the problem isn't Chrome per se, it's DRM-encumbered media.
And that's why I buy audiobooks from Libro.fmβ , games from GOGβ , and (out of necessity) movies and TV shows from iTunesβwhich are still DRM'd by default but are at least relatively easy to decrypt.
----------
β Among others, I don't use any one source.
(Replying to PARENT post)
https://security.googleblog.com/2019/04/better-protection-ag...
(Replying to PARENT post)
(Replying to PARENT post)
Seems that google pushed hard for EME, under the guise of giving widevine to anyone who wanted it. Of course, as is evident from OPs situation - this isn't the case.
There is an ongoing EC investigation.
(Replying to PARENT post)
If users can execute their free software rights (modify software and run modified versions), they can instruct their computers to do anything, thus DRM would not be possible. Binary blobs like Widivine are not complete DRM solutions on systems where users can still modify their display server or kernel. As DRM gets more widespread, content providers will require more strictly locked systems, that's why mobile devices are shipped with locked bootloaders and PCs have secure boot and TPM β most current hardware is ready to support strict DRM.
The only approach to DRM is to boycott its use completely, there is no workaround or compromise.
(Replying to PARENT post)
Title is very missleading, your web browser works and google does not block you, it's all about DRM.
"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."
This is crap, you should probably have known that before starting the project? As a dev it should be some common sense that you can't just playback 4k video from Netflix with a built-in Browser.
(Replying to PARENT post)
Say that Google desperately wanted to support any reasonable method to accomplish allowing open source tools access to DRM-protected media. Is there some way to allow that? What would it look like?
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
Google has announced that it is cutting off access to the Sync and "other Google Exclusive" APIs from all builds except Google Chrome. This will make the Fedora Chromium build significantly less functional (along with every other distro packaged Chromium).
(Replying to PARENT post)
(Replying to PARENT post)
Where are the relevant philosophical and legal debates around digital copy?
If we establish some common ground over copy, where balanced legal frameworks can grow, i bet things like DRM would be considered illegal.
It should be not be considered a reasonable legal path to be pursued against copyright infringement (which is a reasonable right).
And while we are at that, i see a lot of people mentioning feeling betrayed by Firefox, while back in the day, i felt that it was Tim Berners Lee and W3C who stabbed me in the back with this.
Is in time like these that we see how important it is to have a guy like Linus (and all the contributors) behind important projects.
Corporations being pulled by the capitalistic strings are not suppose to look forward higher ethical things as the "common good".
Its not irrational that corporations do this kind of things, its irrational that we expect them not to, knowing the game that is being played here.
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
We need more "web browsers" that just browse HTML.
(Replying to PARENT post)
This is a closed source, downstream effort which means no modifications can be made to Electron itself. All changes must make it upstream to show up in this fork. When asked whether they would eventually merge it upstream, they didn't provide a clear answer [1].
I also wrote a followup blog post with more detail on the current state of DRM options on the web [2]. Spoilers: it's not great.
Regardless of all of these problems, I still hold an interest in browser development and have been working towards making Electron a viable option for building a browser [3].
[0] https://github.com/castlabs/electron-releases
[1] https://github.com/castlabs/electron-releases/discussions/24
[2] https://blog.samuelmaddock.com/posts/the-end-of-indie-web-br...
[3] https://github.com/samuelmaddock/electron-browser-shell