Google Developers Blog:
Today, we’re adding a feature to the AMP integration in Google Search that allows users to access, copy, and share the canonical URL of an AMP document.
My biggest issue with AMP is the difficulty in turning a Google-AMP formed URL back into a non-AMP URL I can share. For example, here’s an AMP formed URL from the Google News page:
https://news.google.com/news/amp?caurl=https%3A%2F%2Fwww.washingtonpost.com%2Famphtml %2Flocal%2Feducation%2Fsenate-to-vote-today-on-confirmation-of-betsy-devos%2F2017%2F02%2F06%2Ffd4b7e9c-ec85-11e6-9662-6eedf1627882_story.html#pt0-135000
As you can plainly see, the original URL is encoded, then wrapped. Only way to easily pass this along is to send your recipient through Google’s site, not to the site that wrote the story in the first place. The biggest issue I have here is that of supporting the creator here. They deserve the page views.
More from the Google blog:
Today, we’re adding support for this functionality in form of an anchor button in the AMP Viewer header on Google Search. This feature allows users to use their browser’s native share functionality by long-tapping on the link that is displayed.
This is an excellent first step. Basically, even if the URL is encoded (as shown above), you can still click on the anchor button to copy the original URL. However, if you click in Safari’s address bar, you’ll still see the encoded URL.
My 2 cents: I’d love it if Apple offered a way to opt out of AMP. As Google says in the blog, AMP opens the door to confusion, makes URL phishing harder to detect since all URLs are harder to read, and the original URL hidden from the user.