173
Unpacking Google’s new “dangerous” Web-Environment-Integrity specification (vivaldi.com)
submitted 1 year ago by ruffsl@programming.dev to c/programming@programming.dev
12 comments fedilink hide all child comments

Will accessibility tools that rely on automating input to the browser cause it to become untrusted? Will it affect extensions? The spec does currently specify a carveout for browser modifications and extensions, but those can make automating interactions with a website trivial. So, either the spec is useless or restrictions will eventually be applied there too.

you are viewing a single comment's thread
view the rest of the comments
[-] exussum@lemmy.world 5 points 1 year ago

Even if you were to diminish any valid reasons to not add this DRM feature, what are the actual reasons they think are pro consumer?

[-] odium@programming.dev 4 points 1 year ago

Harder for scammers/hackers iirc.

But this also makes it harder for devs to run tests.

[-] exussum@lemmy.world 2 points 1 year ago

How do you figure?

[-] odium@programming.dev 6 points 1 year ago

Saw some Google bootlicker on GitHub issues talking about how the policy will prevent a lot of automated stuff including bots and many hacker tools.

this post was submitted on 25 Jul 2023
173 points (97.8% liked)

Programming

17696 readers
127 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz