this post was submitted on 02 Mar 2025
781 points (98.2% liked)

Privacy

5040 readers
271 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
 

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.

(page 2) 50 comments
sorted by: hot top controversial new old
[–] homesweethomeMrL@lemmy.world 64 points 1 day ago

said Ajit Varma, veep of Firefox Product

Pack up your shit, and get the FUCK out. You're a fucking disgrace.

[–] rumba@lemmy.zip 47 points 1 day ago* (last edited 1 day ago) (2 children)

Given that this is a privacy community, I would think that it would go without saying, But I just like to point out, We should probably disable Firefox sync if were using it. Log out of Firefox accounts in the browser. Even if you're not giving them telemetry they have all that data.

~~You can use the x bookmarks sync plugin, Don't make an account with them just use the un-logged in plugin to backup and restore your bookmarks between browsers. On the upside it'll even let you copy bookmarks from Firefox derivatives to Chrome derivatives.~~

Go down a comment or two and use Floccus, Just converted it's wonderful

at their location. However the want it

[–] ninepointeight@lemmy.ml 26 points 1 day ago* (last edited 1 day ago) (1 children)

Hey, just wanted to point out that xbrowsersync hasn't seen updates for quite some time. I would suggest folks to read this discussion and to perhaps check out Floccus as an alternative.

Both Floccus and xBrowserSync have Android apps on the F-droid app store as well.

load more comments (1 replies)
[–] beeng@discuss.tchncs.de 19 points 1 day ago (11 children)

Alternative to FF Sync?

I Iove this shit. Send to devices, multiple devices, bookmarks, passwords..

load more comments (11 replies)
[–] Rubanski@lemm.ee 16 points 1 day ago (6 children)

"Flamed", that's a new one

[–] glimse@lemmy.world 31 points 1 day ago (1 children)

That's an OLD one. Wow I haven't heard that term in like 20 years

load more comments (1 replies)
load more comments (5 replies)
[–] Technotica@lemmy.world 29 points 1 day ago (17 children)

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

[–] lena@gregtech.eu 52 points 1 day ago* (last edited 1 day ago) (2 children)

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 18 points 1 day ago (6 children)

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

load more comments (6 replies)
load more comments (1 replies)
[–] TuxEnthusiast@sopuli.xyz 19 points 1 day ago
load more comments (15 replies)
load more comments
view more: ‹ prev next ›