-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggesting an another approach #338
Comments
The relaxed branch aims to be pretty much what you described. Compatible and less breakage that is. |
I didn't see that, thanks. But the download link is the same with the original version? Please update it. |
I didn't go through the main page before trying it on my own Firefox profile, I lost all of my browsing history. Luckily I have a backup a few weeks ago. The relaxed version isn't that "relaxed". There is still a lot of work before I can deploy Firefox with a custom user.js. |
It is built as a boilerplate with every hardening option enabled, so yes. The issues should all be listed in https://github.com/pyllyukko/user.js#known-problems-and-limitations though, so it should be easy to change corresponding settings. If you find an issue not listed, please report it.
@Tunguyen6 The relaxed branch is also too strict for me, so I changed a few things in my own variant. The goal is to enforce as many hardening options as possible without bothering the user with unusual browser behavior. I've started porting some of these changes here, but it takes time.
To save you time you could either pick what you like in master...nodiscc:dbu (
Sent a patch #339 |
Either use relaxed pyllyukko's user.js on a fresh profile or stay conservative with a webextention like https://addons.mozilla.org/firefox/addon/privacy-settings-webextension/ |
I'm personally quite happy with the strict settings, many of these are not even implemented in Tor Browser. Keep up the great work! Recommend closing the ticket as it was already answered. 👍 |
Thanks! 😊
True that. |
The problem is the user.js file causes many compatibility issues, so it cannot be deployed in mass (casual users, organizations). Therefore we would leave Firefox user.js alone or worse is that the users would use Chrome! That defeats the purpose. At personal level it also causes a lot of inconveniences. If I wanted a really high level of privacy I'd use Tor Browser instead, which leads to point number 2.
As mentioned in issue #316, with respect, I think it's a waste of time, I doubt the hardened Firefox is better than Tor Browser (with or without Tor), the more this projects progresses, the more it becomes like Tor Browser. It's not worth it.
Let's build a user.js file and other presets (such as add-ons) that balance between privacy and compatibility, and lean more to compatibility and user experience, that can be deployed in mass. This project still holds values, so what I'm suggesting is another project with that approach.
What are your thoughts?
The text was updated successfully, but these errors were encountered: