Chronotope’s avatarChronotope’s Twitter Archive—№ 128,345

        1. …in reply to @robinberjon
          robinberjon clancynewyork steveglista swodinsky anniesullie This is a very common hijack ad I've seen all the time. It is pretty crafty because it all exists in the ad but calls out and rewrites the top frame. The publisher should enact safeframes if this is a common issue.
      1. …in reply to @Chronotope
        robinberjon clancynewyork steveglista swodinsky anniesullie Or they can put all their ads in iframe sandboxes. Also, in my experience this ad hides itself behind a fake ad when it detects dev tools being open. So if you have dev tools open it presents as a normal ad, only loading when it looks like it has found non savy prey. Fun!
    1. …in reply to @Chronotope
      robinberjon clancynewyork steveglista swodinsky anniesullie This ad was really common for a while and I actually built a basic browser plugin that protects myself from this type of hijack while allowing good ads to load so I don't rob monetization from a publication. Pretty basic, just sandboxes all iframes. github.com/AramZS/AdSandbox
      OpenGraph image for github.com/AramZS/AdSandbox
  1. …in reply to @Chronotope
    robinberjon clancynewyork steveglista swodinsky anniesullie We actually saw something very similar in iOS apps too, and enacted active countermeasures to protect our readers - washpost.engineering/2019/05/28/the-ad-performance-and-safety-protocol-cleaner-better-safer-ad-experiences-on-ios/
    OpenGraph image for washpost.engineering/2019/05/28/the-ad-performance-and-safety-protocol-cleaner-better-safer-ad-experiences-on-ios/


Search tweets' text