1010
CHROME (google) is planing to implement DRM (kinda) into their browser
(lemmy.dbzer0.com)
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
💰 Please help cover server costs.
Question: Firefox renders certain DRM content in containers. Would that be applicable here? (Run unmodified site in container in background, load site content from that to user, and direct the attestor to the container so that the user can modify the site on the front end)?
The point of this is so that the user can't modify the site at all, despite what the proposal might say. Their goals and non-goals are contradictory.
Running this content in a container will not protect you. Just don't even try to adapt to it. Reject it completely.
Doesn't not being able to modify it would also imply that the information can not be parsed? Thus this consept falls apart immediately as the information would need to be able to be parsed so that it can be rendered?
The browser would need to be allowed to parse it, as they're the ones displaying the content; it would imply, however, that adblockers and other extensions would no longer be allowed.