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.
Queer individual from southeast Texas. Helping to work on the Linux desktop - currently contributing to Flatpak and Flathub, getting familiar with GNOME.
Can find me at:
https://orowith2os.gitlab.io/ https://tech.lgbt/@orowith2os https://github.com/orowith2os/ https://gitlab.com/OroWith2Os/
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.
you’re running a drm-compilant browser
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.
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.
That way should not be intrusive ads, and it shouldn’t be tracking without user consent.
On their own, exposed to the user in an easily understandable way and easily customizable, they’re not bad. They can even help; used right, you can get advertisements relevant to you and your interests, and developers can know what to improve on.
The problem is when this is abused to hell and back by companies that want to strip you of every penny they possibly can, without giving you the choice.
Possibly, but it sounds like a pain to work with, if I understand the technical details correctly.