-
Notifications
You must be signed in to change notification settings - Fork 738
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
[Anti-adblock] washingtonpost.com #5070
Comments
Have you tried with an up to date |
Hi. I updated the filter and confirmed that your revision is present. The site still serves its anti-adblock response to me. I checked on a second computer that runs old Windows (XP, crazy), FF, & uBO. The anti-adblock overlay began the same day on that pc too. Updating filters didn't help there either. |
Updated filters and like @Woofy-Wolf I still see the blocker. My observations: Can disable the anti-adblock by blocking first-party scripts, in which case the page loads but many images are masked. Have not been able to fix by trying to whitelist specific parts of the first party script. Another workaround is immediately stopping the page load after reload, which must stop the page load before the problem script runs. A previously suggested filter of |
Updated my filters and went through a few links on the site and waited no anti-adblock here. Using Chrome v72 latest ublock. |
I can reproduce, if I use a VPN from USA, but I can't reproduce if I use my real IP. |
Can you test the following filter and confirm if it works?
|
Does not work for me; thank you though. |
Did you test with my edit to include |
Thanks; It removes the blue bar at left. The article is still truncated, and there is a gray mask over it. Using @Woofy-Wolf 's original URL screenshot: |
I think it is a cookie set by the site triggering the limit, not sure if it is appropriate to fix in uAssets Possible other things you can try on your end:
|
Thanks. Any idea what cookie? I can perhaps whitelist. Third-party tracking cookies are blocked by FF's strict setting. I disabled/changed that to standard but same result. I also have a cookie destruction plug-in, but that only triggers upon leaving the site and I can whitelist there too. |
You could try blocking all cookies from |
Tried switching FF to block all cookies, cleared cookies, and reloaded... No change. |
Weird, I can't reproduce no matter what IP I use. |
Looks like that fixed it @okiehsch. Many thanks! |
You nailed it, @okiehsch . Thank you! |
I added |
It works on my end with an up to date |
Google Chrome 74.0.3729.169 on macOS 10.14.5 (18F132). Checking uBlock-filters ("16,588 out of 16,605") I see WaPo in the following chunk
So it is in there... |
This is probably a macOS issue, see #2317 (comment). An alternative filter fixing the issue on my end is |
If that
they should work with macOS. |
Hey this is a problem again, you should reopen it. I started getting this problem today, August 2nd 2019 after previously not having it, seems washingtonpost.com updated their code. I have isolated the problem to this uBlock filter in the filter list "uBlock filters": washingtonpost.com##+js(abort-current-inline-script, Promise.all, adblocked) If I disable the uBlock filters filter list I don't get the anti-adblock message but if I do have uBlock filters on, washingtonpost.com story pages (not the front page) all come up with an anti-adblock message as described earlier, and this is something new as of August 2nd, 2019, this was not happening yesterday on August 1st. I have not found a workaround other than disabling that filter. I would also mention this issue likewise happens with the "EasyList" filter list too now with this change washingtonpost.com did, which blocks several different things, so it also has to be disabled too to get rid of this anti-adblock message. But that is a separate issue for EasyList to deal with. Anyway if both uBlock filters and EasyList are turned off I can have all my other filter lists turned on and washingtonpost.com works fine. |
I can reproduce in Chrome. Bait: |
This filter |
|
They won't |
URL(s) where the issue occurs
https://www.washingtonpost.com/technology/2019/03/06/facebooks-mark-zuckerberg-says-hell-reorient-company-towards-encryption-privacy
most washingtonpost.com urls other than the front page
Describe the issue
An anti-adblock notice and overlay appear with a request to unblock ads.
Screenshot(s)
Versions
Settings
All official/included lists except mobile ads filter, plus nano defender & its lists
Notes
washingtonpost.com permits non-subscribers to view x articles for free, IIRC, in which case this issue is not about a paywall. It's about anti-adblocker behavior when the site detects a blocker.
The text was updated successfully, but these errors were encountered: