Live data from Hacker News

Firefox Now Available with Enhanced Tracking Protection by Default

blog.mozilla.org

51–60 of 278 posts

Re: Firefox Now Available with Enhanced Tracking Protection by Default

#52
post #7

I have two main computers. One has for continuity reasons the old version of Firefox, the other the new one. The old version is so much more usable that I find myself using that computer much more frequently. It is rock solid with 100's of tabs open, all my extensions work and without silly restrictions on what they can and can not do and it uses a lot less memory. It's measurably faster too. I'm all for progress and…

Please don't use old versions, for security reasons.

Re: Firefox Now Available with Enhanced Tracking Protection by Default

#53

Now if only the could fix firefox to not be the slowest and biggest battery draining browser on mac.

I believe this is related to using scaled resolution in macOS. https://bugzilla.mozilla.org/show_bug.cgi?id=1404042 I was able to achieve way better performance by changing this to `true` in `about:config`: gfx.compositor.glcontext.opaque Another note, performance seems way better when changing the following to `true`: gfx.webrender.all gfx.webrender.enabled If anyone with deeper understanding of these options has an…

I've heard of this bug on and off for years now. Clearly it's not important to the Firefox team that Firefox is a viable browser on mac. Every other browser / application seems to be able to work around/with the issues described except them.

Re: Firefox Now Available with Enhanced Tracking Protection by Default

#54

It sounds like this is similar to what Apple added to Safari two years ago ( https://techcrunch.com/2017/06/05/apple-adds-a-tracker-block... ), though I don't know the details. I will be excited for the day when Privacy Badger is an unnecessary extension.

Safari uses a machine-learning classifier algorithm to determine which third-party sites are trackers: https://webkit.org/blog/7675/intelligent-tracking-prevention...

Disconnect may or may not use M-L classifiers in their selection process, I don’t know.

Re: Firefox Now Available with Enhanced Tracking Protection by Default

#55

Earlier quoted context omitted.

I believe this is related to using scaled resolution in macOS. https://bugzilla.mozilla.org/show_bug.cgi?id=1404042 I was able to achieve way better performance by changing this to `true` in `about:config`: gfx.compositor.glcontext.opaque Another note, performance seems way better when changing the following to `true`: gfx.webrender.all gfx.webrender.enabled If anyone with deeper understanding of these options has an…

I've heard of this bug on and off for years now. Clearly it's not important to the Firefox team that Firefox is a viable browser on mac. Every other browser / application seems to be able to work around/with the issues described except them.

I took over a month away from other work I have to do to develop the planeshift crate [1] to solve this exact problem. On the WebRender side, tiling work is advancing quickly as well. OS compositing in WR hasn't landed yet, mostly because work has to be done on the legacy Gecko side to wrangle the Cocoa widgets properly, but it's not true that nobody cares.

[1]: https://github.com/pcwalton/planeshift

Re: Firefox Now Available with Enhanced Tracking Protection by Default

#56
The article starts with: "It’s been several weeks since I was promoted to Senior Vice President of Firefox, responsible for overall Firefox product and web platform development."

How is this relevant? Did Dave Camp's SVP appointment trigger these changes? Honest question, because this is the first sentence of the article and I'm having a hard time understanding why.

Tracking protection is great though. I hope Firefox gains market share again, I love the direction it's taking.

Re: Firefox Now Available with Enhanced Tracking Protection by Default

#57

Earlier quoted context omitted.

If I had to guess? Try disabling webrender on the new computer. Firefox is rolling this out by default but if your GPU sucks or has fucked up drivers for whatever reason it can cause severe performance issues. goto about:config and search for gfx.webrender.enabled and make sure it's set to false. EDIT: More info on the rollout https://www.ghacks.net/2019/05/20/firefox-webrender-rollout-...

Or update your GPU drivers to latest and see if that improves the situation, in many cases it does improve things. At least it did for me and a few people I know, it's not like there's a database out there where GPU bugs are tracked.

I believe the Firefox crash stats database includes both “is webrender enabled” and “what is your GPU” with crash reports, which likely relates to their choices for only enabling it for specific GPUs right now.

Re: Firefox Now Available with Enhanced Tracking Protection by Default

#58
post #34

I've dumped Chrome altogether since FF 67 was released. My only gripe is they still aren't blocking ALL ads, but regardless it's a way better user experience now than it ever was. Firefox 67 feels like a whole new beast compared to their older versions. If you haven't tried FF for a while I recommend doing so and I suggest trying it across multiple devices. The tab management, syncing, pinning and sending etc. across…

I'll second the multi device functionality. I use Firefox on desktop and iOS and all of my history, autocomplete, and tabs follow me and everywhere. It's incredibly convenient.

Re: Firefox Now Available with Enhanced Tracking Protection by Default

#60
post #7

I have two main computers. One has for continuity reasons the old version of Firefox, the other the new one. The old version is so much more usable that I find myself using that computer much more frequently. It is rock solid with 100's of tabs open, all my extensions work and without silly restrictions on what they can and can not do and it uses a lot less memory. It's measurably faster too. I'm all for progress and…

Please don't use old versions, for security reasons.

Sure... See this is the whole problem with upgrades: upgrades are supposed to improve things but more often than not they break things. In this case the fact that stuff would break was quite predictable. The options to continue to support the non-javascript based branch of FF with plug in support with security updates but for some reason the decision was made to totally ignore backwards compatibility and to forcibly migrate the userbase to a new version without taking into account the problems that would cause. In some cases those problems are substantial, and the security risk then is outweighed by the damage.

This is one reason why the software industry as a whole sucks, we just do not give a damn about the users.

Post reply on HN