768
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Mar 2025
768 points (100.0% liked)
Technology
63746 readers
4105 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
A big problem with such forks (same with packages made by Linux distributors) is that there is a delay between official FF release and the release of the corresponding update of the fork. 99% of the time this doesn't matter much but when there is a severe security issue, the patch needs to be available ASAP.
Past enshittifications of Firefox could be disabled by users. Users who know what to disable don't need such forks then.
I'm not yet clear what Mozilla even intends. Is it just an adjustment of language of things that are already in FF and can be disabled easily? If so, I just keep the following shit disabled and benefit from earlier update releases.
I have not dug too deep into it for now (especially if I end up changing browser), but even with everything in the preferences disabled, examining the content of about:config gives a lot of telemetry.whatever.enabled left to true, sometimes with names that do not seem to match any option given to the user. That's not a good look either.
And you cannot change those in the default mobile Firefox since about:config is disabled (by their claim that it may break stuff in the ui)
The issue is that Mozilla is actively hiding these settings. There's one (I forgot which one) that you can't find by searching for the title in the FF settings, you have to scroll to it yourself.
They are under "Privacy", just as I expected where they would.
🤷
Yes, you can disable the settings that are exposed to you with a checkbox. How about all the other that have no checkboxes and you can find by snooping around in either the code or about:config ?
Which are? Genuine question. I'm not aware of those either.
I'm not going to enumerate them, mostly because I did not keep track of which one was on and which one was off before messing all of them up. If you're curious, open "about:config" and search for "survey*.enabled", "collect*.enabled". Even with all settings disabled, some of them remains on, and they do cause traffic to the (documented) endpoints.
Dude, I'm not talking about the specific settings you've shown. There's more settings you should set regarding privacy, and (at least a couple of months ago) one of them wasn't appearing when searching for it.
Please be more specific.