Hacker News new | past | comments | ask | show | jobs | submit login

I guess Mozilla could implement this and still allow the user to save the .mp4 in Firefox.

For DRM to be "effective" you have to control the client and not allow arbitrary implementations. Or what am I missing here?




The DRM stack is outside the browser.


How is that different from some binary-only browser plugin (with limited availability on platforms that the DRM vendor doesn't want to support)?

All it does is giving credibility to DRM ("but the W3C has a standard for that!")


But so what? The browser needs access to the picture to display it, so there is no way to prevent the browser from saving the picture to a file.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: