• edric@lemm.ee
      link
      fedilink
      arrow-up
      22
      arrow-down
      1
      ·
      1 year ago

      The problem is they have the lion’s share of users, so they can force websites to adhere to their policies and those sites will stop working in FF.

      • baked_tea@lemmy.world
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        1 year ago

        Google is the source of most of the funding to Firefox. Can go 100 to 0 anytime basically

        • sexy_peach@feddit.deM
          link
          fedilink
          English
          arrow-up
          16
          arrow-down
          1
          ·
          1 year ago

          You’re assuming that this will kill FF instantly instead of them finding new ways to fund themselves. Not saying the situation is good, but it’s not that bad.

    • Pyro@pawb.social
      link
      fedilink
      English
      arrow-up
      20
      ·
      1 year ago

      The issue beyond them trying to change chromium to not have it but they are trying to make it so part of websites have the “security” built in as well

    • 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
        7
        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.

          • nanoUFO@sh.itjust.works
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            I’d be fine ditching youtube and gmail instead of having to use their shitty services with ads that lead to fake software that compromise your computers. Also my bank could try this, I would quickly turn into their most annoying customer also it could get to the point that unless you run a specific OS these pages won’t work and it would start being problematic legally for them. But until then I will pray everyday that the EU will take a hammer to WEI and break it’s legs.