-
When you don't fix the problem it continues *being a problem* digiday.com/media/publishers-find-google-amp-loads-fast-ad-views/amp/ Chronotope/651799579030081536Permalink On twitter.com
❤️ 3 Favorites
Mood -4 🙁
-
Always was going to be an issue. We adopt these things without fixing the ad server at the source of the problems. Chronotope/722588312679092225Permalink On twitter.com
Mood -1 🙁
-
"The gap between content and ads loading persists even though Google has worked on the issue since AMP launched about 20 months ago."Permalink On twitter.com
❤️ 1 Favorite
Mood +1 🙂
-
It baffles me that Google would rather attempt to take over the internet and unseat web standards then *fix their ad server and ecosystem*Permalink On twitter.com
❤️ 1 Favorite
Mood 0
-
- PUT REAL, AUTOMATICALLY ENFORCED, CODE STANDARDS INTO PLACE - ENFORCE SIZE RESTRICTIONS - LIMIT THE AMOUNT CALLS HOME - REFORM VPAID !!!Permalink On twitter.com
❤️ 1 Favorite
Mood 0
-
Anyone who paid attention knew this was going to be an issue from Day 1 of AMP Chronotope/689528778905763841On twitter.com
❤️ 2 Favorites
Mood 0
-
Notable: "Six publishing sources, requesting anonymity out of fear of angering Google" "are scared of acting against the platform’s wishes"Permalink On twitter.com
❤️ 1 Favorite
Mood -1 🙁
-
Google, in both its statement of priorities and the words of its engineers doesn't care if publishers make enough of a profit to survive.Permalink On twitter.com
❤️ 1 Favorite
Mood 0