>>A DRM API in HTML5 harms users by legitimizing and enabling restrictive technology under the banner of the free and open web, with all the practical harm (lac

>>A DRM API in HTML5 harms users by legitimizing and enabling restrictive technology under the banner of the free and open web, with all the practical harm (lack of control, reduced bargaining power, security issues) that loss of freedom entails. In whose eyes does it legitimize it? Are you saying someone will be convinced that DRM is ok because it is in a web browser? >>If the framework is no different from existing frameworks, why do we need it? Because it is different. Native solutions are more likely to be faster and more secure than external plugins.