-
There were proposals for protecting against this in the WEI explainer under "Open Questions" https://github.com/RupertBenWiser/Web-Environment-Integrity/...
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
People think it's about checking for ad block because protecting ad revenue is the very first concern the proposal addresses. The obvious path is that Chrome implements WEI and disallows ad blocking, and then Google gradually starts pushing websites to favor approved browsers that don't allow ad blocking. Perhaps they pay out a bit extra for "authenticated" ad impressions made using an approved browser. Or they could start suspending AdSense accounts for "invalid traffic" because a high percentage of visits have no WEI token or a token from an "unrecognized" browser. I'm sure you can imagine Google doing something like that: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
EFF clearly explains why the holdback mechanism doesn't make sense, and why the proposal authors' personal beliefs are not relevant. What matters is what capabilities this technology allows, and what Google's corporate motivations are.
-
Because I, for now, have the ability to make my computer say what I tell it to say, I have developed a small Firefox extension [1] that tells it what to say.
Silly? Yeah. Petty? Yeah. But sometimes it feels good to exercise your rights.
[1] https://github.com/rogual/wei-gfy
