Chronotope’s Twitter Archive—№ 88,244

This is all true, but what goes unsaid and is far worse is that the bad ads that Google's Chrome is blocking *can't be blocked in Google's ad server or exchange*. So you could use nothing but Google software in monitizing your site and Google could blacklist you. FrankPasquale/965229893150760960
Permalink On twitter.com ♻️ 10 Retweets ❤️ 33 Favorites 2018 Feb 18 Mood -6 🙁

…in reply to @Chronotope
The irony is that if you're a medium to large news site and you're reading this the first reaction you should have is: time to stop using DFP and AdX and find tools that give these controls. *Because Google does not*
Permalink On twitter.com ♻️ 2 Retweets ❤️ 8 Favorites 2018 Feb 18 Mood -2 🙁

…in reply to @Chronotope
There's this notion that publishers want to push shitty ad experiences on you. We don't! But the programmatic markets, where all the most prominent tools are made and run by Google, don't allow publishers full control.
Permalink On twitter.com ♻️ 5 Retweets ❤️ 17 Favorites 2018 Feb 18 Mood -1 🙁

…in reply to @Chronotope
Like AMP, this action falls into the category of 'things that should be done, but not by Google', because the context that Google brings is *dominance*.
Permalink On twitter.com ♻️ 1 Retweets ❤️ 6 Favorites 2018 Feb 18 Mood +2 🙂

…in reply to @Chronotope
We should feel deeply uncomfortable with Google dictating what the web should look and act like because they are the only ones who can hold entire companies hostage to those decisions. It's an immortal, dangerous, approach, worse because they don't understand why that's so...
Permalink On twitter.com ❤️ 7 Favorites 2018 Feb 18 Mood -3 🙁

…in reply to @Chronotope
They don't need to be doing this. All the problems that AMP and the Chrome ad blocker propose to solve would be better solved by: Fixing Their Own Ad Tech And solving it that way would accrue none of the blowback or discomforting pressure on the web that their current path does
Permalink On twitter.com ♻️ 5 Retweets ❤️ 16 Favorites 2018 Feb 18 Mood +2 🙂

…in reply to @Chronotope
It's hard to imagine any company has ever before stepped into a pitched battle with itself, having its different business verticals at war with each other, with such idiotic abandon. It's locked in a deathgrip with itself and the open web is the throat.
Permalink On twitter.com ♻️ 2 Retweets ❤️ 6 Favorites 2018 Feb 18 Mood -9 🙁

…in reply to @Chronotope
Dear Google, fix your own crap before holding websites accountable for the problems you are also causing.
On twitter.com ♻️ 2 Retweets ❤️ 4 Favorites 2018 Feb 18 Mood -3 🙁

…in reply to @Chronotope
And it would be so easy for Google to do this. So little work to fix their exchange & ad server to stop bad ads at that level. It's ludicrous that Google engineered an entirely new JS library, altered its browser and manipulated a committee rather than add checks to their ad tech
Permalink On twitter.com ♻️ 1 Retweets ❤️ 5 Favorites 2018 Feb 18 Mood -7 🙁

…in reply to @Chronotope
It was true with AMP and it is true now, no one is in a better position to fix the root of the problem than Google's Ad Tech engineers. Why don't they? Seriously can the next media reporter who gets them on the phone ask? Chronotope/924008311590137861
Permalink On twitter.com ❤️ 5 Favorites 2018 Feb 18 Mood +3 🙂

…in reply to @Chronotope
Seriously, I will write the question for you: Hi Google, why are you building tools into your browser to block ads you distribute through your own advertising technology? Why don't you build those restrictions at the ad server level?
Permalink On twitter.com ♻️ 3 Retweets ❤️ 22 Favorites 2018 Feb 18 Mood -1 🙁

…in reply to @Chronotope
I await a response! I'm genuinely curious because AMP felt evil but this feels stupid and I'm genuinely curious wtf is going on here because it's bad from almost any possible angle.
Permalink On twitter.com ❤️ 6 Favorites 2018 Feb 18 Mood -11 🙁

Search tweets' text