-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Non-Issue/Info] Adblock Edge to be discontinued, dev directs users to uBlock. #70
Comments
You forgot to add related links. https://bitbucket.org/adstomper/adblockedge/issue/197 |
I was looking at that NoMercy's Guide for uBlock, and for that kind of level of blocking, it would be much simpler to just advise users to turn on "I am an advanced user", then globally block 3rd-party requests (aka default-deny for all 3rd-parties). This would result in an even more merciless configuration, users would be able to un-break through point-and-clicking if they care to un-break, and even when un-breaking, the page would still have to go through static filtering (default filter lists is stricter than ABP + EasyLIst + EasyPrivacy). |
I can't get that guide to load, and it has only been 22 minutes. |
@lewisje |
@lewisje that link only works with Tor. |
I almost forgot, those are the idiots who think any and all whitelists are "unnecessary" instead of being workarounds for false positives (especially in gorhill's case, for false positives in other lists, which he does not directly control); I hold the "NoMercy" forks of EasyList and some other lists in almost as much contempt as the "Adblock Edge" wankers, and I agree that gorhill's solution is better for those who really want to get rid of third-party whitelists and know what they're doing. Now I'm not sure why that site was refusing to send anything to me; surely it can't be because I run a non-exit Tor node, because I would think the operator of a Hidden Service would be friendlier to node operators than that. |
[WIP] Add filter linter
Link to AMO.
Just FYI.
The text was updated successfully, but these errors were encountered: