1641
Chrome not proceeding with Web Integrity API deemed by many to be DRM (9to5google.com)
submitted 2 years ago by to c/technology@lemmy.world
240 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent