As a publisher it really sucks. The DSPs must know these ads are shit. It would be trivial to filter them with a bit of AI.
I've asked my Google partnered SSP to disallow ethically bankrupt ads like gambling, alcohol etc. They say "we've asked the partners to block those categories"... and then it just keeps happening. They're either unable or unwilling to help.
I had to take ads down for several days at my own expense due to rogue ads. The ads are now in safe frames which doesn't pay quite as well but I'm okay with it.
This. When it's a person the original quote applies. But big companies have millions of data points on everything and are competent in areas they care about like their own profit. So you can assume it's not ignorance. They don't care if a publisher has to spend loads of time resolving issues rogue ads and malvertising because it doesn't affect them and the end user just blames the publisher.
Suppose a secret like some personally identifying information was recently leaked into the main branch. You are legally required to scrub it. How do you fix it?
Ideally a repo needs to reflect the state of every event that happened. Practically there are edge cases when it's just best to rewrite history.
reply