Safari in iOS 11 strips Google AMP links down to original URL for sharing
When iOS 11 launches this fall, users sharing Google AMP pages from Safari will find Apple's operating system automatically remove Google's proprietary URL in favor of the webpage's original format.

The new feature, spotted by MacStories editor Federico Viticci, is present in the latest version of iOS 11 beta that was released on Monday.
Unveiled in 2015, Google AMP, or Accelerated Mobile Pages, is a custom-developed framework for rendering lightweight webpages designed for mobile consumption. Online media entities, including AppleInsider, offer support for AMP, allowing readers to quickly access stories through Google search.
Stripped down to text, rich graphics and video, AMP pages normally sport special links that in many cases do not relate to an originating article's URL. AppleInsider AMP pages do point to the original URL, but pages served up by other media outlets do not.
Currently, users who share AMP pages from iPhone and iPad are forced to share Google's non-standard URLs, which in turn leads recipients to the AMP page. This behavior will change in iOS 11.
"Very nice: when sharing AMP pages to iMessage or Reading List, iOS 11 Safari automatically removes AMP's crap from the URL. Go Apple," Viticci said in a tweet on Wednesday.
As Viticci notes, Safari in iOS 11 reformats AMP's specialized links when sharing story URLs. The feature appears to go further than simply stripping out text, however, as Google obscures or does not include original URL in its AMP page URLs.
For example, the URL for The Verge referenced in Viticci's tweet begins with "www.theverge.com/platform/amp," which leads to the AMP page for that particular story. In another example, USA Today typically formats its AMP pages with "amp.usatoday.com," followed by a story identification number.
In both cases, Safari must perform a backend process to suss out the AMP page's originating URL, then deliver that information in text form for sharing.
Apple is slated to release iOS 11 this fall with a bevy of new features, user interface tweaks and performance enhancements.

The new feature, spotted by MacStories editor Federico Viticci, is present in the latest version of iOS 11 beta that was released on Monday.
Unveiled in 2015, Google AMP, or Accelerated Mobile Pages, is a custom-developed framework for rendering lightweight webpages designed for mobile consumption. Online media entities, including AppleInsider, offer support for AMP, allowing readers to quickly access stories through Google search.
Stripped down to text, rich graphics and video, AMP pages normally sport special links that in many cases do not relate to an originating article's URL. AppleInsider AMP pages do point to the original URL, but pages served up by other media outlets do not.
Currently, users who share AMP pages from iPhone and iPad are forced to share Google's non-standard URLs, which in turn leads recipients to the AMP page. This behavior will change in iOS 11.
"Very nice: when sharing AMP pages to iMessage or Reading List, iOS 11 Safari automatically removes AMP's crap from the URL. Go Apple," Viticci said in a tweet on Wednesday.
As Viticci notes, Safari in iOS 11 reformats AMP's specialized links when sharing story URLs. The feature appears to go further than simply stripping out text, however, as Google obscures or does not include original URL in its AMP page URLs.
For example, the URL for The Verge referenced in Viticci's tweet begins with "www.theverge.com/platform/amp," which leads to the AMP page for that particular story. In another example, USA Today typically formats its AMP pages with "amp.usatoday.com," followed by a story identification number.
In both cases, Safari must perform a backend process to suss out the AMP page's originating URL, then deliver that information in text form for sharing.
Apple is slated to release iOS 11 this fall with a bevy of new features, user interface tweaks and performance enhancements.



Comments
So yeah, good on Google for recognizing the problem and offering a fix. Bad on Google for essentially mandating a fix.
www.theverge.com/platform/amp
or
amp.usatoday.com
Both are hosted on the original domain of the publisher. AMP is simply a set of Javascript libraries to minimize the amount of extra code that has to be loaded with every page request.
Moreover, Google Chrome on mobile devices (both iOS and Android) already does this:
https://www.theverge.com/2017/2/6/14524424/google-amp-update-share-link
For each AMP page, the link button on top reveals (and copies) the canonical version as intended by the publisher (and the URL does become visible when you click it on Chrome). The reason for this is exactly that the publisher domains conveys trust. Presumably, Safari uses exactly the same mechanism as Chrome to get the non-AMP version of a page.
Regurgitating Google talking points don't help you.
AMP was a completely enraging experience. AMP pages don't scroll like normal Safari pages, reader doesn't work on them, links don't work right in them, and they hid the original URL. The updated version that shows the original URL in a header bar is half broken most of the time. Complete garbage. I'm not going to consume the internet while filtered through a crippling pile of garbage like AMP.
Screw Google. They're just another freakishly huge and overbearing corporate monster that thinks it knows what's best for humanity. Their whole business model is to make product out of their users. I wish I wasn't so invested in their gmail service. I should move my saved messages to a local archive. The day Google rids themselves of Gmail, a LOT of internet users will be screwed.
Wonder if this will affect the $3b Google supposedly pays Apple to be the default search engine.
Just give me the real damn link!
As I mentioned earlier perhaps simply down-ranking bloat-sites would be enough to push website admins and designers to think more about how they are designing their pages instead of throwing so many different elements on one. I do think something needs to be done to make mobile web search faster. No evening goes by that I don't find myself while doing a search killing a page-load or two that chokes or takes far too long to load.
Please, not another Google shill.
So I have to load the AMP page first, and then click on the link to reload the full page after wasting time and bandwidth loading the AMP page I had no intention of viewing?
How come you can't see the sheer stupidity of this?