AudioContext Fingerprint Defender
Defending against AudioContext fingerprinting by reporting a fake value.
Defending against WebGL fingerprinting by reporting a fake value.
Review user movement across collected snapshots.
View collected rating snapshots from the latest 7-day window to assess rating stability.
Compare 1-day, 7-day, and 30-day net growth and growth rate.
Review publication date, version, supported languages, and crawl timestamps.
Review the store description, core capabilities, and common use cases.
WebGL Fingerprint Defender is a browser extension that let you easily hide your real WebGL fingerprint by reporting a random fake value.
According to many tech blogs, completely blocking WebGL API is not a good idea, therefore reporting a fake fingerprint could be the best solution to better protect your privacy. This add-on simply adds a small noise to the actual fingerprint and renews it every time you visit a website or reload a page.
With the browser's WebGL API, in general, two types of fingerprints can be generated. One with WebGL constants and the other with an image that is rendered with the WebGL API. This add-on can spoof both values at the same time.
To disable this add-on, please visit the extensions page in your browser and then click on the disable button. Please note that this add-on does not have any toolbar icon/button.
This extension is made in collaboration with the author of "Canvas Fingerprint Defender":
https://chrome.google.com/webstore/detail/canvas-fingerprint-defend/lanfdkkpgfjfdikkncbnojekcppdebfp
Inspect the latest comments and rating distribution.
Store average score: 3.5. The bars below are calculated from synced review text only, so they may be empty for extensions that have public ratings but no synced comments yet.
Review related products from the Chrome Web Store detail page.
Defending against AudioContext fingerprinting by reporting a fake value.
Defending against Canvas fingerprinting by reporting a fake value.
Defending against Font fingerprinting by reporting a fake value.
Have control over WebRTC (disable | enable) and protect your IP address.
Prevent HTML canvas element from generating a unique identification key to protect user's privacy
Your browser, your rules — your digital fingerprint, in your control.
https://webbrowsertools.com/webgl-fingerprint. This website is still able to detect wheather we are spoofing WebGL Fingerprint or not so now what is the benefit of using it?
Несовершенно конечно, но это проблема не расширения а некоторых сайтов, которые хотят знать больше о пользователях.
Ломает большинство сайтов где используется WebGL, например на гугл картах, карта просто становится чёрной, при посмотре улиц вокруг непонятные точки с волнами, онлайн браузерные игры вовсе перестают адекватно работать
Does what it claims to in the most convenient way possible. I don't know why would anyone need a whitelist for this addon (seen this as a downside in another review) - it's hard to imagine a situation where a legit website feature would be broken because of what this addon does, this is not an adblocked that removes parts of the page outright. I also don't think it is fair to criticize the addon for spoofing being detectable - it might be technically impossible due to addon api limitations. It would be a nice feature to have, though.
I mostly use this extension in my primary browser, Opera (as Opera is on the Blink engine, which is based on Chromium, it can install Chrome extensions) and boy could it really use some options. I realize I'm posting this as a review for the both Chrome & Opera, but many of the criticisms still apply to both. Firstly, when I went to install this extension in Chrome (to write this review) I got an error that popped up from Google that said "This extension is not trusted by Enhanced Safe Browsing" and gave me a link to learn more which sent me here: https://support.google.com/chrome_webstore/answer/2664769 Second, my god the notifications and sounds. In Chrome I assume you can disable this. In Opera, unfortunately you cannot. So, the constant popups and beeping gets OUTRAGEOUS on some websites I visit. I filed a bug report on this with the author of the plugin but still haven't heard back. Third, this should be optionally combined with the author's other plugins - Canvas Fingerprint Defender, Font Fingerprint Defender, & Audiocontext Fingerprint Defender. The author makes another plugin I use called Privacy Tweaks I use as well, because it has optional geolocation blocking and spits out a random timezone to the websites you're visiting. Besides that, it's a pretty standard ad + tracker blocker. I don't know why he can't make another optional "defender" type plugin that would defend against all that other stuff without separating them. If anyone knows one that blocks all these, please let me know in the comments below. The author has separate extensions for geoblocking and timezone switching, so I don't know why he couldn't combine all these defender plugins into one single extension. Fourth, yes, as many people have mentioned, this - and the other defender plugins need a pause/disable button and a whitelist. That should be standard for any kind of extension of this type. Any kind of privacy extensions that blank block content on all websites is simply not acceptable. Some websites just won't operate if you're blocking this type of content and so a whitelist is MANDATORY! Otherwise you have to go into extensions, disable it, do your surfing, then go back and turn it back on. Finally, sites CAN detect this as a spoofed WebGL value, as opposed to a fake one. When you click on the extension under your extension tabs or the icon you have pinned and choose "What's my fingerprint?" It takes you to this website: https://webbrowsertools.com/webgl-fingerprint/ where the value for "Is browser webgl fingerprint spoofed" reads "true". Ideally, this would read "false" as it would send fake WebGL packet to the server and not come back detecting it as spoofed, making your browser look suspicious in the eyes of some web hosts.
A nice addition to fingerprint defending options. I do, however, have an issue where chrome says "This extension is not trusted by Enhanced Safe Browsing." Hopefully this can be remedied. I haven't looked into whether this extension tries to reduce the issue of randomness becoming too much uniqueness...
excellent work
Does exactly what it should do and claims it does. Tested at https://browserleaks.com/webgl where it defeated both forms of WebGL hashing. I like that this is a one-exploit fix instead of a plugin claiming to spoof all forms of user fingerprinting, since new methods of that come up all the time. It's better to be certain that you have a particular weakness patched up because you have an extension that corresponds to it exactly, than to go without preventing a leak because you assumed it was included in some catchall extension but it wasn't. PS: Anyone who cannot figure out that they can click on the extension's icon and pick "Show|Hide desktop notifications" simply doesn't DESERVE to use this extension. Heh. Really, the developer should just turn this option off by default, since it's obviously the only thing causing unhappy feedback. PPS: Yes, it may trigger some additional two-factor authentication requests from some sites. This is not actually a bad thing. More sites need to be doing more of this, and we just need to get used to it, as we got used to "password123" not being a good password, and even "@3'4e9sef!J29x" not being a good password if used on a bunch of sites. However, spoofing this kind of stuff actually *shouldn't* trigger a 2FA request, much less a refusal to provide services, so if it does, you should complain to the site in question.
It use to work. But now doileak(.com) can detect IP with this app enabled. I have ran this for over a year without issue. So the newest detection software see's through it. Removed from chrome and using other options. Use to work great, just zero updates and zero support.
Won't work. It's trivial for a site to know you're using this plugin. Hence you are fingerprinted. You've merely replaced your WEBGL-fingerprint with a WEBGL-blocker-fingerprint. If the fingerprint spoofing was undetectable, that might work.