RagingNerdoholic

Web dev here. It enforces the original markup and code from a server to be the markup and code that the browser interprets and executes, preventing any post-loading modifications.

That sounds a bit dry, but the implications are huge. It means:

• ad blockers won't work (the main reason for Google's ploy)
• many, if not most, other browser extensions won't work (eg.: accessibility, theming, anti-malware)
• people are going to start running into a lot of scam ads that ad blockers would otherwise prevent
• malicious websites will be able to operate with impunity since you cannot run security extensions to prevent them
• web developers are going to be crippled for lack of debugging ability

These are just a few things off the top of my head. There are endless and very dangerous implications to WEI. This is very, very bad for the web and antithesis of how it's supposed to be.

TBL is probably experiencing a sudden disturbance in the force.

Ah yes, because "just following orders" has worked out so well in the past.

That's right, I just godwin'd this bitch.

But they do care about their money. Explain it in ways that will resonate with them.

Without ad blocking, they'll encounter "scam ads" that take over the browser and demand calling "support" that collects their credit card info and costs them hundreds of dollars in fraudulent charges. At the very least, it's a pain in the ass they have deal with by calling their credit card provider to cancel the charges.

Security extensions from antivirus/antimalware applications won't work and subject them to even more of the above.

Malicious "attestation" services can falsely verify unscrupulous websites as legitimate.

That's exactly what it will do. Don't believe the bullshit in their "non-goals" section, they don't give a fuck. If accessibility extensions happen to continue working (at least temporarily), it will be by accident, because they for damn sure aren't going to spend even a second on compatibility.

If it's something like a proxy server that pre-modifies the markup/code, then yes, I can see WEI interfering with that.

Such an abstraction, while unnecessary, should be possible, providing that Google doesn't forcibly prevent access to the final markup that coalesces (ie.: view source and web dev tools)

Web dev here. It enforces the original markup and code from a server to be the markup and code that the browser interprets and executes, preventing any post-loading modifications.

That sounds a bit dry, but the implications are huge. It means:

• ad blockers won't work (the main reason for Google's ploy)
• many, if not most, other browser extensions won't work (eg.: accessibility, theming, anti-malware)
• people are going to start running into a lot of scam ads that ad blockers would otherwise prevent
• malicious websites will be able to operate with impunity since you cannot run security extensions to prevent them
• web developers are going to be crippled for lack of debugging ability

These are just a few things off the top of my head. There are endless and very dangerous implications to WEI. This is very, very bad for the web and antithesis of how it's supposed to be.

TBL is probably experiencing a sudden disturbance in the force.

This is normal. Titles should be plain text.

we won't ever ever keep your pictures and stuff for the juiciest possible marketing fodder, we super duper pinky swear

Funny how webrips still exist literally everywhere. They built a 10 foot wall, so someone else just built an 11 foot ladder.

I'm still salty that they implemented video DRM (for Netflix, Amazon, etc.), but at least they're standing against this bullshit.

Thing is, RiF is working for me again and it's not patched.