1010
CHROME (google) is planing to implement DRM (kinda) into their browser
(lemmy.dbzer0.com)
looks like rendering adblockers extensions obsolete with manifest-v3 was not enough so now they try to implement DRM into the browser giving the ability to any website to refuse traffic to you if you don't run a complaint browser ( cough...firefox )
here is an article in hacker news since i'm sure they can explain this to you better than i.
and also some github docs
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.
NO, that's not the case.
it doesn't prevent that. did you read that misleading post? All it checks is thay you're running a drm-compilant browser by providing a special token (signed by your device's id and real name from google account) which can be verified by the server.
of course that means that Firefox users will get a worse experience (more captcahas, or get completely blocked) on websites that use this new api.
They also don't want users to be able to use adblockers, that isn't all they're checking for. So this absolutely is the case. Their entire proposal is contradictory.