|
|
|
|
|
by freehorse
722 days ago
|
|
The article itself [0] asnwers to this argument. > How did it get into the spec? Oh, it got into the spec because when the Content Mafia pressured W3C to include it, Mozilla caved. At the end of the day they said, "We approve of this and will implement it". Their mission -- their DUTY -- was to pound their shoe on the god damned table and say: "We do not approve, and will not implement if approved." [0] https://www.jwz.org/blog/2024/06/mozillas-original-sin/ |
|
At the end of the day, does it really matter? DRM extension is external and disabled by default on fresh install, and it asks to be enabled only once you encounter the DRM content. You can always say no if you deeply care about it.