@zachleat’s avatar@zachleat’s Twitter Archive

Tweets about AMP

Not including retweets.


⬅️ New ⬆️ 🙂
⬇️ 🙁


  1. “As part of this update, we'll also incorporate the page experience metrics into our ranking criteria for the Top Stories feature in Search on mobile, and remove the AMP requirement from Top Stories eligibility.” Well—this is good news! webmasters.googleblog.com/2020/05/evaluating-page-experience.html
  2. …in reply to @rauchg
    rauchg Fair but if they sell this as an AMP need for an immediate AMP problem (which it very much is) it will be a hard sell for Mozilla or Apple. 😅
  3. …in reply to @rauchg
    rauchg “Catching up” is a weird way of phrasing that. We’ll see what happens but I’d be surprised if this solution to this very AMP-specific problem gets any traction from other browsers.
  4. seeing URLs like this hurts me deep in my bones https​://www-theverge-com.cdn.ampproject.org/c/s/www.theverge.com/platform/amp/2020/4/3/21207643/zoom-security-privacy-zoombombing-passwords-waiting-rooms-default
  5. Last week I was ornery joking about putting AMP sites in a carousel buried at the bottom. But it made me think—if I think search results should give no preferential treatment to AMP sites—the whole thing should be sorted by raw performance. So I did that: 11ty.dev/docs/sites/
  6. …in reply to @scottjehl
    scottjehl is ajit pai talking about AMP again
  7. …in reply to @sebabenz
    sebabenz AMPhtml eleven_ty What is a “Blue link” here? I know there has been a lot of discussion about the specific definition of “ranking”. It seems as though most of if not all real-world discussion about using AMP is circling the SEO benefits so “ranking” a red herring for me
  8. …in reply to @sebabenz
    sebabenz AMPhtml eleven_ty I had a think about it and a re-read of my original tweet and I think you’re right—the tone definitely missed the mark there—sorry! But I have just had another look and it seems now y’all are showing the AMP icon for results outside of the carousel? This seems worse than before?
  9. …in reply to @sebabenz
    sebabenz AMPhtml eleven_ty I don’t think *hate* is the right word! I think a few lighthearted jabs are certainly fair given the bad incentive structure that AMP has set up. Personally, I’d rather if Eleventy wasn’t a part of the AMP ecosystem at all but I don’t have that sort of power (nor should I)
  10. …in reply to @triblondon
    triblondon former AMP dev? 😅
  11. …in reply to @jaffathecake
    jaffathecake DasSurma dollar in the amp url jar jake
  12. …in reply to @RWD
    RWD typetura css eleven_ty ScottKellum & did it first and better imo
  13. I want to see these graphs but for AMP and React. briankardell/1194314471491035136
  14. On his blog, AMP Advisory Committee member edent has posted a scathing review of AMPhtml and his recommendations moving forward: shkspr.mobi/blog/2019/05/a-report-from-the-amp-advisory-committee-meeting/
  15. …in reply to @rem
    rem 🗑🔥🚀🌕👏 without an amp care-o-sell in the world
  16. …in reply to @davatron5000
    davatron5000 AMP is a Trojan horse.
  17. …in reply to @zachleat
    oh god I've shared an amp url
  18. Reply to this thread with your AMP performance comparisons and I'll retweet/share a bunch of them 👍🏻 zachleat/1068867361472696321
  19. …in reply to @kylemathews
    kylemathews joeyquarters DaryBarrio I think it's an important performance story that isn't really told, though. AMP is faster from the carousel but slower when visited directly. I see AMP urls shared on social media regularly: twitter.com/search?q=google.com%2Famp%2F&s=09
  20. A race against AMP: this site does a full two seconds better for first meaningful paint compared to AMP hosted on Google. Nice work DaryBarrio! DaryBarrio/1067817156178513921
  21. …in reply to @WebInspectInc
    @TJacobDesign Sure, but the same argument is used against consumer recycling too. Mostly I’d love to profile the energy usage of my sites and try to make them more efficient if possible—great for energy-constrained mobile devices Not sure how AMP is related?
  22. Google Wants To Kill The URL, writes lilyhnewman for WIRED Read the article at google​.com/amp/s/www.​wired​.com/story/google-wants-to-kill-the-url/
  23. …in reply to @grigs
    grigs *Especially* given the damage that's been done to URLs from AMP. Seems like they're working to repair that, but it definitely doesn't pair well. 😐
  24. …in reply to @davatron5000
    davatron5000 is this an amp tweet
  25. “To put a finer point on it, nothing about AMP is changing today, in the short-term, nor in the medium-term.” beep is on-point with another solid AMP roundup ethanmarcotte.com/wrote/campaign/
  26. …in reply to @angustweets
    angustweets is this a promotional tweet for amp for email (also, same)
  27. …in reply to @ChrisLove
    ChrisLove AMP can exist in a positive way AND we can do the thing you said 👍
  28. …in reply to @cramforce
    cramforce AMPhtml Thanks for your reply! That’s good news—what might that look like, practically speaking? I do feel strongly that an official roadmap that lives on an AMP maintained web property would be great for communicating what’s happening and what’s being addressed 👍
  29. …in reply to @zachleat
    AMPhtml I still have mixed feelings about this. Happy to see money flowing to support open source sustainability. Hopefully, it doesn’t stifle healthy discussion from developers on these projects about the problems with Google’s AMP project.
  30. …in reply to @beep
    beep I guess t.co does amp urls now 😫 apropos to the gif, I guess
    oh my god twitter doesn’t include alt text from images in their API
  31. …in reply to @zachleat
    also cc DuckDuckGo maybe y’all shouldn’t show the first answer on stackoverflow that has 0 upvotes you’re giving it the fake news amp treatment
  32. …in reply to @AMPhtml
    AMPhtml AaronGustafson DasSurma what is causing FOUC? amp styles seem to be inlined on the page here
  33. …in reply to @AMPhtml
    AMPhtml AaronGustafson DasSurma Well, what are your reqs? Other reasons to make whole page invisible instead of FOIT? Do you optimize pages w/o amp-font too?
  34. …in reply to @zachleat
    AMPhtml AaronGustafson DasSurma for example, this demo on the amp documentation: ampbyexample.com/samples_templates/live_blog/preview/ could’ve rendered at 468ms albeit with foit, no?
    oh my god twitter doesn’t include alt text from images in their API
  35. hmu when ⚡️ amp offers google plus integration