Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by JulianMorrison on Tuesday November 28, 2017 @08:21AM
(#15796945)
EME is basically the new Flash Plugin.
[ Parent
| on HN ]
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by _jal on Tuesday November 28, 2017 @09:23AM
(#15797500)
Yep, and I will cripple it just like I did Flash.
Any site depending on EME will not see traffic from me.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by imhoguy on Tuesday November 28, 2017 @03:04PM
(#15800898)
But then you need to disable of WebAssembly too -- another DRM lobbied standard.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by steveklabnik on Thursday November 30, 2017 @07:53AM
(#15815331)
Could you elaborate on this? Wasm has nothing to do with DRM as far as I can tell.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by imhoguy on Friday December 01, 2017 @04:22PM
(#15827622)
Not directly, but encourages obfuscated binary blobs, like some DRM decoders and as a new complexity also new security challenges. It is come back to Flash, ActiveX or Java Applets. See top comments: https://news.ycombinator.com/item?id=10487713
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by steveklabnik on Sunday December 03, 2017 @07:28AM
(#15837304)
View source has always been a priority for the wasm folks, and it's supported a debuggable text-based format the whole time for this reason. It's also significantly different than Flash, ActiveX, or Java Applets.
Re:DRM’s Dead Canary: How We Lost the Web, What We Learned, ...
by josteink on Tuesday November 28, 2017 @09:28AM
(#15797539)
Sure thing. Except we were sold and promised cross-platform works everywhere DRM if we just included EME because “EME will be a standard”? Oops. How did that work out?
Guess saying “I told you so?” won’t do much at this point.