Alignment fail
-
Proxomitron
TIL. Wikipedia suggests that people are still maintaining filters, and there is a support group on Yahoo!. I didn't bother going to any of the linked sites to see how recently or actively they are being maintained.
-
Proxo was awesome, because, since it wasn't part of the browser, it filtered out ads before you ever
sawdownloaded 'em.
-
I once thought about setting up something like that. If I had known Proxomitron existed, I probably would have. These days, I'm mostly satisfied with ABP and Ghostery.
-
I just hosthole particularly annoying ad servers in my hosts file.
-
Firefox, whose plugin API exposes the ability to veto loading something. Unlike Chrome, where AdBlock Plus can only hide things using CSS rules, in Firefox ABP can prevent ads from being loaded at all. Wladimir Palant has a whole rant somewhere...
-
I just hosthole particularly annoying ad servers in my hosts file.
That seems like work.
If I were gonna do that I'd have to redirect them to a web server that serves up 1x1-pixel gifs and empty files so I don't see errors on my pages, and that seems like even more work.
-
Firefox, whose plugin API exposes the ability to veto loading something.
That sound really cool, but I can't bear to use FF.
-
How does Chrome with Adblock Plus trigger the silly "We know you're blocking our ads" messages on some sites then?
-
I can think of one obvious way right off the top of my head.
-
I did some checking and failed to update my post. It looks like Chrome added an actual proper API for that in 2013, causing a major update that brought ABP Chrome up to par with ABP Firefox and much rejoicing.
But theoretically they could detect it by elements that should exist in the DOM poofing out of existence or suddenly taking up no space, instead of catching the "a plugin vetoed loading this content" JSError. Or not even try to catch it and just have whiny messages beneath where the ads go.
-
Or not even try to catch it and just have whiny messages beneath where the ads go.
I'd thought of that - but was thinking of where the ad and the message aren't in the same place.
But theoretically they could detect it by elements that should exist in the DOM poofing out of existence or suddenly taking up no space,
That sounds like it'd make sense. Web isn't my thing so didn't know such things were possible.
-
It could check for a certain JS object to exist or a certain cookie to have been set.
It can load the ad into the container of the whiny message, replacing it only when successfully loaded.
Or maybe the whiny messages are set by a CSS rule triggered by an empty container.
-
It can load the ad into the container of the whiny message, replacing it only when successfully loaded.
That's what it does -- I've seen those messages when ads simply failed to load (Flash ad on a Flash-less box, for instance).