2 ms·
Then ads should be bucketed as such... Ads that are a link, and an image can be automated, or changed via the end user without intervention. Ads with JS, requi
by tracker1 11y ago
Then ads should be bucketed as such... Ads that are a link, and an image can be automated, or changed via the end user without intervention.
Ads with JS, require going through automated testing (certain things like new Function, and eval are not allowed, along with `window[`, as well as creating a script tag, XHR, and some other bits... No remote content loading, beyond images, period... all content for an ad must be in a self-contained file, and can only exit via a window.goto that the ad-network injects for the purpose... A whitelisted subset of DOM interaction is all that is allowed, and the total payload of an advert must be under ???kb, something reasonable.
Flash ads requiring a source inspection...
All ads served from the network directly, not loading js/html/css or anything outside their network...
It's easy enough to do this, and pass the cost of inspecting JS and Flash ads onto the customers... they can decide if they really need it. It becomes part of the cost of doing business... Banning interstitial ads, and those that take up more than half the screen.