this post was submitted on 26 Jul 2023
29 points (100.0% liked)

ELI5

569 readers
2 users here now

Explain it to me like I am 5. Everybody should know what this is about.

founded 2 years ago
 

Non-techy here, I've been seeing a lot of posts about Google DRM shenanigans, but don't really understand it, and what's 'bad' about it.

ELI5 please thank you

you are viewing a single comment's thread
view the rest of the comments
[–] PathogenXD 26 points 1 year ago (10 children)

Right now, you go to a url, which has a server behind it. Your browser says, "I'd like the site!". The server gives you the site, and your browser shows you the site and runs it for you. When you run the site, you may actually make modifications to the site in your browser, blocking ads, doing some custom stuff with extensions, etc.

Now, Google is essentially bringing something into their browser that allows servers to block any modifications to the site as you run it. And servers may automatically block any browsers that don't support that feature. Basically, servers will be able to ensure that you run the app in the exact way they intend, without modification

[–] PathogenXD 17 points 1 year ago (1 children)

Oh, and why is bad: the server requires your browser to pass a check to see if it's going to run your code correctly (called an attestation). It asks a third party to do that check, which will most likely be Google. Guess which browsers are going to pass those attestations more easily? Chrome. The only possible benefit to the average person is that maybe this will make it more difficult for bot farms to access the web

[–] Wabbitsmiles 1 points 1 year ago

Is what you are describing similar to the experience of declining cookies on certain sites, and in turn, sites dont allow you to enter and redirect you to Google or a main page?

e.g. healthline.com

load more comments (8 replies)