I think the logic here is that the code to deliver an ad is protected by copyright and your modification of that code is considered a derivative work that is protected under copyright law.
But that’s not what happens at the browser level.
The HTML code is sent, whole cloth, to the browser. The browser inspects the code, you know, to do browser stuff.
During this inspection, the code is put against the ad block rules. Nothing is modified. If the code violates some sort of logic, it doesn’t get rendered properly.
Hell, the opposite argument is probably more damning. Say you have this literal HTML:
<html><title>I use arch</title><p>
Btw
hello
World</html>
You could argue the browser is NOT showing your code the way you intended (e.g. “Btw hello World” being rendered though I’m not sure if spaces would be there or not).
At the end of the day, unless you send your webpage as an image, you can’t guarantee how the browser will render it.
You could argue the browser is NOT showing your code the way you intended
I don’t think that’s a good example because how line breaks are treated is defined in the HTML standard.
A better example might be “reader” mode on mobile browsers? Or that mode in Opera where their servers act as a proxy to compress images and reduce the amount of data required to load the website for slow connections.
Actually the default HTML form and button elements are good one. Chromium and Firefox have different default styles.
yeah, website code editing is not needed, blocking of resource loading and browser API editing is what is done, and of course attaching additional stylesheets. sometimes HTML “code” editing happens too, but that’s probably not that important.
also browsers are called user agents for a reason. they should be an agent of the user, not of website owners, for the purpose of communicating with the website on the behalf of the user
You could argue the browser is NOT showing your code the way you intended (e.g. “Btw hello World” being rendered though I’m not sure if spaces would be there or not).
and that shouldn’t be legally required either. for one the web standards were not developed as laws of a government, but there’s also software bugs and unspecified behaviors, website owners should never be able to sue browser makers for not showing their website exactly as they expected.
They are also including the “CSSOM” and “rendering tree” as part of what they consider subject to “unlawful reproduction and modification”.
So, according to them, the rendering tree is also part of their IP… which is bonkers, since it’s the browser the one who implements this and even different browsers (or different versions of the same browser) might actually have different rendering strategies, different trees… different CSS extensions (or omisions/deprecations), etc. You basically would be potentially violating their IP if you used any browser different than what they specifically might have had in mind (which we don’t even have a way to know for sure unless they clearly state it…).
It’s like a painter suing someone for using glasses and altering the lightwaves coming from their painting…
I think the logic here is that the code to deliver an ad is protected by copyright and your modification of that code is considered a derivative work that is protected under copyright law.
But that’s not what happens at the browser level.
The HTML code is sent, whole cloth, to the browser. The browser inspects the code, you know, to do browser stuff.
During this inspection, the code is put against the ad block rules. Nothing is modified. If the code violates some sort of logic, it doesn’t get rendered properly.
Hell, the opposite argument is probably more damning. Say you have this literal HTML:
<html> <title>I use arch</title> <p> Btw hello World</html>You could argue the browser is NOT showing your code the way you intended (e.g. “Btw hello World” being rendered though I’m not sure if spaces would be there or not).
At the end of the day, unless you send your webpage as an image, you can’t guarantee how the browser will render it.
People have confused HTML with PDF for a long time.
I don’t think that’s a good example because how line breaks are treated is defined in the HTML standard.
A better example might be “reader” mode on mobile browsers? Or that mode in Opera where their servers act as a proxy to compress images and reduce the amount of data required to load the website for slow connections.
Actually the default HTML form and button elements are good one. Chromium and Firefox have different default styles.
yeah, website code editing is not needed, blocking of resource loading and browser API editing is what is done, and of course attaching additional stylesheets. sometimes HTML “code” editing happens too, but that’s probably not that important.
also browsers are called user agents for a reason. they should be an agent of the user, not of website owners, for the purpose of communicating with the website on the behalf of the user
and that shouldn’t be legally required either. for one the web standards were not developed as laws of a government, but there’s also software bugs and unspecified behaviors, website owners should never be able to sue browser makers for not showing their website exactly as they expected.
They are also including the “CSSOM” and “rendering tree” as part of what they consider subject to “unlawful reproduction and modification”.
So, according to them, the rendering tree is also part of their IP… which is bonkers, since it’s the browser the one who implements this and even different browsers (or different versions of the same browser) might actually have different rendering strategies, different trees… different CSS extensions (or omisions/deprecations), etc. You basically would be potentially violating their IP if you used any browser different than what they specifically might have had in mind (which we don’t even have a way to know for sure unless they clearly state it…).
It’s like a painter suing someone for using glasses and altering the lightwaves coming from their painting…
also if you update the browser and the update uses new rendering code that does things differently, that would also result in a copyright violation.
simply, these things are intermediate “products” of the web browser, not of the web developer.