How off notifications?

It works but you need to manually change the fingerprint at the right moments. Would be much better if it did provide a different fingerprint to each website, and then change again overnight or some such. If you forget to push the icon at some intervals, it's useless.

Nice protection, love what it does. But alas it's impossible to disable notifications, and more importantly to disable the very annoying sound !!!

Would be nice to have an option to disable notifications when a page is reading the fingerprint.

I'm very happy that it fuzzes my browser fingerprint, but I wish it didn't pop a notice every time a site attempted a fingerprint, because that's basically every site (through their ad networks if not themselves). That notification needs to be toggleable. It might be nice if there was a passive visual indicator instead...

hi
nice concept :)
Runs without problems on FF pre 57.

BUT with Firefox Quantum v57 update there are errors on Google Drive, Blogger.com and GMail !
Google sites seem not to be loaded now...
The deactivation of your add-on Canvas Defender solves it.

Perhaps it's only on my Win10 config.

It works so well that google is defending itself, by blocking its services when it's on. Good work guys. Now, we need that "disable here but fuck the others / ads" button....

Pas mal mais problème très gênant actuellement, il empêche le chargement de GMAIL en mode normal, obligé de le passer en mode classique.. => Je le désactive donc pour le moment

Visit https://panopticlick.eff.org or https://browserleaks.com/canvas. It lists the current canvas fingerprint for its image test. Exit Firefox (and check Task Manager there are no remnant processes for Firefox), reload Firefox, and visit the site again. The same Canvas hash is identified as before.

While a Canvas hash should remain stable within a session (to avoid getting fingerprinted as a Canvas blocking user), it does NOT have to remain stable between web browser sessions. A site that checks that a different hash is returned for multiple tries upon a visit can detect if a blocker is used. Those sites won't test upon a revisit of the page in a new browser session which could be from a different computer, different config, or different user.

Another Canvas blocker, CanvasBlocker, defaults on install to creating a new unique hash on every Canvas read. That isn't the best way to avoid Canvas fingerprinting. Repeated testing by a site when you visit them can detect you are blocking (changing) the Canvas hash so they know you are in a small populace of Canvas blocking users. However, CanvasBlocker has the option to change its random hashing on a per-session option. The hash remains stable within a web browser session but a different random rehashing is used in the next web browser session. Alas, CanvasBlocker is not a Web Extension add-on, there doesn't seem to be any movement to make it one, so it will die as of Firefox version 57. Already in Firefox 55 that add-on is getting flagged as "Legacy" meaning it is not a WebExt add-on and will cease to function shortly when Firefox 57 gets released.

So I was looking at an alternative. Canvas Defender has some nice features but the timer is deficient. The timer should function only *within* a web browser session, not at some wall-clock interval between web sessions. When the web browser is loaded, the timer should start anew (reset) with a new rehash or noise injection. The user might want to manually change the hash during a web browser session or let a timer do that during a web browser session but a NEW web browser session should start with a new random noise rehash of the Canvas reads. Every reset of the timer, which includes when loading the add-on in a new web browser session, should generate a new random noise injection.

Canvas Defender should reset and generate a new random rehash noise injection when the timer resets. When set to an interval, the timer resets when the interval is reached (and the timer starts measuring a new interval). When the add-on is freshly loaded (because it loads with a new instance of the web browser in a new browsing session), that is also a timer reset and the add-on should begin with a new random rehash noise injection.