Chronotope’s avatarChronotope’s Twitter Archive—№ 82,290

    1. …in reply to @Chronotope
      Always was going to be an issue. We adopt these things without fixing the ad server at the source of the problems. Chronotope/722588312679092225
      1. …in reply to @Chronotope
        "The gap between content and ads loading persists even though Google has worked on the issue since AMP launched about 20 months ago."
        1. …in reply to @Chronotope
          It baffles me that Google would rather attempt to take over the internet and unseat web standards then *fix their ad server and ecosystem*
          1. …in reply to @Chronotope
            - PUT REAL, AUTOMATICALLY ENFORCED, CODE STANDARDS INTO PLACE - ENFORCE SIZE RESTRICTIONS - LIMIT THE AMOUNT CALLS HOME - REFORM VPAID !!!
            1. …in reply to @Chronotope
              Anyone who paid attention knew this was going to be an issue from Day 1 of AMP Chronotope/689528778905763841
              1. …in reply to @Chronotope
                Notable: "Six publishing sources, requesting anonymity out of fear of angering Google" "are scared of acting against the platform’s wishes"
                1. …in reply to @Chronotope
                  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.
                  oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API


Search tweets' text