Tags: amp

In AMP we trust [↗]

Jeremy Keith on AMP, concludes with:

Google says it can’t trust our self-hosted AMP pages enough to pre-render them. But they ask for a lot of trust from us. We’re supposed to trust Google to cache and host copies of our pages. We’re supposed to trust Google to provide some mechanism to users to get at the original canonical URL. I’d like to see trust work both ways.

And there lies the rub. My trust levels for Google are very low. I’ve been around long enough to know that hosted Google services/projects come-and-go with little regard to their users. Wave, Jaiku, Buzz, Reader, Knol, the list is quite impressive.

I know AMP is different from the services on the aforementioned list, but the trust damage has already been done. For me, AMP will need to fully establish itself and showcase real benefits, before I trust it enough to invest any development time in it. I’m doubtful that’ll ever happen.

248: AMP – ShopTalk [↗]

Getting AMP’d with AMP. We’re going to talk about the #hotdrama about AMP with a couple of AMP experts.

Before listening to this episode, I was completely uninterested in AMP. After listening, I’m still uninterested. The proponents did nothing to sell it to me.

That said, I can imagine how AMP could be good for end users. For example, last night I was listening to a podcast and browsing the web on my iPhone, I had just started reading an article on Boing Boing when a video advert started playing, which in-turn muted the podcast that I was listening to. Grrr. I’m thinking that AMP could have prevented this annoyance, but then again, I’m also thinking the owners of Boing Boing could also have prevented it by not deploying obnoxious ads.