washingtonpost.com

Post by **postgraphics** » Tue Mar 12, 2019 7:27 pm

Hello.

I'm here to representing The Washington Post's Graphics team.

Would it be possible to whitelist this domain on the EasyPrivacyList?

Code: Select all

wp-stat.s3.amazonaws.com

Many of our static files -- mostly images, as far as we know -- are hosted on this domain, and the blocking makes our graphics unreadable.
Here is a page

Code: Select all

https://www.washingtonpost.com/transportation/2019/03/12/where-plane-model-that-crashed-ethiopia-flies

we recently published that shows our graphics without images, resulting in the domain being blocked.

Post by **intense** » Tue Mar 12, 2019 7:56 pm

waiting for easyprivacy authors, I fixed the issue in unbreak list for uBo (ublock origin)
https://github.com/uBlockOrigin/uAssets ... 617bdef78c

Post by **postgraphics** » Tue Mar 12, 2019 8:22 pm

Thanks, intense. Much appreciated.

Post by **smed79** » Wed Mar 13, 2019 2:40 am

PR https://github.com/easylist/easylist/pull/3037

Post by **intense** » Wed Mar 13, 2019 7:27 am

fixed (removed) for all adblockers
https://github.com/easylist/easylist/co ... bc7a843c91

Post by **Khrin** » Wed Mar 13, 2019 7:33 am

intense wrote: ↑Wed Mar 13, 2019 7:27 am fixed (removed) for all adblockers
https://github.com/easylist/easylist/co ... bc7a843c91

yeah, and im still not sure of why

good job indeed postgraphics or whoever is behind the account

Post by **postgraphics** » Wed Mar 13, 2019 3:43 pm

Thank you, all. I can confirm the page is now working with the whitelist.

Post by **cantare** » Sat Aug 17, 2019 1:33 am

On Chrome (76.0.3809.100 (Official Build) (64-bit)) & Windows 7 Ult SP1 x64, the EasyPrivacy list under AdBlock Plus 3.6.2 blocks the display of comments, but only when logged in as a subscriber You can click the display comments button but nothing happens until you disable that particular list (the other default ABP lists are fine)

Code: Select all

https://beta.washingtonpost.com/opinions/2019/08/16/mcconnell-realizes-with-horror-that-beto-is-right-senate-is-not-enough/#comments-wrapper

Non-subscription trial access (tested in in incognito mode) does not appear to trigger the problem.

ABP issue report dump follows:

https://pastebin.com/raw/FJT6r8g0

Post by **cantare** » Sat Aug 17, 2019 7:38 am

I found the offending item in EasyPrivacy that's blocking the subscriber comments. It's

||nile.works^$third-party

Post by **fanboy** » Sat Aug 17, 2019 9:01 am

I couldn't reproduce this, I created an account. Viewed in a private windows, was able to view comments. Works for me.

Post by **cantare** » Sat Aug 17, 2019 6:27 pm

Did some more digging. I thought incognito vs regular mode might be the key. I had originally used incognito so I could directly compare logged-in vs anonymous access in the same browser instance.

But then I tried logging in via incognito, after making sure I had the same set of extensions enabled for incognito mode--and there's no problem with the offending filter or the full EP list.

However, I notice something else. My non-private logged-in session (where I'm experiencing the issue) always sends me to article URLs with the beta.washingtonpost.com domain. And there is that little tab overlay at lower left with 4 buttons, including one for comments, which is a new addition to their system (visible in my screenshot). I'm guessing you don't see that. So I believe they are beta-testing a new comment interface--on what basis, I'm unclear.

It's not on a userID basis, because I now have 2 Chrome sessions logged in as the same subscriber, and one is using the beta and the other (incognito) is plain washingtonpost.com. Manually pasting a non-beta washingtonpost.com link into the existing "beta" session always redirects to the beta URLs which have the button overlay and the filter problem. Repeatedly logging out and back into my incognito session with the same ID never triggers the beta mode.

Anyway, it's clear this filter conflict only affects those who are being subjected to the beta comment engine. That may of course become the site-wide default at any time, and pose an issue for all WaPo users who run ABP and the Privacy list. I just don't know how you can test it yourself unless you can experience the beta site.

Post by **MaxH42** » Thu Aug 22, 2019 7:18 pm

This appears to be due to EasyList Privacy blocking a script from nile.works. When I turn off EasyList, the comments load.

The only difference in the browser console when reloading an affected page is this line (appears when comments are broken, is missing when they work):

Loading failed for the <script> with source

Code: Select all

https://coral-talk.ext.nile.works/talk/static/embed.js

Confirmed by adding

Code: Select all

@@||coral-talk.ext.nile.works/talk/static/embed.js

to my custom list and re-enabling EasyList Privacy.

EasyList Forum