Live data from Hacker News

A look at Firefox forks

lwn.net

281–290 of 390 posts

Re: A look at Firefox forks

#281

Earlier quoted context omitted.

The narrative you gave above is by definition not a first party source. Here's a first party source explaining your misunderstanding of the situation: https://blog.mozilla.org/en/products/firefox/update-on-terms... And here's another credible source explaining Mozilla's mistake in making this decision based on language that was only present in a draft version of the CCPA, as opposed to the final version, but which al…

Why do you trust everything the allegedly bad guys say? By reading it and thinking critically as you said we all should, I can easily see that they are following the pattern that many bad guys follow: write some legalese allowing them to do bad stuff, then write some non-binding non-legalese saying they won't. Then only point at the latter to silence complaints. And then, the next step in the pattern is to actually d…

Not much changed on Mozilla's side, only the law (e.g., CCPA, GDPR), because technically speaking (as far as CCPA is concerned), Firefox has already been “selling” users' data.

Furthermore, at this point, that legalese talks about features that the user expects. Otherwise, in the EU, Firefox would be forced to ask for explicit consent. GDPR is so strong that when Firefox will actually sell your data, you'll know it because in the EU it will have to tell users exactly how or why.

Note that Mozilla was already hit with a privacy complaint in the EU due to PPA [1] because it's opt-out instead of opt-in. Whether they'll be found guilty by EU's DPAs, it really depends on whether they actually anonymize that data, as they claim to do, or not. Note here that the GDPR doesn't accept pseudo-anonymization as being valid anonymization.

Of course, it may take a while to find the outcome of such complaints, just note that as far as the GDPR is concerned, that Privacy Policy of theirs doesn't count for squat. It really doesn't matter what they claim in their Privacy Policy, unless they are lying, i.e., if they actually “sell the data” of users in a way that users don't expect as part of the service, then the GDPR asks for explicit consent (opt-in).

Technically speaking, they've already sold user data since 2006 because they've been installing Google's Search as the default, used, for example, for search suggestions. So everything you type in that address bar, goes to Google, and they get paid for it. Of course, search suggestions are part of the service that the user expects, but note that the user's search history can also be used for user profiling by Google. So as far as the CCPA is concerned, that's selling user data. And, very importantly, Firefox has been funded by ad-tech since 2006, much like all Chromiums and even Safari.

What's actually new is that Mozilla wants to diversify. Which is good, as the Search deal is in jeopardy and those hundreds of millions of $ they need to fund the browser aren't going to come from donations. So they would like an alternative to cut the middleman, i.e., Google. If that alternative is also privacy preserving and at the very least opt-out (though I'd prefer opt-in), then that's even better than the status quo.

People unhappy with this deal are people that hate advertising, or any reasonable monetization strategy, as if a viable browser with an independent engine could be funded via the donations of people that ad-block YouTube instead of paying for Premium.

---

TLDR:

1. Nothing actually changed, and that Privacy Policy doesn't count for squat.

2. Results matter, not words, results such as that wonderful offline translation feature, which is a great showcase of privacy preserving AI tech that only Mozilla pulled ;-)

PS: Isn't it odd that whenever the underdogs get boycotted, the winners are always the Big Tech solutions that are far worse in every aspect?

[1]: https://techcrunch.com/2024/09/25/mozilla-hit-with-privacy-c...

Re: A look at Firefox forks

#282

Earlier quoted context omitted.

> The license could be structured so that only the user who compiles the code would be licensed to used it (general distribution would be prohibited). Firefox is already GPL'ed, such a license change would violate that (along with many libraries it depends on also being GPL'ed). This is not possible. Here at ardour.org, we use this: > either compiled binaries for a minimal cost or as free open-source code. (technical…

Firefox is under the MPL, not the GPL

Oops, thanks for the correction.

Re: A look at Firefox forks

#283
post #78

Earlier quoted context omitted.

Zen browser is exactly this. It has a growing ecosystem of “Zen mods” and has a great Arc-like out-of-box experience. https://zen-browser.app/

After a short time with it, I find it kinda funny. Back then, power users were up in arms about things like the omnibar, and chrome removing more and more parts of the actual URL. And here is a browser marketed at power users that goes beyond that, showing only a small fraction. There doesn’t even seem to be a Zen mod that restores a real usable URL bar. For me, I manipulate URLs every day, both for work and private…

> I manipulate URLs every day, both for work and private usage

Zen/Arc are actually much better for this use case, albeit after an adjustment period for people who’ve become accustomed to the way Firefox/Chrome do it.

The idea is that URLs are out of your way when you don’t need them and front-and-center when you do. Instead of simply focusing on the URL bar when you CMD+L or CMD+T, it brings up a modal dialog in the center of the screen where you’re free to do everything you can do in a normal location bar and more. It’s modeled after the command palette design in code editors or application launchers. So, for example, not only can you edit URLs, but you can search for commands instead of hunting for them in the browser’s menus. As an example, I’d never memorize the keyboard shortcut to take a whole-page screenshot because I don’t use it enough. But the other day I needed it, so I typed “CMD+L, screen” and it was the second result. Task completed in under 2 sec.

It took a few days to get used to, but now I never want to go back to the sort of location bar that Chrome and Firefox use. It just takes up space that I’d rather devote to the sites I’m visiting. Even the tab pane is easily toggled to get out of my way when I don’t care about it, which is especially useful when I’m tiling websites. I’ve developed a fondness for keeping documentation open in one panel alongside the website I’m developing, which means recapturing the width I lose from the tab pane is valuable.

I highly recommend pushing through the awkward phase where you’re sure you’re going to hate this browser design. Because once you get past it, you’ll wonder how you ever thought the old way could be better.

Re: A look at Firefox forks

#284

Earlier quoted context omitted.

The narrative you gave above is by definition not a first party source. Here's a first party source explaining your misunderstanding of the situation: https://blog.mozilla.org/en/products/firefox/update-on-terms... And here's another credible source explaining Mozilla's mistake in making this decision based on language that was only present in a draft version of the CCPA, as opposed to the final version, but which al…

Why do you trust everything the allegedly bad guys say? By reading it and thinking critically as you said we all should, I can easily see that they are following the pattern that many bad guys follow: write some legalese allowing them to do bad stuff, then write some non-binding non-legalese saying they won't. Then only point at the latter to silence complaints. And then, the next step in the pattern is to actually d…

First of all, while many valuable perspectives are offered here, the legal nuances of the CCPA are complex and usually best assessed by those with formal legal expertise. It seems to me that individuals without legal training are the primary source of the allegation, so I believe that allegation itself needs to be taken with a grain of salt, as those making the accusation are quite possibly missing key legal context. This isn't intended as an insult, rather, just an objective observation from my perspective. Please ask a lawyer or law school friend to review all of this, including both the blog post and other HN post I linked above, as well as the links in that HN post, which include a law blog citing the drafting error. I encourage everyone with legal expertise to review these points and share additional insights. I am offering numerous, reputable, cross-checked sources for my position, something I haven't seen or heard from the people arguing for your position. If you have more information to share, please do share it. I want to have as holistic an understanding as possible here, after all.

Second, Mozilla as an entity has a lengthy track record of being the only big good guy in the "browser wars" for a long time. The entire ethos of Mozilla - both the foundation and the corporation (not the same business entity, another detail the many voices weighing in on this subject aren't even aware that they didn't know, but which is directly relevant to the legalese of the CCPA) - was to preserve a free, open-source, less untrustworthy major browser, in the face of IE and Chrome, both products of companies have taken a more opaque approach to their proprietary code and have been involved in decades worth of controversial experiments on (and changes to) user privacy, unlike Mozilla. Microsoft and Alphabet (Google) want to hide their code from you because their code contains a bunch of functionality that is optimal for the business' interests, but malicious from the perspective of end users who value privacy, freedom, and their right to determine what code runs on their own machine.

This brings me to my third point, that Mozilla's Firefox is COMPLETELY open source. If Mozilla was trying to slurp up user data to sell it, they wouldn't keep their product open-source, because the community would just strip out all the bits they don't like. Contrast to Alphabet (Google), who are literally deprecating Manifest V2 to prevent the community from developing ad blockers that actually block all ads, or Microsoft's documented historical practice of waging war on open standards through "Embrace, Extend, Extinguish". Lengthy, obvious, and well-documented patterns of abuse like that exist for both Microsoft / Alphabet (Google). Contrast to the lengthy pattern of standing up against that very same abuse from Mozilla. Keeping Firefox open source is antithetical to the interests of an entity which was trying to surreptitiously slurp up user data the way Microsoft and Alphabet (Google) do. While each organization has merits of their own, the availability of transparent, open source code (specifically, for the final product - not just an open core like Chromium) can help ensure that power users and developers like us have ways to verify and challenge any potentially problematic practices - something that Mozilla has remained committed to, but which Microsoft and Alphabet (Google) had never fully embraced to begin with.

Fourth, If you've read Firefox's blog posts, if you've read the discussion I linked to above, if you've read the articles about the CCPA drafting error, if you've read the Wikipedia article, confirming that it did contain the incorrect draft language, if you understand that lawyers interpret everything legalistically (not the way ordinary people do), I believe this all paints a picture of an honest misinterpretation on Mozilla's part of the obligations the CCPA might put on them, in the least generous interpretation of the draft language of the CCPA. This does make me sympathetic to the possibility that Mozilla made an honest mistake, but sympathy and trust are not the same, which brings me to my fifth point below.

I'm not "trusting" anything Mozilla says. I'm reading into, understanding, and verifying all of it. And again, even if Mozilla was trying to do such a thing, their current open-source architecture makes those efforts completely irrelevant to developers like myself and many others here who can read, understand, and make modifications to, and rebuild from source. Given the established track record of Mozilla and the documented shortcomings with proprietary browsers in this regard, one might consider whether some of the criticisms (that are encouraging people to trust a narrative that results in a snap judgement against Mozilla without reading into the details) could be influenced by broader competitive dynamics. Nonetheless, it’s important to evaluate each claim on its validated merits.

This brings me to addressing your concerns directly: you make a perfectly valid argument in favor of remaining vigilant, and I support this! Keeping an eye on Firefox source code modifications, monitoring the situation over time, and so on. These can be done while simultaneously assuming Mozilla made a genuine mistake here, and isn't secretly plotting against our interests. The narrative that Mozilla has suddenly turned evil is broadly inconsistent with Mozilla's lengthy track record of standing AGAINST such abuses from Microsoft and Alphabet (Google). That narrative alone is also NOT a reason to spread FUD about a browser that, as of this moment, remains WAY more trustworthy than the "main" alternatives that most uninformed users would migrate to, should they leave Firefox.

A good-faith, open, evidence-based discussion is key to ensuring our whole community understands these complex issues, and I'd accordingly invite you to share more evidence to support your interpretation, which I will read and consider in good faith.

Re: A look at Firefox forks

#285
post #180

The problem with Firefox forks I have: - you don't know when they are gonna keel over and die. - non-existent support from distro package repositories. Void Linux for example has an understandable policy of not providing Firefox and Chromium forks. I really don't wanna install them from appimages or fatpak. I have found using firefox provided by my distro with something like arkenfox to be a decent medium but it suck…

> you don't know when they are gonna keel over and die

Would it really matter? Browsers are pretty much a commodity item. Of all the big pieces of software in your life, I can't imagine one easier to replace than a browser.

Re: A look at Firefox forks

#286
post #16

The browser engine landscape presents an interesting paradox: we have an open specification, yet multiple implementations with their own quirks and incompatibilities. This seems to undermine the very purpose of standardization. Consider our current situation: - The spec is largely influenced by the same big tech companies that develop the engines - Major engines (Blink, WebKit, Gecko) are all open source - Significan…

Because reference implementations are often less efficient. If the standard exists as an abstract interface then future implementors can make different tradeoffs.

[deleted]

Re: A look at Firefox forks

#287
post #73

Earlier quoted context omitted.

I don't disagree, and yes, you make a good point, and I added that the interests of Google and Microsoft coincide, which is also bad for us. The banning of ad-blockers, for instance, is also in the interest of Microsoft.

I think Microsoft just doesn't care about ad-blockers. They probably don't have a strong position on it. If they work it's fine for them, if they don't its also fine. They need to ship a good browser with Windows, because a lot of their enterprise customers rely heavily on web applications. A lot of Microsoft enterprise applications are browser apps. The purpose of Edge is not primarily web browsing.

I don't think we should guess.

In 2024, Microsoft generated 12.58 billion dollars in revenue from advertising, which is nothing to scoff at.

And we also have to look at future opportunities — the share of the advertising market may be small, but they represent THE alternative to Google's ads, including on all alternative search engines.

If they aren't concerned about ads or ad-blockers, then why are they so aggressive about pushing Edge on Windows users? And in the EU, when people first open up the Edge browser, why do they inform people that Edge will share their data with the entire advertising industry?

Re: A look at Firefox forks

#288
post #89

Earlier quoted context omitted.

Amazon equivalent in Poland - Allegro was notoriously blocking me in Librewolf; I was served puzzle captcha or blocked from browsing at all due to "suspicious activity" 98% of the time.

Try a spoofed user-agent, if disabling ETP and RFP doesn't help. Also, fuck companies that do this. I just start permanently deleting accounts whenever services do this.

> Also, fuck companies that do this. I just start permanently deleting accounts whenever services do this.

On the one hand yes, on the other - these times call for ditching US companies and switching to local (EU) ones. So it's better to tell these local ones to be more welcome / less hostile.

I have just yesterday asked Amazon to delete my account and all my personal data and stop processing it, quoting "Article 17 and Article 18 of the General Data Protection Regulation".

I'm also planning (as in: technically planning) to move all my data off AWS reasonably ASAP, too. It's personal stuff; mostly S3, domains registered and parked at Route53, some CloudFront distributions fronting static files, SQS/SNS - not much overall - and domains are the main PITA.

Re: A look at Firefox forks

#289
post #78

Earlier quoted context omitted.

Zen browser is exactly this. It has a growing ecosystem of “Zen mods” and has a great Arc-like out-of-box experience. https://zen-browser.app/

After a short time with it, I find it kinda funny. Back then, power users were up in arms about things like the omnibar, and chrome removing more and more parts of the actual URL. And here is a browser marketed at power users that goes beyond that, showing only a small fraction. There doesn’t even seem to be a Zen mod that restores a real usable URL bar. For me, I manipulate URLs every day, both for work and private…

Manual URL editing is unbelievably painful on mobile and all the kids only use their phones these days - I guess this includes all the cool kid engineers making browsers.

Re: A look at Firefox forks

#290
post #219
post #158

Earlier quoted context omitted.

It costs over $200M per year. That's a lot of paying users.

"Mozilla spends $200M on it per year" does not mean it costs $200M per year. Considering Mozilla overspends on everything else, it's not a stretch to think they might be overspending on this too.

> Considering Mozilla overspends on everything else

That something is repeated endlessly does not make it true. In fact, it's a signal of disinformation (which doesn't make it false). And when words are used like "everything", it suggests 'nothing' specific is really known. And even to the degree it's true, the inference is weak; the question is, how much does web browser development cost?

$200M seems reasonable to me. Comparisons I've seen make it quite a bit less than estimates of Google's costs, for example.

Post reply on HN