• ulterno@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    2時間前

    Hi, I am here to tell you that it is not particularly trivial to make the kind of changes required to make the websites keep working while also preventing stuff similar to JS fingerprinting.
    Some extensions do a decent job in certain cases, but the only ones that completely fix the problem are the ones that simply turn off JS. I checked out what Librewolf’s changes do, using amiunique.org and in some tests it even ends up increasing the uniqueness.


    You will essentially require identifying different parts of the JS engine that expose said vulnerabilities and then creating mitigations for each of them, with either the “blend in” or “randomise” strategy and will also require to make sure they are not detected over any domain (due to partial overlap of either change).

    This kind of change for a single person will require properly understanding the JS engine codebase and then making and maintaining all required patches over the course of the fork as the main project goes forward. This is pretty much a full time job.
    Even if multiple people are working on it, one would still require a good understanding of the codebase.

    I suggest recruiting one of the retired/laid-off Firefox engineers, if you have the funds.

      • ulterno@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        2時間前

        The application of age indication is just going to be another metric that these companies use for fingerprinting and person identification, one that some analyst on their inside possibly considered a useful data point.

        And while this particular API might be an easy one to target, for removal as a patch, it might end up being part of a JS framework that many websites use and will break in case the return value is not available.

        So if people require sites to work, this will become just another feature, requiring similar mitigations to other JS features I mentioned, that will need to be handled in a way that it increases the anonymity of the user, lest the user be subjected to harassment.


        By “harassment”, I mean the actual inescapable kind, not just random internet trolls.

        • artyom@piefed.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          2時間前

          The application of age indication is just going to be another metric that these companies use for fingerprinting

          As I said, there’s nothing to suggest they would receive such an indicator, as far as I’m aware. The indicator is only required between the app store and the OS.

          • ulterno@programming.dev
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            2時間前

            Facebook has “apps”, no?

            Last I checked, it had stuff like FarmVille, FrontierVille, etc.

            • artyom@piefed.social
              link
              fedilink
              English
              arrow-up
              1
              ·
              1時間前

              We weren’t talking about apps, we were talking about Facebook like buttons on websites.

              • ulterno@programming.dev
                link
                fedilink
                English
                arrow-up
                0
                ·
                1時間前

                Causation:

                1. FaceBook website has apps
                2. FaceBook website is an App store
                3. FaceBook website requires access to Age API
                4. Firefox needs to passthrough Age API to Facebook’s domain
                5. All embedded FaceBook buttons now get to see your OS’s age