Our great sponsors
-
-
little-rat
🐀 Small chrome extension to monitor (and optionally block) other extensions' network calls
-
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.
-
-
uBlock-Safari
uBlock Origin - An efficient blocker for Chromium, Firefox, and Safari. Fast and lean.
-
> The author's description even seems to praise Manifest v3 in the same way Google PR did.
No, it simply declares the goal of that add-on: to fully comply with declarative ways of MV3 and its limitations, and no uBO extended features that need workarounds to be implemented.
He's more strict to Lite than full version:
- https://github.com/uBlockOrigin/uBOL-home/issues/17
2: https://github.com/dnakov/little-rat
While I was trying to find out what Firefox's limits are I came across this interesting issue on the W3C's webextensions repo: https://github.com/w3c/webextensions/issues/319
4 days ago the Chromium developers proposed upping the limit for certain types of declarativeNetRequest rules based on data AdGuard provided on real world rule lists.
You are mistaken. Safari removed the APIs necessary for an uBlock port (there used to be one), see https://github.com/el1t/uBlock-Safari/issues/158.
Injecting code via Web Extensions is too late for reliable blocking - by then, either the malicious JS you are trying to defuse has already ran (if it wasn't blocked declaratively), or if it hasn't, then the rest of the page's JS depending on it has already exploded and "fixing" it after the fact (by substituting a neutered shim via Web Extensions) doesn't fix the rest of the page.
Note that CNAMEs is literally caused by GDPR, and the pathway every single ad or tracking company seems to go sooner or later.
For people not understanding how it works: you can set a CNAME entry on your tracker.domain.tld to bypass all Browser's third-party tracking preventions, and make it look like it's a normal subdomain of your website.
You need to make a CNAME tracker database manually by resolving the reverse entries for known IPs. Usually there is hundreds or thousands of CNAME entries pointing to the same IP address.
The AdGuard team also made a database for this, in case anyone needs it for UBOL [1]
[1] https://github.com/AdguardTeam/cname-trackers
Safari users keep repeating this, but it's simply not true: go open http://twitter.com and see for yourself.