Our great sponsors
-
user.js
Firefox privacy, security and anti-tracking: a comprehensive user.js template for configuration and hardening
-
evercookie
Produces persistent, respawning "super" cookies in a browser, abusing over a dozen techniques. Its goal is to identify users after they've removed standard cookies and other privacy data such as Flash cookies (LSOs), HTML5 storage, SilverLight storage, and others.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
hosts
🔒 Consolidating and extending hosts files from several well-curated sources. Optionally pick extensions for porn, social media, and other categories.
-
-
-
hosts-blocklists
Discontinued Automatically updated, moderated and optimized lists for blocking ads, trackers, malware and other garbage
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Firefox’s default anti-fingerprinting is just a blacklist of common fingerprinting scripts.
It is incredibly difficult to make a browser fingerprint non-unique. Only the Tor browser has strict enough settings with a large enough user base to overcome fingerprinting.
If you don’t want to use Tor, try these:
- uBlock Origin (which has a larger blacklist of fingerprinting scripts)
- Enable the privacy.resistFingerprinting setting in about:config to make your browser more similar to other users with that setting enabled (but not entirely non-unique)
- The nuclear option: arkenfox user.js [1]. It’s github repo also contains a lot of further information about fingerprinting.
[1] https://github.com/arkenfox/user.js
Evercookie is a Javascript project that produces respawning super cookies:
https://github.com/samyk/evercookie
I added this to my /etc/hosts
https://github.com/StevenBlack/hosts
What is the advantage of having DNS on a separate device other than that it provides ad blocking for multiple devices?
> allowlist/denylist
As of now, it is called whitelist/blacklist in PiHole [0]. Maybe it will change, maybe it will not, but there is already a place to fight that battle [1] and it is not HN.
[0] https://docs.pi-hole.net/guides/misc/whitelist-blacklist/
[1] https://github.com/pi-hole/AdminLTE/issues/1448
Yea, we are planning to do a blog post on it, but the total overhead is in the 10's of KB. Just a single JS file, and an image. All open source: https://github.com/readthedocs/ethical-ad-client
I think that they put the user information in the image using something like this[1].
[1]. https://github.com/subc/steganography
You can get even better coverage with the NoTracking lists (dnsmasq/unbound or dnscrypt-proxy) https://github.com/notracking/hosts-blocklists
They focus not only on tracking but also malware prevention, where possible via dns filtering.
Pi-Hole still does not properly support wildcard filtering, only via regex but that is not really efficient (requires tons of resources).
[i] Target: https://gitlab.com/quidsup/notrack-blocklists/raw/master/notrack-blocklist.txt
https://github.com/WICG/ua-client-hints
In case you are not aware, uBO also allows to wholly disable/enable JS on a per-site basis.[1]
---
[1] https://github.com/gorhill/uBlock/wiki/Per-site-switches#no-...