3 ms·
Yeah, it's theoretically impossible to stop a determined extension-writer from perfectly blocking ads in a way that leaks no information. But current implementa
by derefr 11y ago
Yeah, it's theoretically impossible to stop a determined extension-writer from perfectly blocking ads in a way that leaks no information. But current implementations are sloppy and leak all sorts of information. Usually you can just run some (inline!) Javascript to inspect the DOM and then do something.
Or, if the client won't run Javascript at all (and you might consider making your site require Javascript to render anything, just to stymie these users, if you're on this path already), you can still set a background-image property as a "default" for a banner div, in a way that it will never get requested if the ad does get rendered, but will get requested if it doesn't. (OKCupid uses this approach, if I recall.) You can then use that information just for analytics, or you can go further and change what the server serves that client from then on (i.e. make all further pages for that session return an error.)