CHROME (google) is planing to implement DRM (kinda) into their browser

looks like rendering adblockers extensions obsolete with manifest-v3 was not enough so now they try to implement DRM into the browser giving the ability to any website to refuse traffic to you if you don't run a complaint browser ( cough...firefox )

here is an article in hacker news since i'm sure they can explain this to you better than i.

and also some github docs

Explain Like I'm Five @lemmy.world

Malcriada Lala @lemmy.world

2y ago

What is DRM and why is Chrome doing a bad thing here?

196 12

You're viewing a single thread.

521 comments

There is already a manifest v3 compatible version of ublock origin so can someone explain to me how it gonna end ad blockers?
- That version can do much, much less.
  Edit: see my other comment here: https://beehaw.org/comment/727017
  
  Thanks will look into it
- Because that version of ublock is already less effective. The long play is ending ad blockers and this is another step to achieve those ends. If you can't see that then I'm sorry but it can't be much more obvious than it already is.
  
  Hmm I think I need to read more about Manifest v3 as it appears my knowledge of the topic is pretty limited to literally just "v3 will kill ad blockers", basing my understanding on a couple of comments and 2 news report videos is a bad thing to do, don't you agree
- uBlock Origin is already less effective when running in Chrome than in Firefox. For example, it can't detect CNAME cloaking on Chrome, while it can do that in Firefox. When Chrome finally enforce manifest V3, uBlock Origin will be even more neutered in chrome due to limited number of blocking rules.
  
  That's a pretty interesting thing to know! Thanks

521 comments