eurogamer.net

[Zhangsun321]

http://www.eurogamer.net/
just started anti ad block last night
chrome violent monkey ublock origin

[uBlock-user]

a.noAccess("stop");

or

eurogamer.net##script:inject(abort-on-property-read.js, stop)

[uBlock-user]

same as #85

[Zhangsun321]

ok now.. i remember doing comicbook.com manually...
so i would put..
||eurogamer.net^$inline-script
||$third-party,domain=eurogamer.net
into my ublock whitelist...
yep.. seems to work as a temp fix.
till jspenguin does the update..

[uBlock-user]

so i would put..
||eurogamer.net^$inline-script

Using that filter might kill other website functionality, so it's advisable to only use it as a weapon of last resort.

[Zhangsun321]

well your fix... where do i put that into my ublock? or do i add it somewhere to my violent monkey?
im still learning... :)

[uBlock-user]

Just wait for @jspenguin2017 to patch it in the Script or the List. We already have the solution.

[Zhangsun321]

ok thank you two very much

[jspenguin2017]

Thanks, I'll patch this.

[jspenguin2017]

Looks like it is "pinging" p.d.nn0e.com, which is currently not blocked with the standard configuration, but I'll roll out the patch anyway, since that domain looks pretty sketchy.

[uBlock-user]

Just add - ||p.d.*.com/v$third-party,script that will take care of any such new domains being added.

[jspenguin2017]

@uBlock-user Yea... we probably should do this...

[jspenguin2017]

@uBlock-user Are you sure /v is needed?

This does not need to be blocked?

[jspenguin2017]

What?

The domain is pointing to Google...

[jspenguin2017]

OK, looks like Google is behind this. It has a valid HTTPS certificate and the domain is pointing to Google's IP.

[uBlock-user]

Yes, all these domains are owned by Google for whatever purposes.

Secondly, the filter I posted is from uBlock Filters+ repo. I already have that so I suggested, you can remove /v or don't add at all and just add the domain, it will still do the job.

[jspenguin2017]

I'm testing ||p.d.*.com^$third-party,script, I'm feel it is a bit too aggressive... And what is telling us that Google won't change d to c or something...

[jspenguin2017]

The certificate matches these domains:

DNS Name=*.d.0emm.com
DNS Name=*.d.0emn.com
DNS Name=*.d.0enm.com
DNS Name=*.d.0fmm.com
DNS Name=*.d.0mme.com
DNS Name=*.d.1emn.com
DNS Name=*.d.1enm.com
DNS Name=*.d.2enm.com
DNS Name=*.d.3enm.com
DNS Name=*.d.4666.ch
DNS Name=*.d.8d1f.com
DNS Name=*.d.9emn.com
DNS Name=*.d.e0mn.com
DNS Name=*.d.em0n.com
DNS Name=*.d.emn0.com
DNS Name=*.d.m80fg.com
DNS Name=*.d.mdf91.com
DNS Name=*.d.mn0e.com
DNS Name=*.d.mpk01.com
DNS Name=*.d.ndf81.com
DNS Name=*.d.nfd81.com
DNS Name=*.d.nn0e.com
DNS Name=*.d.rpts.org
DNS Name=*.w.0emm.com
DNS Name=*.w.0emn.com
DNS Name=*.w.0enm.com
DNS Name=*.w.0fmm.com
DNS Name=*.w.0mme.com
DNS Name=*.w.1emn.com
DNS Name=*.w.1enm.com
DNS Name=*.w.2enm.com
DNS Name=*.w.3enm.com
DNS Name=*.w.4666.ch
DNS Name=*.w.8d1f.com
DNS Name=*.w.9emn.com
DNS Name=*.w.e0mn.com
DNS Name=*.w.em0n.com
DNS Name=*.w.emn0.com
DNS Name=*.w.m80fg.com
DNS Name=*.w.mdf91.com
DNS Name=*.w.mn0e.com
DNS Name=*.w.mpk01.com
DNS Name=*.w.ndf81.com
DNS Name=*.w.nfd81.com
DNS Name=*.w.nn0e.com
DNS Name=*.w.rpts.org

I guess that rule isn't good... Maybe we just go grab the certificate from time to time and just list the domains as black list?

[jspenguin2017]

I think this is better, less aggressive and match those starting with w.

||d.0emm.com^$third-party,script
||d.0emn.com^$third-party,script
||d.0enm.com^$third-party,script
||d.0fmm.com^$third-party,script
||d.0mme.com^$third-party,script
||d.1emn.com^$third-party,script
||d.1enm.com^$third-party,script
||d.2enm.com^$third-party,script
||d.3enm.com^$third-party,script
||d.4666.ch^$third-party,script
||d.8d1f.com^$third-party,script
||d.9emn.com^$third-party,script
||d.e0mn.com^$third-party,script
||d.em0n.com^$third-party,script
||d.emn0.com^$third-party,script
||d.m80fg.com^$third-party,script
||d.mdf91.com^$third-party,script
||d.mn0e.com^$third-party,script
||d.mpk01.com^$third-party,script
||d.ndf81.com^$third-party,script
||d.nfd81.com^$third-party,script
||d.nn0e.com^$third-party,script
||d.rpts.org^$third-party,script
||w.0emm.com^$third-party,script
||w.0emn.com^$third-party,script
||w.0enm.com^$third-party,script
||w.0fmm.com^$third-party,script
||w.0mme.com^$third-party,script
||w.1emn.com^$third-party,script
||w.1enm.com^$third-party,script
||w.2enm.com^$third-party,script
||w.3enm.com^$third-party,script
||w.4666.ch^$third-party,script
||w.8d1f.com^$third-party,script
||w.9emn.com^$third-party,script
||w.e0mn.com^$third-party,script
||w.em0n.com^$third-party,script
||w.emn0.com^$third-party,script
||w.m80fg.com^$third-party,script
||w.mdf91.com^$third-party,script
||w.mn0e.com^$third-party,script
||w.mpk01.com^$third-party,script
||w.ndf81.com^$third-party,script
||w.nfd81.com^$third-party,script
||w.nn0e.com^$third-party,script
||w.rpts.org^$third-party,script

[uBlock-user]

Or we could just let Easylist and Fanboy add them as they come across and allocate one less responsibility on our shoulders as newer domains will be added by Google and there's no end to that.

[jspenguin2017]

Hum, EasyList does have a few of them in there... But I don't think they will block all of them since it does break some sites, and there is no easy way for AdBlock / ABP to fix that.

[ryanbr]

We blocked them initially, then it caused a few issues with page rendering.

[uBlock-user]

I have them blocked always, I don't see any issue with page rendering on any domains I visit. Also these domains are used for serving Anti Adblock notices fyi

[jspenguin2017]

@ryanbr It cause problem with page rendering because there is a script that ping those domains and destroy the page if the ping fails, but with uBlock Origin, we can crash the detection script. I think it is appropriate for EasyList to not block them, because it is aimed at Adblock Plus. But we will block them.

[jspenguin2017]

Closing as it still works.

[jspenguin2017]

@spodermenpls The problem with immobilienscout24.de should be fixed in the latest release, if you have found any other sites using this Funding Choice or whatever, just let me know, it's a trivial fix but I can't apply it to all websites.

[spodermenpls]

@jspenguin2017 I deleted my original comment, because the problem is most likely caused by AAK-Cont, not uBProtector. He/they copied your rules for emn0.com into their .txt-list, but not in the userscript (which I analyzed only after commenting here). By adding the rules to the userscript, the emn0.com-scripts should be effectively disabled, otherwise I will let you know (being the source for those rules).

[jspenguin2017]

I am aware that AAK-Cont is out of sync by quite a bit, but I don't have time to update it right now, and other maintainers are super busy too. I might exclude those rules from AAK-Cont. Thanks for bringing this up.