766
submitted 1 day ago* (last edited 1 day ago) by s38b35M5@lemmy.world to c/privacy@lemmy.world

The answer to "what is Firefox?" on Mozilla's FAQ page about its browser used to read:

The Firefox Browser is the only major browser backed by a not-for-profit that doesn’t sell your personal data to advertisers while helping you protect your personal information.

Now it just says:

The Firefox Browser, the only major browser backed by a not-for-profit, helps you protect your personal information.

In other words, Mozilla is no longer willing to commit to not selling your personal data to advertisers.

A related change was also highlighted by mozilla.org commenter jkaelin, who linked direct to the source code for that FAQ page. To answer the question, "is Firefox free?" Moz used to say:

Yep! The Firefox Browser is free. Super free, actually. No hidden costs or anything. You don’t pay anything to use it, and we don’t sell your personal data.

Now it simply reads:

Yep! The Firefox Browser is free. Super free, actually. No hidden costs or anything. You don’t pay anything to use it.

Again, a pledge to not sell people's data has disappeared. Varma insisted this is the result of the fluid definition of “sell” in the context of data sharing and privacy.

you are viewing a single comment's thread
view the rest of the comments
[-] Technotica@lemmy.world 33 points 1 day ago

Soo... where do we go now? What open source alternative exists that is on the side of its users?

[-] lena@gregtech.eu 69 points 1 day ago* (last edited 1 day ago)

Just keep using Firefox. Nothing in the code has changed, and if it does you can switch to forks. You all are evangelizing about how important FOSS is to prevent this exact scenario and yet you keep switching browsers for no need at all.

Note: I love Foss, I just think this is an overreaction

[-] cm0002@lemmy.world 19 points 1 day ago

Oh sure, but browsers are an entirely different beast.

Eventually, they'll take it closed source, now I know what you're thinking "Then one of the forks will just become the dominant one!"

But here's the thing, the browser engine is very complicated just to keep up with. The W3C spec that all engines must follow is thousands of pages long. So all those forks will wither and die once the engine has been cut off from upstream updates.

None of those forks touch the engine as-is

[-] lena@gregtech.eu 1 points 1 day ago

Do tell how something like Zen or Ladybird has a better chance at doing so. It would be better if instead of this fragmentation the Zen and Ladybird would work in a Firefox fork.

[-] cm0002@lemmy.world 23 points 1 day ago

Ladybird has some serious backing and employed developers working on their engine and has been worked on for years (Ladybird started life as the SerenityOS browser)

And even after all that time and money, it's still not even ready for general use. Their roadmap has them having a public release ready in 2028 iirc

And fragmentation? Really? LMAO there needs to be some competition in browser engines, if there was we wouldn't be in this mess to begin with.

There are only 2 modern, open source and fully working engines. Chromium and FF, that's not fragmentation, that's a duopoly

[-] lena@gregtech.eu 1 points 1 day ago

That's like calling Linux on the server a monopoly. It's open source, with many distros (forks). Anyone can fork the engine.

[-] coldsideofyourpillow@lemmy.cafe 5 points 1 day ago* (last edited 23 hours ago)

Distros are not kernel forks. Distros simply take the kernel, and bundle it with many utilities for the end-user. It is the equivalent of taking a puzzle set and assembling the pieces together. Sure, many distros maintain their own programs (such as a package manager), but it is an entirely different thing to maintain pacman than to maintain the freaking kernel.

[-] cm0002@lemmy.world 6 points 1 day ago

Anyone can fork the engine.

Even the Linux kernel is not as much of a beast that a browser engine is, I've seen estimates that a dedicated small team could build a new modern Linux kernel from scratch and generally usable in about 2-3 years

A browser engine takes years more, again, ladybird's engine is built from scratch, and it's currently in year 3 targeting an alpha release in 2026 or Year 4. With it projected to be generally usable in 2028 a full 6 years later.

And there are actually a couple different independent kernels, so no it's not a monopoly

how something like Zen

Zen is a Firefox fork.

[-] rumba@lemmy.zip 12 points 1 day ago

I mean, FOSS doesn't prevent this on its own. We should probably all switch to LW and try to keep an eye that those telemetry settings don't become disabled upstream.

Also of concern would be anyone using Firefox accounts and sync.

[-] QuadratureSurfer@lemmy.world 8 points 1 day ago
[-] Rose@lemmy.zip 17 points 1 day ago

Depends on where you stand on misogyny and transphobia.

[-] QuadratureSurfer@lemmy.world 13 points 1 day ago

I feel out of the loop on this one. Is there a particular individual on the project that this is about, or is this a company policy issue?

[-] Evkob@lemmy.ca 13 points 1 day ago

Essentially, someone submitted a PR on GitHub changing a "he" in the build instructions to a gender-neutral "they", to which the main dev of Ladybird (Andreas Kling) replied:

This project is not an appropriate arena to advertise your personal politics.


This next part's just my opinion; that's an insane response to someone suggesting neutral language. As a non-binary person, I wouldn't feel comfortable around this person after such a reply, and I certainly wouldn't donate to Ladybird or anything of the sort.

That being said, we all likely use tons of software developed by people way worse than Kling. As long as it's FOSS and is privacy-respecting, I'll run code that's been written by bigots. However I definitely won't support them by recommending their software to others, or by donating time or money to the project.

[-] mke@programming.dev 5 points 1 day ago* (last edited 20 hours ago)

I don't think that's just opinion anymore, it's a fairly accurate analysis. Countless serious projects use pronouns and "they," and that's fine, but for these few specific groups they're somehow political and a bad thing.

I've heard Andreas' twitter likes were telling, before those went private, but that information's out of reach now. That said, I've seen the people who frequently interact with him there, and I wouldn't feel comfortable around them either. He seems to really like it, though. Make of that what you will.

Still, good point on the reality of "moral software use." For all its issues, I do hope Ladybird succeeds as a new browser engine because the internet needs more of those. I'm just not touching it unless they get their shit sorted.

[-] possiblylinux127@lemmy.zip 1 points 1 day ago

Honestly it seems blown way out of proportion. You are leaving out the part where he said he thinks that they sounds weird. I believe he is still open to rewriting the docs to not use pronouns at all

[-] mke@programming.dev 7 points 1 day ago* (last edited 1 day ago)

You are leaving out the part where he said he thinks that they sounds weird.

That doesn't help. Also, his main reason remains "keep politics out of my project," completely missing the point that his stance is also political. It's the old "my politics aren't political because they're normal."

I believe he is still open to rewriting the docs to not use pronouns at all

That's even more political, and ridiculously so. Linux kernel docs refer to users as "they." Should they change it? Are they bringing in unnecessary politics into the sanctity of one of the world's greatest collaborative technical projects? Are they too fucking woke?

[-] possiblylinux127@lemmy.zip 1 points 4 hours ago

Documentation shouldn't have pronouns since that's the wrong tone

I think the dev probably just hasn't been exposed much to transgender people. Reacting with hate immediately doesn't help at all.

[-] oxideseven@lemmy.ca 12 points 1 day ago* (last edited 23 hours ago)

There is a link on another FF post to GitHub where someone changed "he" to "they" in the documentation. All references to a user being able to do anything in the documentation only uses "He".

The main dev told them to "keep their politics to themselves" and refused the fix.

[-] pumpkinseedoil@mander.xyz 2 points 1 day ago

In which context? If it was referring to a man I get why he'd say that answer

[-] mke@programming.dev 3 points 20 hours ago

Parent comment says "a user." Reading the docs, it clearly wasn't referring to a man, but any user, as in "the average Lemmy user interacts with many instances, and they have the option to block those they're not interested in."

[-] possiblylinux127@lemmy.zip 2 points 1 day ago

I think that's a pretty cheap PR. Ideally it should be rewritten to not to use pronouns. The PR is low effort and feels like it was deliberately done for attention.

[-] mke@programming.dev 6 points 1 day ago

I think that's a pretty cheap PR.

And?

Ideally it should be rewritten to not to use pronouns.

Why? Linux kernel docs use pronouns and they, and they're fine. What's so special about Klingland that they need to keep pronouns out?

The PR is low effort and feels like it was deliberately done for attention.

Have you ever seen the piles of "good first issue" tags on github? Most newcomers start with simple changes, and documentation improvements are high up in being a user's first contribution. Do you have anything that suggests the person behind the PR had such intentions, beyond you thinking it's low effort?

[-] possiblylinux127@lemmy.zip 1 points 1 day ago* (last edited 4 hours ago)

I think it is overblown

Also we don't exactly have a lot of options

[-] Dimmer@leminal.space 6 points 1 day ago
this post was submitted on 02 Mar 2025
766 points (100.0% liked)

Privacy

5040 readers
301 users here now

A community for Lemmy users interested in privacy

Rules:

  1. Be civil
  2. No spam posting
  3. Keep posts on-topic
  4. No trolling

founded 2 years ago
MODERATORS