Why is AmIUnique always reporting a unique browser fingerprint with all APIs set to "block"?

[Gitoffthelawn]

This extension is impressive, and according to the readme, its intent is to "prevent websites from using some Javascript APIs to fingerprint".

I tried setting everything in the extension's settings to "block" and then going to https://amiunique.org/fingerprint

This caused that site to think JavaScript was disabled, so I allowed Navigator API (and kept all other APIs set to "blocked"). I then cleared all cache/cookies/local storage, closed the browser, and went to https://amiunique.org/fingerprint

The site indicated a unique browser fingerprint. Okay, no problem.

So I again cleared all cache/cookies/local storage, closed the browser, and went to https://amiunique.org/fingerprint

The site again indicated a unique browser fingerprint. Why would this be?

[Gitoffthelawn]

@kkapsner Any thoughts?

[kkapsner]

I think you need to dig into the details and check what changes when you dis-/enable CB. But as said here having a unique fingerprint is not a problem in general - only if that unique fingerprint stays the same.

That's why I advocate for the "fake" setting to change things up all the time.