Chrome not proceeding with Web Integrity API deemed by many to be DRM - eviltoast
Back in July, Google's work on a Web Integrity API emerged and many equated it to DRM. The company announced today it's not proceeding...

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.

  • xep@kbin.social
    9·
    1 year ago

    Since Android Webview is Chromium, this reads to me like it’s making it into Chrome anyway.
    It’s behind some restrictions, but now that it’s deployed Google can

    1. test it in live environments, making sure everything works
    2. more easily enable it for Chrome proper with fewer to no restrictions
      They’ll probably do this in the future using a staged rollout similar to what they did for Youtube and adblockers.

    The fact that it’s making it into production means the only concession Google made was admitting that they know that some of us vocally oppose it.
    I’d continue encouraging friends and family to use Firefox.