Marketwatch.com problems

[Jojo999]

I just looked at the filter subscriptions in use in Lattitude (which I think are the same as in ABP) and I found references to Livefyre and Fyre as follows:

===========================
Found in Lattitude Easylist
@@||livefyre.com^$script,third-party,domain=activistpost.com|addictinginfo.org|alfonzorachel.com|allenbwest.com|allenwestrepublic.com|aplus.com|askmefast.com|bizpacreview.com|boredpanda.com|breathecast.com|bulletsfirst.net|chacha.com|christianpost.com|christiantoday.com|clashdaily.com|classicalite.com|comicallyincorrect.com|comicbookmovie.com|conservativebyte.com|conservativetribune.com|conservativevideos.com|cowboybyte.com|crossmap.com|dailyheadlines.net|dailysurge.com|dccrimestories.com|digitaljournal.com|drhotze.com|eaglerising.com|enstarz.com|explosm.net|flexonline.com|gamezone.com|genfringe.com|girlsjustwannahaveguns.com|hellou.co.uk|heroichollywood.com|hngn.com|infowars.com|instigatornews.com|joeforamerica.com|kdramastars.com|kpopstarz.com|latinopost.com|latinpost.com|libertyunyielding.com|listverse.com|mensfitness.com|minutemennews.com|mobilelikez.com|mstarz.com|muscleandfitness.com|musictimes.com|naturalblaze.com|naturalnews.com|natureworldnews.com|newser.com|oddee.com|okmagazine.com|patriotoutdoornews.com|pitgrit.com|radaronline.com|rantlifestyle.com|realfarmacy.com|redmaryland.com|rightwingnews.com|segmentnext.com|shark-tank.com|spectator.org|starmagazine.com|stevedeace.com|techtimes.com|theblacksphere.net|thechive.com|thefreethoughtproject.com|thegatewaypundit.com|themattwalshblog.com|thepoke.co.uk|traileraddict.com|valuewalk.com|variety.com|vcpost.com|victoriajackson.com|viralnova.com|viralthread.com

||beacon.livefyre.com^
||fyre.co^*/tracking/
||livefyre.com/libs/tracker/
||livefyre.com/tracking/
||livefyre.com^*/tracker.js
||livefyre.com^*/tracking/
@@||fyre.co/*/facebook_share_post.png
==============================

It would seem that I have to remove that "Easylist" or custom edit it everytime it updates? I don't really understand ad blocker syntax.

But seems like a real conflict possibility with NS as to who gets to block what! I would think that relatively few users look at those ad blocker subscription lists, so they could be the source of unresolved many problems.

[barbaz]

NoScript _should_ always run last, but if Adblock Latitude is using nsIContentPolicy to block stuff then the order can be somewhat indeterminate.

Try adding these custom whitelist filters in Adblock Latitude:

Code: Select all

@@||googleadservices.com^$script,domain=marketwatch.com
@@||googletagservices.com^$script,domain=marketwatch.com
@@||contextual.media.net^$script,domain=marketwatch.com

Since you said you run an adblocker, I was making my testing with uBlock Origin enabled in my usual configuration (which is generally REALLY strict). These filters should be better equivalents of what I did in uBlock Origin.

[Jojo999]

I just switched to UO in Pale Moon. Turned off ABP. Still using Easylist. But Livefyre comments are working in MW still and I can post.

Why isn't the Easylist filter contents related to Livefyre causing problems??? This is why I am mixed up with what is going on.

I need to leave for a few hours so will look at anything you post later.

Thanks!

[barbaz]

Probably because EasyList isn't actually blocking Livefyre. None of the filters you posted would have that effect: filter starting with @@ is a whitelist, and the others look targeted to blocking just tracking done by Livefyre. Also, in the uBlock Origin setup I have (which includes all EasyList's blocking rules & most of their whitelist rules), neither Livefyre nor contextual.media.net are explicitly whitelisted.

Not sure what else to say here other than double-checking in Adblock Latitude, both subscriptions (especially the URLs) and custom filters, in case it might have added something or redirected a subscription?

And, you're welcome.


EDIT
just realized I explained something quite poorly, should clarify. Sorry about the confusion.
uBlock Origin uses a different method of blocking from ABP, and that method of blocking necessarily runs *after* NoScript's script-blocking. I think NoScript tries to have its nsIContentPolicy run last out of all nsIContentPolicy's, but my own experience is that order of nsIContentPolicy it's somewhat indeterminate.
Also I'm not sure uBlock Origin blocks websockets or not (ws: & wss: URLs), but I know ABP can (and so probably can Latitude).. and I think I saw something about a ws: URL in the Browser Console (Ctrl-Shift-J) when I was investigating that marketwatch link. Maybe relevant, maybe not - I don't know.