cross-posted from: https://discuss.tchncs.de/post/5707453
The Chrome team says they’re not going to pursue Web Integrity but…
it is piloting a new Android WebView Media Integrity API that’s “narrowly scoped, and only targets WebViews embedded in apps.”
They say its because the team “heard your feedback.” I’m sure that’s true, and I can wildly speculate that all the current anti-trust attention was a factor too.
Many said we couldn’t stop it. We, like many, applied pressure, and they backed the fuck off.
We have no room for complacency now though. Google cannot be allowed to dictate web standards. Firefox needs to eat into that Chromium market share. Never forgive. Never forget.
Hmm.
That was too easy.
That was just the first salvo. This proposal was a feeler: now Google has learned what they couldn’t get away with and they need to boil us frogs more slowly.
This will come back on the table. Less aggressive, less visible, but they won’t give up on it.
https://youtube.com/watch?v=neSzpvdKa5k
spoiler
A few months later: Somehow, the Web Integrity API has returned
Here is an alternative Piped link(s):
https://piped.video/watch?v=neSzpvdKa5k
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
So if I understand this correctly, it would be a way for websites to opt in to this tool that allows for the website (and google by proxy) to get a lot of information about you and your browser and if you use privacy tools it potentially will prevent you from using their website?
But doesn’t google use bots to crawl the web? I’m sure those get a pass, but they could shut down competitors doing the same thing, seems like an anti-trust suit waiting to happen.
Oh they’ll be proceeding with it, just quietly at some undisclosed soon date in the future.
Constant vigilance
