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

Technology

59673 readers
4253 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
[email protected]
[email protected]
L4s
enu
1643
Chrome not proceeding with Web Integrity API deemed by many to be DRM (9to5google.com)
submitted 1 year ago by [email protected] to c/technology
245 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
[–] [email protected] 1 points 1 year ago

I’ve tried running Replicant and degoogled Lineage OS on an old Samsung phone many years ago. The experience was a bit rough, but tolerable as long as you’re a tech enthusiast and willing to make some sacrifices. Back then it wasn’t quite acceptable to me, because my bank app didn’t work. Then they announced that they were going to phase out the old code paper, so authentication through a mobile app was seen as the only acceptable method going forward.