-
Post #SRCCON I've been thinking more and more about how publishers could secure the advertising experience...Permalink On twitter.com
♻️ 2 Retweets
❤️ 6 Favorites
Mood +2 🙂
-
Chronotope and I'm thinking that overwriting default Javascript functions may be the way to go.Permalink On twitter.com
♻️ 1 Retweets
❤️ 1 Favorite
Mood 0
-
Alert and document.write could be overwritten to require an authentication key. Document.cookie and window.location could use whitelisting.Permalink On twitter.com
♻️ 1 Retweets
Mood -1 🙁
-
This would work right? What do people think? Am I crazy or could 20-100 lines of JS stop browser hijacking?Permalink On twitter.com
♻️ 1 Retweets
❤️ 1 Favorite
Mood -3 🙁
-
Publishers can't fix the complete lack of oversight within ad networks, but if ads abuse Javascript, could we just take it away from them?Permalink On twitter.com
♻️ 1 Retweets
❤️ 1 Favorite
Mood -6 🙁
-
Basically instead of paywalling users, could we wall off abusive ads?Permalink On twitter.com
♻️ 1 Retweets
Mood -3 🙁
-
Impressions still happen, ads can still be clicked on, but if those ads abuse the privilege of being on our sites, can we stop that abuse?On twitter.com
♻️ 1 Retweets
Mood -7 🙁