Reviews for CanvasBlocker
CanvasBlocker by kkapsner
445 reviews
- Rated 5 out of 5by pixel8ed, 2 years ago
- Rated 4 out of 5by theoneand33, 2 years ago
- Rated 5 out of 5by CharlesSr, 2 years ago
- Rated 5 out of 5by Firefox user 17789833, 2 years agofor an average user like me it needs approximately an hour to understand the different settings and its reactions. however after i tested everything with https://amiunique.org/fp i'm pretty happy with the results.
- Rated 1 out of 5by macum, 2 years ago
- Rated 4 out of 5by Firefox user 13916787, 2 years ago
- Rated 5 out of 5by K8, 2 years ago
- Rated 5 out of 5by Mistermind, 2 years ago
- Rated 5 out of 5by Torcerdra, 2 years ago
- Rated 5 out of 5by block_overdose, 2 years ago
- Rated 5 out of 5by Ads Reklam Hizmetleri, 2 years ago
- Rated 3 out of 5by Mike S., 2 years agoWorks, but slows some sites to a crawl (i.e., eBay). Settings are hard to understand. Unclear how to whitelist a site.
Developer response
posted 2 years agoFor eBay you can check the discussion on https://github.com/kkapsner/CanvasBlocker/issues/555 and https://github.com/kkapsner/CanvasBlocker/issues/563
The best way to whitelist a site is over the little fingerprint icon in the URL bar.
Optimizing the settings is on my todo but it's hard as I'm not a UX/UI person... - Rated 4 out of 5by Seishirou, 3 years ago
- Rated 5 out of 5by Beatrix, 3 years ago
- Rated 5 out of 5by opexxx, 3 years ago
- Rated 5 out of 5by Claudiu, 3 years ago
- Rated 5 out of 5by Dmitry Valter, 3 years ago
- Rated 5 out of 5by Alexandre, 3 years ago
- Rated 5 out of 5by VerifiedStaff, 3 years ago
- Rated 5 out of 5by Bryan Hoang, 3 years ago
- Rated 4 out of 5by drifty, 3 years ago
- Rated 4 out of 5by lilith, 3 years ago
- Rated 5 out of 5by Max, 3 years ago
- Rated 3 out of 5by ko to, 3 years agoНа насыщенных страницах типа youtube, google docs вызывает перманентное повышенное потребление процессора
Developer response
posted 3 years agoI assume you meant CanvasBlocker with "google docs"...
You should check which API protection is causing the CPU usage and consider allowing this API on these sites. Also ignoring the DOMRect API in the notifications (you have to enable the expert mode to be able to do that) can help massively with performance problems.