FingerprintingJS is used by some of the major sites such as Yahoo, ebay, Target, Western Union amongst many other big enterprises.
I use different fingerprinting blocking addons from Chrome store to resist fingerprinting and it seems to work well with FingerprintingJS as well.
Even the “strict” mode to resist fingerprinting in Brave browser does not seem to work accurately, (presumably) because fingerprintjs is quite easily able to revert the “farbling”: https://fingerprintjs.com/blog/audio-fingerprinting/
The farbling modifies the original Blink AudioBuffer by transforming the original audio values.
Reverting Brave standard farbling
To revert the farbling, we need to obtain the fudge factor first. Then we can get back the original buffer by dividing the farbled values by the fudge factor
It seems that fingerprinting blocking will probably continue to be a game of cat and mouse for quite some time.
Just as an example, we haven’t even talked about external protocol flooding (schemeflooding) vulnerability that creates a unique fingerprint across multiple browsers. Perhaps, many people take for granted that cross-browser tracking is not possible; at the time of writing this post, this vulnerability seems to be able to generate a unique fingerprint across browsers. I did a quick test in Firefox and Brave and my fingerprint was unique across both browsers. On the surface it does look like an easy (relatively speaking) vulnerability to fix, I am not a developer per se so don’t quote me on that!
The point I am trying to make is that fingerprinting blocking will be quite a difficult job for browsers at least for the foreseeable future.