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...

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.

  • xrtxn@lemmy.sdf.orgEnglish
    11·
    1 year ago

    You are probably behind a nat. I contacted my isp and they disabled it, since it works perfectly!

    • Keith@lemm.eeEnglish
      1·
      1 year ago

      What do you mean nat? For me there is an app with an option (apparently no other way) and it didn’t worj

      • xrtxn@lemmy.sdf.orgEnglish
        11·
        1 year ago

        Compare what your router reports as ip and compare what your public ip is. If its not the same then that means you are behind a nat(?)(or something else) and you can’t port forward now.