Ironfox doesn't have privacy.resistfingerprinting set to true in about:config?
-
I noticed that the sites that have issues are the sites I should avoid.
After a while, you just don't need them if you are willing to make the changes needed to reduce that corpo exposure
Sites like my banks, and stores, and self hosted VTT games.
I've had issues with all. Not acceptable -
How come?
Idk why, it doesnt say anything on their gitlab about changing that. Maybe it is a problem with the build process? I remember on Mull a couple months ago i did a clean install and RFP was disabled. You can just enable it if you want.
-
This comment should be deleted soon
-
How come?
In my opinion you should enable it
-
How come?
We very publicly discussed our approach to fingerprinting and the reasoning for this. But a basic TL;DR is that we're using a hardened configuration of FPP - which matches all of RFP's targets, except the few known to cause breakage/be undesirable for users. I'd recommend reading that GitLab issue for a detailed explanation, and please let me know if you have any questions or concerns.
FYI: Arkenfox doesn't enable RFP by default anymore either, and LibreWolf is also considering switching to FPP with an approach like ours.
-
In my opinion you should enable it
We don't recommend enabling it; you can see our reasoning as to why we don't enable RFP here - we use a hardened configuration of FPP instead.
FYI: Arkenfox doesn't enable RFP by default anymore either, and LibreWolf is also considering switching to FPP with an approach like ours.
-
We very publicly discussed our approach to fingerprinting and the reasoning for this. But a basic TL;DR is that we're using a hardened configuration of FPP - which matches all of RFP's targets, except the few known to cause breakage/be undesirable for users. I'd recommend reading that GitLab issue for a detailed explanation, and please let me know if you have any questions or concerns.
FYI: Arkenfox doesn't enable RFP by default anymore either, and LibreWolf is also considering switching to FPP with an approach like ours.
Thanks!
-
Idk why, it doesnt say anything on their gitlab about changing that. Maybe it is a problem with the build process? I remember on Mull a couple months ago i did a clean install and RFP was disabled. You can just enable it if you want.
-
waterfox
Waterfox contains proprietary Google Play libraries, and doesn't include any hardening when compared to standard Firefox on Android. It's a completely different project with a different set of goals than IronFox or Mull.
You would be far better off using standard Firefox over Waterfox, in terms of privacy & security.
-
They changed some basics from Mull and decided to go other ways. That's why I'm not using thus browser
They changed some basics from Mull and decided to go other ways.
What
basicsdid we change, and why do you have a problem with them?IronFox still has the same core goals/mission as Mull: to provide a privacy & security-oriented Firefox-based web browser for Android. If IronFox isn't for you, that's completely fine - but I'm just perplexed by your reasoning here, and would appreciate any elaboration so that we can improve.
-
This comment should be deleted soon
Shitty of them claiming to follow Mull's legacy if they're doing their own thing.
How?
Our change in approach to fingerprinting was very carefully considered and discussed, both privately and publicly.
FYI: Arkenfox doesn't enable RFP by default anymore either, and LibreWolf is also considering switching to FPP with an approach like ours.
IronFox still has the same core goals/mission as Mull: to provide a privacy & security-oriented Firefox-based web browser for Android. If IronFox isn't for you, that's completely fine - but I just don't understand how this is
shittyor compromising Mull'slegacy/ideals. -
Ok, might want to make that more clear under the section about issues inherited from Mull which still mentions RFP.
Your explaination seems sound.
-
Maybe consider enabling RFP for private browsing. Is letterboxing enabled?
-
Ok, might want to make that more clear under the section about issues inherited from Mull which still mentions RFP.
Your explaination seems sound.
-
Yeah, we've been waiting to update documentation until our website is ready (since that's where we'll keep everything). You're right we do need to make this more clear.
Understandable, thank you for your (and contributor's) work on this project. I am happy that i dont need to compile this from source for each update.
-
We don't recommend enabling it; you can see our reasoning as to why we don't enable RFP here - we use a hardened configuration of FPP instead.
FYI: Arkenfox doesn't enable RFP by default anymore either, and LibreWolf is also considering switching to FPP with an approach like ours.
Thank you useful read
-
We very publicly discussed our approach to fingerprinting and the reasoning for this. But a basic TL;DR is that we're using a hardened configuration of FPP - which matches all of RFP's targets, except the few known to cause breakage/be undesirable for users. I'd recommend reading that GitLab issue for a detailed explanation, and please let me know if you have any questions or concerns.
FYI: Arkenfox doesn't enable RFP by default anymore either, and LibreWolf is also considering switching to FPP with an approach like ours.
Thank you for getting out of your way and explaining it here.
-
System shared this topic on
