@soferman
link
5
edit-2
6M

deleted by creator

Elbullazul
link
26M

In the 2nd paragraph:

But it plans to retain the blocking webRequest API that’s among the most consequential casualties of the technical transition in Firefox, at least until there’s a replacement more suitable to the web community than Google’s alternative, declarativeNetRequest (DNR).

Ephera
link
16M

It would be a first, if we couldn’t find some creative workaround, but yeah, fighting this war of attrition on our enemy’s battlegrounds is obviously royally stupid.

@fatboy
link
-4
edit-2
4M

deleted by creator

Elbullazul
link
106M

Mozilla keeps up with Google’s spec to reduce the amount of work to adapt extensions to work on Firefox. Google changed their spec and Mozilla is following it minus the ad block nerf. How is that supposed to make money for Google?

@pinknoise
link
8
edit-2
6M

The comment was probably about mozilla getting money from google. But I think google couldn’t care less.

For Mozilla this is kind of a win-win situation. Extensions have to be modified anyways to support chrome, the new format actually improves security and they will have a clear advantage over chrome because adblock isn’t a nice-to-have feature but an actual requirement for a modern Webbrowser.

also it’s not like they have many options unless they want to transform both browsers into some incompatible thing which needs its own developing structures to work

A place to discuss the news and latest developments on the open-source browser Firefox

  • 0 users online
  • 5 users / day
  • 8 users / week
  • 42 users / month
  • 121 users / 6 months
  • 1.94K subscribers
  • 202 Posts
  • 964 Comments
  • Modlog