How come?

    • celenity@lemmy.zipEnglish
      0·
      1 month ago

      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 shitty or compromising Mull’s legacy/ideals.

  • Steve@communick.newsEnglish
    0·
    1 month ago

    If I remember, that setting is extremely aggressive, and breaks lots of sites. Firefox has by default, a more complicated and nuanced feature that works practically as well, without breaking everything.

      • Steve@communick.newsEnglish
        0·
        1 month ago

        In that specific regard, probably.
        I use Fennec. I’ve found the more security minded versions, tend to have problems with some site or another, and annoy me.

  • Undertaker@feddit.org
    0·
    1 month ago

    They changed some basics from Mull and decided to go other ways. That’s why I’m not using thus browser

    • celenity@lemmy.zipEnglish
      0·
      1 month ago

      They changed some basics from Mull and decided to go other ways.

      What basics did 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.

  • celenity@lemmy.zipEnglish
    0·
    1 month ago

    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.