Agree with Fred - would like this to generate the profile automatically and a way to disable notifications (why not use a badge instead?).

This addon really works! Thanks for making this addon. But, can I request a new feature? Please add option to "Generate new noise every browser restart." That would be very useful for me. Please consider my request. I think that's a simple request. For now I will leave it with 4 stars. :)

I agree with suggestion to automatically create a new profile on each startup (each tab opening?)

Would REALLY like a way to disable the popup messages!!!

FF55.03 64
it's working as described
just if u can add an option to regenerate a new noise every session it would be perfect!

Canvas Defender blocked enter gmail!! the issue is on Firefox only. http://funkyimg.com/i/2x6A1.jpg

gmail will not load on linux while this addon is enabled

I've been really happy with how well this extension works, especially with the Alpha/Beta releases leading into Firefox 57. However, I just recently encountered the issue reported on 28 Aug where the web interfaces for some of our intranet appliances were broken when the extension is enabled. A whitelist would be a great addition while such issues are investigated.

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.

With the last updates this has become the best anti-fingerprinting solution so far, but could it be possible to add an option to don't receive a notification when a possible attempt of fingerprinting is detected?

As a preliminary side note, I find it "funny" that some users who seem to care about their privacy still use Google services, Gmail above all. Dudes, think again (if I may) and find yourself equivalent online services that do care about your privacy and respect it.
I may suggest the "De-google-ify Internet" campaign (https://degooglisons-internet.org/) among others.

Regarding Canvas Defender: after using it for a few weeks, I suddenly wondered about its license... After checking, it's apparently released under the BSD-2-Clause license (according to Mozilla) and its source code is "available" (by unpacking the extension xpi file I believe ?). But this is about all. Nowhere on https://multiloginapp.com/canvasdefender-browser-extension/ could I read anything relating to the license of this extension. I don't know what to think about this lack of clarity. So for the time being, I'll stop using this extension, until Gravity Development LLC clarifies that point (ideally, their FAQ should mention which license protects their extension and a license file should be enclosed in the xpi file).

Quelle surprise de découvrir certains sites prétendument "sérieux" pratiquer du canvas fingerprinting, grâce à cet addon. L'addon mérite quelques ajouts, comme une notification permanente sur l'icône (la notification "toast" disparait trop vite).

Sinon, vraiment bien.

If you are using any Google service - such as Blogger - and attempt to edit any WYSIWYG form, the page will not allow you to edit at the code level and with crash.

Google is fingerprinting ever time you enter such as subsystem! You will have to disable Canvas Defender when using such forms.

Was a real PIA troubleshooting all my extensions to see which one was making gmail unusable. You would think the dev would at a minimum test compatibility with gmail.

In use without issue since v1.0.6 (5 Stars!), 1.1.0 breaks google and several web sites so far. Need to whitelist mail.google.com, drive.google.com, etc. (merely google.com doesn't work). And bankofamerica.com as one example. It's too tedious to figure out a site needs it and then entering it manually. Reverting to 1.0.9. Thank you.

got error:

Current canvas noise hash
#
Last changed: (Scheduled change: )

did not show # and canvas.