Reviews & Comments of Font Fingerprint Defender chrome extension

From March 31st, 2021 to November 5th, 2022, 50% user give 5-star rating, 25% user give 4-star rating, 13% user give 3-star rating, 13% user give 1-star rating. for Font Fingerprint Defender chrome extension.

Reviews of font fingerprint defender:


Dan Uber November 5th, 2022
Dan Uber

This is another useless extension. doesnt not hide anything. Does not provide anything. is inocuous. Others comments shall be troll accounts


Combax Techx July 13th, 2022
Combax Techx

This is awesome for privacy and doesn't let businesses track you based on the fonts you have installed.


Kutiz June 4th, 2022
Kutiz

I don't know if it's by design but it broke Discord scrolling so bad.


michael schumacher December 5th, 2021
michael schumacher

Works, but breaks css on some websites (for example gazeta.ru). Would be nice to have an option to whitelist particular sites.


MadCake October 17th, 2021
MadCake

Does what it claims to in the most convenient way possible.


Julian Ott October 4th, 2021
Julian Ott

works fine


Michael james TOMLINSON August 11th, 2021
Michael james TOMLINSON

This extension works really well and it's easy to use. Thanks to the developer!


Stanton McCandlish March 31st, 2021
Stanton McCandlish

Does exactly what it should do and claims it does. Tested at https://browserleaks.com/fonts and it spoofed both forms of font fingerprinting. I like that this is a one-exploit fix [well, TECHNICALLY it's two in this case] 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 in this entire series of fingerprint defender extensions, since it's obviously the only thing causing unhappy feedback about any of them.