News for hackers. Stuff that matters.
Re:Google Will Help Publishers Prepare for a Chrome Ad Block... by Akujin on Thursday June 01, 2017 @04:33PM (#14464341)
The images were being served through a PHP passthrough script at /media/$ID

You would have no way of knowing if the image was an ad or part of the article content since they were all served through the same thing. No silly subdomains like ad.domain.com either.

Re:Google Will Help Publishers Prepare for a Chrome Ad Block... by JoshTriplett on Thursday June 01, 2017 @04:45PM (#14464497)
> You would have no way of knowing if the image was an ad or part of the article content since they were all served through the same thing. No silly subdomains like ad.domain.com either.

Still quite feasible to detect by size and styling.

Re:Google Will Help Publishers Prepare for a Chrome Ad Block... by ceejayoz on Thursday June 01, 2017 @05:01PM (#14464677)
Not if they mimic the size/styling of, say, images in the articles.
Re:Google Will Help Publishers Prepare for a Chrome Ad Block... by JoshTriplett on Thursday June 01, 2017 @05:12PM (#14464802)
If you make your ads look exactly like content, devaluing your actual content, then yes, you can mask ads more easily.
Re:Google Will Help Publishers Prepare for a Chrome Ad Block... by soared on Thursday June 01, 2017 @05:15PM (#14464830)
That makes it a native ad and not a display ad, which can change the discussion quite a bit.
Re:Google Will Help Publishers Prepare for a Chrome Ad Block... by jlarocco on Thursday June 01, 2017 @08:59PM (#14466587)
That doesn't change anything, it just makes your site more annoying. I block "one off" ads like that every time I notice them. If I have to keep doing it then I just turn off images for the page.

I wish web developers had more respect for their audience. If I say, "No ads," I really mean "No ads." Your site is not a special snowflake where I suddenly don't mind seeing advertisements.

Re:Google Will Help Publishers Prepare for a Chrome Ad Block... by Akujin on Friday June 02, 2017 @04:18PM (#14472982)
I think you missed the part where I mentioned the content was targeted towards dentists and dental professionals. Our typical visitor would be a dentist in his 50s or 60s looking up some medical text. They generally had almost no technical expertise with the web or computers. Let alone ad blockers.

I'm also not sure what you mean by "respect for their audience". If I put an ad on a website I didn't ask your opinion and frankly I don't care what you think. Unless you wanna pay my bills. If what you're saying is I should detect the existence of ad block and actually proactively stop writing the code for said ad into the website.....well... that's just silly.