this post was submitted on 03 Mar 2025
4 points (83.3% liked)
LibreWolf
3955 readers
1 users here now
Welcome to the official community for LibreWolf.
LibreWolf is designed to increase protection against tracking and fingerprinting techniques, while also including a few security improvements. LibreWolf also aims to remove all the telemetry, data collection and annoyances, as well as disabling anti-freedom features like DRM. If you have any question please visit our FAQ first: https://librewolf.net/docs/faq/
To learn more or to download the browser visit the website: https://librewolf.net/
If you want to contribute head over to our Codeberg: https://codeberg.org/librewolf
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Well, I don't know about OP, but MY purpose for using Librewolf is to have something that is not run by Mozilla and doesn't call home to Mozilla, has a strong contribution history, exists in nixpkgs, and can be fully configured in Nix Home Manager. Librewolf is the only fork that checks those boxes. The security benefits are just a nice side-effect when they fit with my workflow.
Noob here - How come browser extensions can be used in fingerprinting? Why is the fact that I have an extension shared with servers? Why doesn't a browser like Libre Wolf refuse to share this? Is it really ingrained in the we browsing process to pass that info back? It seems like it should remain on the client-side. I can see Google sharing it but why can't LibreWolf decide not to?
Got it, so it's not that the browser passes an extension list to the server, but the server could recognize an extensions impact on the page with local JS or something and then send that info home. Could that in theory be blocked?
If librewolf is just about low fingerprintability then I don't think I understand it at all. Thanks.