3 ms·

> 1. Browsers do nothing to support DRM and sites like Netflix recommend people to just use a native app to experience the full Netflix experience. This weakens

> 1. Browsers do nothing to support DRM and sites like Netflix recommend people to just use a native app to experience the full Netflix experience. This weakens the open web by having sites leave the web and opt to move users to the mobile web instead. It would be easier if it was just Netflix using this crap like you imply. Nowadays, a good 10% of the websites have a popup "this page has DRM content, do you want to enable it?", I'm assuming it's used for advertising fingerprinting and malware even more than videos. So yeah, requiring a netflix app is an improvement on the current situation. > 2. Browsers adopt a closed standard for DRM. This weakens the open web because now a care use case of the web now uses a closed standard instead of an open one. DRMs aren't the open web, they are the closed web, regardless if there's a specification or not, that doesn't change a thing. And having an open specification for it lowers the cost of deploying them (as we've seen now, it's in a lot of places) which is bad.

NoGravitas 3y ago
The open specification doesn't really even mean much, because the specification covers how the DRM module interfaces with the browser, not compatibility between DRM modules. In practice, there is exactly one DRM implementation used on the web, and it is proprietary (Wildvine). You could implement another standard-compliant DRM scheme, but no one would use it; the value of the standard is basically nil.
- realusername 3y ago
  It still helps interfacing with Widevine, if the website had to tell each user to install a custom plugin, that would increase the work to do
charcircuit 3y ago
>So yeah, requiring a netflix app is an improvement on the current situation. If you are botherd by popups I'm sure you can disable them. I've never seen a popup asking me to enable DRM when I browse the web. >DRMs aren't the open web EME has a standardized javascript API for people to use. This is a public standard developed openly. >And having an open specification for it lowers the cost of deploying them (as we've seen now, it's in a lot of places) which is bad. Allowing copyright holders to have their hard work be protected is a good thing and allows for them to be willing to share them more if they can trust they won't be stolen from. Artists want control over how their art is used. Saying tough luck and that they should just deal with it being stolen is not productive and is ignoring their needs.

NoGravitas 3y ago

The open specification doesn't really even mean much, because the specification covers how the DRM module interfaces with the browser, not compatibility between DRM modules. In practice, there is exactly one DRM implementation used on the web, and it is proprietary (Wildvine). You could implement another standard-compliant DRM scheme, but no one would use it; the value of the standard is basically nil.

realusername 3y ago
It still helps interfacing with Widevine, if the website had to tell each user to install a custom plugin, that would increase the work to do

charcircuit 3y ago

>So yeah, requiring a netflix app is an improvement on the current situation. If you are botherd by popups I'm sure you can disable them. I've never seen a popup asking me to enable DRM when I browse the web. >DRMs aren't the open web EME has a standardized javascript API for people to use. This is a public standard developed openly. >And having an open specification for it lowers the cost of deploying them (as we've seen now, it's in a lot of places) which is bad. Allowing copyright holders to have their hard work be protected is a good thing and allows for them to be willing to share them more if they can trust they won't be stolen from. Artists want control over how their art is used. Saying tough luck and that they should just deal with it being stolen is not productive and is ignoring their needs.