I think I understand why this is bad, but I am not confident in my technical understanding of the mechanics here. Will appreciate an explainer :)

cross-posted from: https://lemmy.dbzer0.com/post/978408

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

  • @reversebananimals@lemmy.worldEnglish
    19•1 year ago

    Code is like a set of Lego pieces you put together to make an app or website. Usually, you have to go to Windows’ house to play with Windows Legos, and you can’t play with Windows Legos at iOS’s house. If you tried to put a Windows Lego on an iOS Lego, they wouldn’t fit. This means that if you want to make something with Legos, you have to do it in their house and play by their rules.

    Website Legos are special. You can play with Website Legos at the public library, and any other kids who go to the library - a public place that’s always open to everyone - can play with Website Legos too. Even Windows and iOS can come to the library and play with Website Legos. No one gets to decide what Legos are allowed or who gets to play with them, and kids can build things together because their Legos fit together.

    What Chrome is doing is bad because they want to take all the Website Legos back to their house, and force every kid in town to come to their house if they want to play with Legos. That way, Chrome gets to decide who is allowed inside, and can ban any Lego shapes they don’t like from their house.

    We need to stop Chrome, because every kid deserves to play with Legos, and kids make much cooler things when they can all work together with a shared Lego set.