Closed Esokrates closed 5 years ago
Hum, it's really hard to reproduce. I'll investigate later. Clearing the cookies fixes the issue.
FYI @okiehsch
I don't know what to tell you, I can't reproduce.
I use the site frequently and I never have any issue unless I disable uBO-filters
at which point I get the adblock message within three or four clicks.
@okiehsch Can you try Chromium on Ubuntu?
My standard "private" setup is Linux Manjaro Chrome/Chromium and that does not have any issues.
I can't install Ubuntu right now.
Hum, I can't reproduce it anymore... My only worry is that set-constant
could fail the race.
That's easy to check. @Esokrates does adding
derstandard.at#@#script:inject(set-constant.js, nuggprof, noopFunc)
@@||derstandard.nuggad.net/rc$script,domain=derstandard.at
to your filters fix the issue on your end.
It's working for me with or without the scriptlet.
Hm, if I disable the scriptlet after clicking on a few articles
I don't know what to make of all this, I do know that it does make it nearly impossible to find a reliable fix that works for everybody.
I can reproduce it using the default settings in both uBO and Nano
Same here, fully updated extensions (using 15.0.0.19), cleared cookies. It takes some minutes, but it reliably triggers :-(.
@okiehsch I just tried your scriptlet: does not make a difference, the paywall triggers reliably after a few minutes at the latest.
@jspenguin2017 please reopen
Upgraded to chromium 68.0.3440.75, does not make a difference, I can 100% reproduce, just a matter of time.
@okiehsch Also tried fresh profile with ublock origin + ublock origin extra: same issue.
I don't know what to tell you, I can't reproduce. The only problem I can think of is the race condition in that scriptlet. Which should be fixed now.
Which country are you in? Do your ISP or organization block certain domain? Also I need the dump of the logger output and the DevTools console. I need to see every line, screenshot as many times as it takes.
@jspenguin2017 I am located in Austria. I am not aware of my ISP censoring anything, nor do I have any sort of network filtering activated. What logger output do you need / what do you mean by logger output? Regarding DevTools console output: would a screencast do it? I have the console open and trigger the paywall and you can follow along the output?
I can reproduce it immediately using the following steps:
Go to derstandard.at
Refresh page 4 or 5 times
You are right, I can reproduce if I refresh the homepage page 4 or 5 times. If I refresh any article I can't reproduce. Example:
https://derstandard.at/2000083972831/Vettel-Ich-glaube-nicht-dass-es-ein-grosser-Fehler-war
This is some weird detection mechanism and I can't believe that it is working as intended.
Confirming the observation that refreshing the main page 4 to 5 times triggers the issue.
OK, so the problem is just with the home page.
Well, it is only if you refresh it 4-5 times in a row. If I for example go to the homepage, then click an article, go back to the homepage, click another article etc. I can't reproduce. That's why I never had any issue using the site, as no "normal" user refreshes the homepage 4-5 times just for the fun of it.
True, but if you have no extension enabled, refreshing 4-5 times won't send you to the block page.
@@||adfarm1.adition.com/s$script,domain=derstandard.at
fixes the issue, but I am hesitant to add an exception for such a frankly bizarre case.
I'm not too worried as long as it doesn't let ads through.
The homepage with the exception.
The homepage without the exception
The "Bezahlte Anzeige" is an ad.
Interesting, they didn't come up before.
Should be good now.
The exception is really not a good idea, go to https://derstandard.at/Inland
and wait a little.
The ad is quite obvious on that page ;)
Edit: Your fix was quicker than my post.
Bad News: Using Nano Defender 15.0.0.20 reloading 4 times does still trigger the issue, tested with fresh profile.
tested with fresh profile.
Don't, you need to update filters.
But yea, it somehow still triggers, but it's gone after a few seconds.
Force an update of uBO-filters
and then add
derstandard.at##script:inject(cookie-remover.js, /^MGUID/)
to your filter list.
Does that break login?
I can login, the problem is that I get automatically logged out if I refresh the page.
@okiehsch Adding
derstandard.at##script:inject(cookie-remover.js, /^MGUID/)
fixes the reloading issue yes, but I can still trigger the issue when aggressively clicking through articles randomly for at most 4 minutes, any idea?
@gwarser pointed out that
"Cookie is only removed at the main page, because document.cookie
defaults to current path when path is missing in cookie string, and derstandard.at
sets cookies on /
."
That is probably the reason for your issue clicking through articles, which I still can't reproduce.
@okiehsch Thanks for pointing this out. I just recorded yet again how I am able to reproduce: https://youtu.be/cauubMXgn1s If you want I can also demonstrate this with an ublock setup. I am always successful within a 5 minute timeframe. Tested on two different networks.
The moment you get the anti-adblock message, what does your logger show?
Found the way to trigger it, click exactly as in the screencast (demonstrated that ublock and nano behave exactly the same): https://youtu.be/WAvYM49PBuY https://youtu.be/xGv3KBaBDdY The trick is to use the uppermost navigation bar, which triggers the issue within 4 clicks. Regarding the logger (by which I suppose you mean the console): there are only unrelated vsync errors.
EDIT: BTW, the 5 times reloading triggers the issue again!!
EDIT2: Hum, ok in today's tests I forgot adding derstandard.at##script:inject(cookie-remover.js, /^MGUID/)
, so the deomstrated trigger does not work with that line, so the first EDIT is not true!!
I mean uBlockOrigins logger.
EDIT: BTW, the 5 times reloading triggers the issue again!!
With
derstandard.at##script:inject(cookie-remover.js, /^MGUID/)
added to your filter list?
@okiehsch I've added a second EDIT to my comment. Now I have recorded another screencast with the line added to my filter list, force updated filters and the logger open, please have a look: https://youtu.be/2nb0-B5UvVY
EDIT: Just saw that the screencast is very choppy, I am sorry for that, the screencast software I'm using sucked up the whole cpu ressources so I guess some frames were lost in the process.
Ok, this is the same output that I get if I remove
derstandard.at##script:inject(cookie-remover.js, /^MGUID/)
Now, no need for a screencast, just open your logger and put --
in the "filter log entries" box.
Trigger the anti-adblock message and post a screenshot of the logger after you successfully triggered it.
I only need the last entries, so no need to show all of them.
Because I've already uploaded here another link for a screencast where I triggered: https://youtu.be/z0c_VCGFKLY Here a screenshot of another try as you requested:
Both times WITH
derstandard.at##script:inject(cookie-remover.js, /^MGUID/)
Well, adding
@@||adfarm1.adition.com/s$script,domain=derstandard.at
to your filter list should work.
The message should change to
and then to
@okiehsch Well, when adding that to my filters I can recover from the paywall yes, but the articles break after a few seconds like: I'll do further tests.
Add
derstandard.at##iframe[src="about:blank"]
That works :-). I'll do further testing.
@okiehsch It still triggers but recovers afterwards as you pointed out, but I guess that's the best you can do!?
I can't reproduce, so yes that is the best I can do.
Edit: By the way this
It still triggers but recovers afterwards
clearly shows that something is wrong with the sites anti-adblock script in the first place.
Ok, shall I do something else? Here how it looks after triggering with all the lines you provided:
At this point I have clicked nothing Here I clicked to return to the article:
Really strange that you can't reproduce, did you try really hard for a few minutes?
Sorry, I do not want to fool you guys, but the issue is not solved for real, locking as solved does not make it any better. I do not use any Apple device.
Here is a screencast I just recorded for proof when launching chromium with a fresh profile: https://youtu.be/JR-NgxfAuIc
I am happy to give you any info you need.