this post was submitted on 02 Nov 2023
1635 points (99.6% liked)

Technology

59605 readers
3435 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
1635
Chrome not proceeding with Web Integrity API deemed by many to be DRM (9to5google.com)
submitted 1 year ago by Bishma@discuss.tchncs.de to c/technology@lemmy.world
252 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
[–] SirQuackTheDuck@lemmy.world 7 points 1 year ago

I mean, Widevine is present in all browsers and actively used by Netflix for example. YouTube also uses this when you're watching movies on YouTube Movies.

Not running DRM on the majority of YouTube content is also likely due to the added cost of running such encryption (the encryption is usually on a per-customer level, not one key fits all) and the added bandwidth and computer cycles required. Not to mention that this might be a legal struggle with the content creators.