3 ms·

If Twitter is redirecting to the original URL, what's the problem? It muddies the claim of those that oppose AMP so fervently to mix AMP the framework with the

by berns 9y ago

If Twitter is redirecting to the original URL, what's the problem? It muddies the claim of those that oppose AMP so fervently to mix AMP the framework with the use that Google makes of AMP. The publisher has decided to use this technology to make their mobile page. It's perfectly valid (and well engineered) HTML and javascript. Asking for a non AMP version of a page is like asking for the non React page or the non Bootstrap page.

sp332 9y ago
Google recommends that the "canonical" link always be the one that gets shared. https://news.ycombinator.com/item?id=15086192 https://news.ycombinator.com/item?id=15086192 Implementations have been ignoring this, but it does seem more predictable, and also less likely to break if a publisher removes AMP later.
- LoSboccacc 9y ago
  And deep linking be damned right? Now we have to mess with the canonical url to include the deep linked resources so that sharing works and a page that could have been static need dinamic generation of their meta
akras14 9y ago
It's not, it's redirecting to the AMP version, even if non AMP link was shared. See: https://www.alexkras.com/i-decided-to-disable-amp-on-my-site/ https://www.alexkras.com/i-decided-to-disable-amp-on-my-site...