Chronotope’s avatarChronotope’s Twitter Archive—№ 66,063

        1. Post #SRCCON I've been thinking more and more about how publishers could secure the advertising experience...
      1. …in reply to @Chronotope
        Chronotope and I'm thinking that overwriting default Javascript functions may be the way to go.
    1. …in reply to @Chronotope
      Alert and document.write could be overwritten to require an authentication key. Document.cookie and window.location could use whitelisting.
  1. …in reply to @Chronotope
    This would work right? What do people think? Am I crazy or could 20-100 lines of JS stop browser hijacking?
    1. …in reply to @Chronotope
      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?
      1. …in reply to @Chronotope
        Basically instead of paywalling users, could we wall off abusive ads?
        1. …in reply to @Chronotope
          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?


Search tweets' text