/linked/2017/02/07/sharing-amp-urls

Comments

GrubeTube:
> I am a designer who studies iconography

I just sprayed kombucha out my nose all over my Microsoft Surface as I read this.
9:14 am — Wednesday, 8 February 2017
Sebby:
I hate this. I wish I could just turn off the use of AMP; AdGuard is already quite effective enough. I'm totally ambivalent only because publishers have been asking for this by being utterly fucking inconsiderate for all this time to mobile users. Grubs is right there, at least.
11:04 am — Wednesday, 8 February 2017
jimothy:
Two things that could fix this:

1. Google includes the canonical (i.e., non-AMP URL in the page)
2. When sharing, iOS uses the canonical URL rather than the browser URL

This [Stackoverflow answer](http://stackoverflow.com/a/27845946/) suggests iOS is already doing #2, so it may be that only Google needs to change this.

Interestingly, Google requires web sites to supply the canonical URL on their AMP pages, so apparently, Google strips out that URL when it serves AMP content. Also, of course Google *knows* the non-AMP URL, which is how it creates the kludgy URI described.

These give credence to the Grubester's claim that "Google wants you to pass around the google.com-hosted AMP URL, not the publisher’s original URL."

Die, AMP, Die.

4:11 pm — Wednesday, 8 February 2017
Anonymynous:
>I am a designer who studies iconography

I ran to get my computer for DFWC.

>I am a blogger who studies loose threads hanging off my clothing

TFTFY
8:57 pm — Wednesday, 8 February 2017
Leave a Comment
To leave a comment, install the Safari extension!