News for hackers. Stuff that matters.
Re:Mozilla patches two use-after-free vulnerabilities (ab)us... by wizzwizz4 on Saturday March 05, 2022 @04:11PM (#30571911)
When Google wants a feature implemented in Chromium, it gets implemented, pretty much regardless of how buggy it is. When I want a feature implemented and Google wants it not implemented… tough luck.
Re:Mozilla patches two use-after-free vulnerabilities (ab)us... by weaksauce on Saturday March 05, 2022 @06:31PM (#30573104)
Just look at the most recent changes to webextensions that chrome is trying to do... basically solely to make ad blocking nigh impossible. That's why browser diversity matters.
Re:Mozilla patches two use-after-free vulnerabilities (ab)us... by moonchrome on Saturday March 05, 2022 @04:20PM (#30572009)
Is that different with Firefox? I haven't been paying attention in a while now but I constantly read complaints about UI changes - and Firefox has it's share of experimental features that ended up being exploited or abuse (asm.js comes to mind).
Re:Mozilla patches two use-after-free vulnerabilities (ab)us... by wizzwizz4 on Saturday March 05, 2022 @04:40PM (#30572175)
It's not much different with Firefox, no. I was making a point that browser monopolies are bad; the fact we only have three real browser engines (two of which are based on Konqueror) is a problem.

But at least Mozilla do a basic back-of-the-envelope “is this feature a huge security vulnerability” check before shipping. (Looking at you, <portal>.)

Re:Mozilla patches two use-after-free vulnerabilities (ab)us... by blihp on Saturday March 05, 2022 @06:30PM (#30573095)
Only in the sense that when Google wants a new web standard the Firefox devs need to be convinced before it happens there. That has stopped a few, but not all, user hostile things from becoming defacto standards over the years.
Re:Mozilla patches two use-after-free vulnerabilities (ab)us... by eternityforest on Saturday March 05, 2022 @04:25PM (#30572057)
When Google invents a feature I want, Mozilla writes a position statement on how it's evil and never implements it.

It's hard to get behind engine diversity when Mozilla is trying to take the web in a direction I don't really want.

Meanwhile Brave does the same thing, but with Cryptocurrency.

I wish we had an open source clone of Vivaldi.

Re:Mozilla patches two use-after-free vulnerabilities (ab)us... by bkberry352 on Saturday March 05, 2022 @05:26PM (#30572575)
What features are you referring to?
Re:Mozilla patches two use-after-free vulnerabilities (ab)us... by extra88 on Saturday March 05, 2022 @05:49PM (#30572760)
FLoC may be one that could be characterized as “evil.” I mainly think about APIs that extend beyond the browser, like USB or Bluetooth, that Firefox won’t do for security reasons.
Re:Mozilla patches two use-after-free vulnerabilities (ab)us... by eternityforest on Saturday March 05, 2022 @10:33PM (#30574796)
Those are the features I was thinking of.

FLoC seems to be pretty irrelevant to anyone not directly working on ad infrastructure, so I'm fine with Mozilla ditching that.