Recent searches
Search options
So now a bit of the #hubbub around #Google's #Web #Environment #Integrity proposal has died down, let's see what we've learned...
Apparently, despite the author saying it's "only a #proposal", some code for this has already landed in the #Chromium repository. [1]
Even if you were willing to give them the benefit of the doubt before, this should pretty much stick a fork in it.
[...]
[1] I read about this on Fedi, but of course I can't find it again to link to it.
They have clearly worked on this, in #secret, to get it into the tree, with minimal #publicity. #Publishing the proposal in someone's personal Github repo, rather than in a #public place, is like Douglas Adams' "the notice was posted in the #lavatory in the unlit #basement where the #stairs are missing, behind a door with a 'beware of the #leopard' sign on it" situation.
This shows bad faith. They know this is bad for users, and tried to hide it as much as they could.
[...]
So as I initially said, I expect them to try to let the controversy die down, and then go forward with it. They don't expect anyone to keep up #resistance to this proposal indefinitely.
The only #solution I see at this point is for all the other #browsers based on #Chromium to step up and #fork it, so #Google doesn't have total #control and can't sneak #malware into it as they are trying to do here.
#Opera, #Brave, #Vivaldi, everyone else - you need to step up.
Forking Chromium would also let the new maintainer organizations plant a #flag and declare that the #BlockingWebRequest part of the extension API was here to stay. #Google is still trying to #kill that off with Manifest V3, specifically because doing so makes effective #adblocking impossible.