• AbidingOhmsLaw@lemmy.ml
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        1 year ago

        FireDragon (my understanding is that FireDragon is built from LibeWolf) and LireWolf is a custom and independent version of Firefox, with the primary goals of privacy, security and user freedom. LibreWolf (and FireDragon I assume) is designed to increase protection against tracking and fingerprinting techniques, while also including a few security improvements.

        I don’t use either, I use just firefox so maybe a user of FireDragon could give you more.

        Edit: Take a look at Jao’s post again, he updated it with more info on FireDragon.

      • Da_Boom@iusearchlinux.fyi
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        Idk, looking at the code, it doesn’t look like it does much other than preinstall some useful add-ons and also remove some search providers, among Other privacy things - it also Reskins the about page, code wise there’s really nothing different - It’s like setting privacy to higher than max.

        Best to look through the code to see what it does before you use it. Just a brief skim I’ve noticed that for some reason it disables WebGL. Not sure why, it doesn’t specify a reason. It could completely break some websites.

        • setVeryLoud(true);@lemmy.ca
          link
          fedilink
          arrow-up
          5
          ·
          edit-2
          1 year ago

          WebGL can jeopardize your privacy on some untrusted sites by revealing your hardware specs, allowing sites to fingerprint you easier. The TOR Browser does it for the same reason.

        • Venia Silente@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          1 year ago

          Not sure why, it doesn’t specify a reason. It could completely break some websites.

          It’s 2023 and Firefox still does not have a per-site / per-domain toggle for WebGL, so it’s on them. It stays disabled on my end, and if a site requires it I just open a temporary tab in a different profile with WebGL enabled.