Closed jspenguin2017 closed 6 years ago
Eh... Are you sure that's going to last? But alright, let's call it fixed for now...
I am open for long lasting suggestions.
Do you have good toolkits to deobfuscate it? Mine is falling short these days.
No, which is why I added that fix 😉 .
What is your main "objection" LaodIrmb
or entMNbx
or both?
My toolkit can only get this far...
Seems that navigator
and _0x
are good candidates.
The code feels like https://github.com/javascript-obfuscator/javascript-obfuscator , I'm making a deobfuscator specifically targeted at it, but so far no luck, it's pretty difficult to fingerprint their template functions.
How about
washingtonpost.com##script:inject(abort-current-inline-script.js, InstallTrigger, _0x)
?
Yea, that looks better.
I agree :).
Doesn't quite work anymore, new rule: ||washingtonpost.com/wp-stat/pwapi/prod/*
@jspenguin2017 that is no anti-adblock message, it is their "paywall", I get it every few articles even if I disable uBlock.
@okiehsch I get exactly the first anti adb message in this thread
I do not get that message, I tried with Chrome and Firefox, the only way to reproduce is to disable the filter washingtonpost.com##script:inject(abort-current-inline-script.js, InstallTrigger, _0x)
The filter jspenguin proposed disables the "paywall" part, so I guess that is what he meant when he said "Doesn't quite work anymore".
@mapx- washingtonpost.com##.adblocker-root
fixes the adb-message on your end, do you get the "paywall" message of my screenshot if you click a number of different articles?
Best solution: Just ignore washingtonpost.com completely, nothing of value is lost.
Sorry, I could not resist, please don't hate me.
After few articles I get an overlay instead, if I hide it I see "subscribe to read the full article"
The question is ..should we block the paywall ?
Really? When I tested it, the "paywall" goes away if I disable my adblocker -- so it is not a paywall.
It always goes away, even if you do not disable your adblocker, for a few articles then it comes back. You can see in my screenshot that uBO is disabled.
Is there a point to even ponder whether we should remove that overlay? On my side when I remove it I am left with a not very useful page: article is truncated and there is a "Subscribe to read the full article".
If I add
washingtonpost.com##script:inject(abort-on-property-read.js, WpPwapi1)
I never get that overlay and can read every article without any "Subscribe to read the full article" message.
Well, either remove the "paywall" entirely or unbreak it entirely, removing just half of it is confusing.
We are not removing half of it, it is broken because of EasyPrivacy
, so adding
@@||washingtonpost.com/wp-stat/analytics/*.js$script,domain=subscribe.washingtonpost.com
to uBO-unbreak
and
washingtonpost.com##script:inject(abort-on-property-read.js, WpPwapi1)
to uBO-annoyances
if we decide to circumvent it.
In my opinion it is a badly implemented "quasi" paywall, there is no difference if you use an adblocker or not on my end, so it should not be fixed in a default list, if at all.
It's your call, I'm OK with either way, just make sure it's not confusing.
either remove the "paywall" entirely or unbreak it entirely, removing just half of it is confusing.
has been fixed with https://github.com/uBlockOrigin/uAssets/commit/7ff90332738717c3bd816fa8f9c6479a2681b6bb and for the rest, that's gorhills decision.
A paywall-circumvention list is not part of uBO's stock lists, that would be the only place to put a filter which primary purpose is to cirumvent a paywall. Also, I think it's best to not have such list in uBO's stock lists.
Reportedly there is an issue with washingtonpost.com
:
https://bugzilla.mozilla.org/show_bug.cgi?id=1466730
I can't reproduce on my side (using a US VPN), using default lists.
The issue https://bugzilla.mozilla.org/show_bug.cgi?id=1466730 is OS related.
Some script:inject
filters do not work with MacOS, see https://github.com/uBlockOrigin/uAssets/issues/682 and https://github.com/NanoAdblocker/NanoFilters/issues/45#issuecomment-391129192 for example.
I can reproduce the bugzilla issue, if I add
washingtonpost.com#@#script:inject(abort-current-inline-script.js, InstallTrigger, _0x)
To get the antiadblock message I also have to add
washingtonpost.com#@#.adblocker-root
Example link:
https://www.washingtonpost.com/news/worldviews/wp/2018/06/03/the-united-nations-says-trump-is-making-life-harder-for-the-poor/
Whats the latest filter to circumvent paywall(to be used as custom filter ) ? like this
low-tech solution, clear cookies or stop the page from loading as soon as you click on the link. That's what I do on my phone often.
clear cookies or stop the page from loading as soon as you click on the link.
Technically, you will have to do that after browsing every 3-4 links and that will turn into quite an annoyance if you're an active reader, that's why I didn't suggest that before.
You can also block cookies but that will break videos and I'm sure it will break other stuff.
There's an addon for this called "Bypass Paywalls Clean" Might be worth checking out, since it seems unlikely for uBlock to add this.
For this case, ||washingtonpost.com/*/pwapi-proxy.min.js$script,1p
still works. but won't be added to built-in lists as we don't fix paywalls.
URL(s) where the issue occurs
https://www.washingtonpost.com/world/europe/eu-takes-6-member-states-to-court-over-air-quality/2018/05/17/8582aea4-59f2-11e8-9889-07bcc1327f4b_story.html?noredirect=on&utm_term=.af82a1f5e561
Describe the issue
Anti-adblock
Screenshot(s)
Versions
Settings
All default