And since you won’t be able to modify web pages, it will also mean the end of customization, either for looks (ie. DarkReader, Stylus), conveniance (ie. Tampermonkey) or accessibility.
The community feedback is… interesting to say the least.
https://discuss.tchncs.de/post/1053698 - case develops.
I ditched Chrome about a year ago for Edge and just recently switched to Firefox, shouldn’t really be concerning as long as there are alternatives.
web env. integrity is not as bad as people make it out to be.
yeah I absolutely agree that it’s terrible and also a bad idea (we don’t need MORE drm in our browsers, I’m looking at you, Widevine (although firefox worked around it by running drm in an isolated container)), but it’s main purpose is to detect automated requests and effectively block web scraping with a drm system (it ensures two things: your useragent can be trusted and you’re a real non-automated user), NOT detect ad blockers. It doesn’t prevent web pages from being modified like some people are saying.
there’s a lot of misleading information about the api as it doesn’t “verify integrity” of the web page/DOM itself.
it works by creating a token that a server can verify, for example when a user creates a new post. If the token is invalid, server may reject your attempt to do an action you’re trying to perform. (this will probably just lead to a forced captcha in browsers that don’t support it…)
Also, here’s a solution: Just don’t use Chrome or any Chromium-based browsers.
Companies like google should really not have so much power. I have stopped using chrome 1 year ago, and i am thinking about switching to a browser that doesn´t use chromium.
If they overcome / disable ad blocking, they will lose browser market share - and people don’t design websites for marginal browsers with exotic features.
