Live data from Hacker News

A look at Firefox forks

lwn.net

311–320 of 390 posts

Re: A look at Firefox forks

#311

I'm generally happy with the "original" Firefox. Just wished it played better with KDE Plasma, especially on Wayland. It ignores the window decoration settings among other things.

Go to Customize Toolbar, check "Title Bar" at the bottom - that gives a Plasma-native title bar with window controls.

Sure but then you lose the screen estate. I guess you can't have it all.

Re: A look at Firefox forks

#312
post #293

Earlier quoted context omitted.

You can't donate to Firefox anyway—you can only donate to the Mozilla Foundation, which isn't alowed to work on Firefox. The Mozilla Corporation owns Firefox, and money can only flow from the Corporation to the Foundation. So every donation that has ever been made to "Firefox" has actually gone to whatever random stuff the Foundation is working on this week and, yes, to the Foundation's CEO.

To be fair, Mozilla has come out with a lot of new services that have dramatically decreased their dependency on Google. They went from over 95% of their revenue being google royalties to less than 70% just in the past half decade

Still though. 70% is a lot to be dependent on Google for. And the way Google operates these days, I'm honestly surprised that their interest in Firefox remains.

Re: A look at Firefox forks

#314

Earlier quoted context omitted.

There’s an option under Settings > Look and Feel for a full length URL bar.

I had checked there before, just checked again, and I still only see an option for a smallish bar with the two floating options. Where there exactly?

Settings → Look and Feel → Multiple Toolbars or Collapsed Toolbar as shown in the screenshot[0].

[0]: https://i.ibb.co/BVmkmkLC/Screenshot-2025-03-15-at-12-34-26-...

Re: A look at Firefox forks

#315

Earlier quoted context omitted.

Would you expect a "privacy focused" browser to offer you networking disabled by default but the ability to enable completely unrestricted networking in the settings (you can install a plugin for CORS and the like if you want) or to natively provide the privacy controls you need to actually use the browser? If the latter, why is it different depending which attack surface you ask about? If the former, why not just ma…

> Would you expect a "privacy focused" browser to offer you networking disabled by default Obviously not, because at that point it can no longer be used to browse the web. (That said, "do no network requests" should be the default idle state of the browser until appropriate user interaction. Allowing CORS is also a horrible default but that ship has long sailed.) I also disable WebGL in my Firefox profile and this do…

Everyone is welcome to have their own definition of what browsing the web requires be supported but if it wasn't part of browsing the web it shouldn't be part of the browser you can enable in the first place. That it is part of the browser you can enable is why it should have privacy support by the same browser, not because I personally think it should be part of what browsing the web requires.

Re: A look at Firefox forks

#316

Earlier quoted context omitted.

Would you expect a "privacy focused" browser to offer you networking disabled by default but the ability to enable completely unrestricted networking in the settings (you can install a plugin for CORS and the like if you want) or to natively provide the privacy controls you need to actually use the browser? If the latter, why is it different depending which attack surface you ask about? If the former, why not just ma…

I have left WebGl disabled and do not miss anything so far (maybe in the future?). Just not my use case. Network disabled is a straw man argument. If somebody already has made the effort of creating an extension and maintaining it, why not use that?

If WebGL is a straw man to browsing the web why is the feature still included in the browser itself at all then? You certainly don't have to utilize every feature of the browser yourself but it is part of that browser nonetheless, it's just not a natively securable part.

Re: A look at Firefox forks

#317

Earlier quoted context omitted.

I tried Sidebery for a couple of months off the back of multiple recommendations and while it has some decent features, I found it surprisingly lacking in terms of basic features like "close multiple tabs". I also found it regularly would semi-regularly prevent me from clicking on tabs which was frustrating until I restarted the extension or Firefox. In the end I found good old Tree Style Tabs was better. I just wish…

I use Sidebery a lot and I'd like to know what exactly you mean by "close multiple tabs"? I currently drag with right click in Sidebery and then click close tabs in the popup menu, however I don't really like doing this way. How is it done in Tree Style Tabs?

Oh! As another Sideberry user thanks for sharing this. I usually Ctrl+click or Shift+click tabs before middle mouse clicking to delete all selected.

Re: A look at Firefox forks

#318
post #205

Not released yet, but honorable mention to ladybird: https://ladybird.org/

I am a bit confused by their moving from C++ to Swift instead of Rust. It sounds a bit Apple-first. I get that it ports to Linux okay, but will it be hard to make it work with Windows some day?

The main reasons were that Swift supports OOP and Rust doesn't (useful because web standards are object-oriented and it's easier to follow the specs when you can model them in your code), and that Swift supports C++ interoperability instead of just C interoperability like Rust (makes it easier to incrementally move to Swift in an existing C++ codebase).

Re: A look at Firefox forks

#320
post #233

For years I've thought of creating a "paid" Firefox fork that is _just_ Firefox rebranded, but otherwise the exact codebase. The money brought in would be used to pay an open source developer to work strictly on things intended to be sent upstream to the Mozilla Firefox. If nothing else, it would prove whether or not people are willing to pay for Firefox. The problem with Firefox currently is the organizational struc…

The fact that the Mozilla CEO makes over $6,000,000.00 per year is a complete betrayal of what Firefox was. How could anyone justify donating to Firefox knowing that so much of their money would be going to this one person?

[dead]
Post reply on HN