• Mikina@programming.dev
    link
    fedilink
    arrow-up
    16
    arrow-down
    2
    ·
    edit-2
    1 year ago

    We know how it will impact Firefox. They will be deeply concerned with WEI and extremely opposing it, but will implement it anyway because they are forced to do it.

    It’s going to go exactly like this. Again.

    With most competing browsers and the content industry embracing the W3C EME WEI specification, Mozilla has little choice but to implement EME WEI as well so our users can continue to access all content they want to enjoy.

    And that is almost a direct quote.

    • StewartGilligan@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      2
      ·
      1 year ago

      Someone will most likely create a fork to remove this or an option to disable it will probably be baked into about:config. I don’t visit many sites that use DRM. When I do visit sites that require it, I’ll usually shift to Ungoogled Chromium or Brave.

      Another one of my major fears with this change is whether Google will decide to make Chromium closed source and the implications it can have for other chromium based browsers.

      • Mikina@programming.dev
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        1 year ago

        Someone will most likely create a fork to remove this or an option to disable it will probably be baked into about:config.

        But that’s the issue - if WEI passes, EVERY webpage will be able to use DRM. So, just like you have to switch to Chromium for DRMed media content, you will now have to switch for every website that has decided to implement it. So, your bank (because google is pushing it as a security feature), Youtube, Gmail… Just like you are not able to play DRM media, you won’t be able to visit DRMed websites without WEI API supported. It’s not something you turn off.