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.
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.
With most competing browsers and the content industry embracing the W3C EMEWEI specification, Mozilla has little choice but to implement EMEWEI as well so our users can continue to access all content they want to enjoy.
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.
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.
As long as this doesn’t impact Firefox, I don’t care…
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.
Google is the source of most of the funding to Firefox. Can go 100 to 0 anytime basically
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.
Removed by mod
I feel like that might trigger an anti-trust lawsuit somewhere.
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
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.
And that is almost a direct quote.
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.
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.
Removed by mod
It will impact Firefox.
deleted by creator