No, our policy is that AMP platforms should share the canonical URL when technically possible.
-
-
Replying to @cramforce @seldo
This makes it technically possible. I’m advocating for a more general solution, but I’ll take the hack for now :)
1 reply 0 retweets 13 likes -
Replying to @cramforce
You know I have all the respect in the world for you personally, but I continue to think AMP is un-weblike and a bad idea.
4 replies 1 retweet 57 likes -
Replying to @seldo @cramforce
Persuading all browsers in the world to adapt to a format a single company invented and maintains for its own benefit is like 1990s Msft.
2 replies 1 retweet 47 likes -
Replying to @seldo
How is that happening? AMP renders in every browser. My proposal was to allow customizing share URLs. Generally useful.
3 replies 0 retweets 2 likes -
Replying to @cramforce @seldo
The issue is that the spec of supported web components is maintained and decided almost exclusively by Google.
3 replies 1 retweet 5 likes -
This is an easy point to make, but have you actually experienced the process?https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md …
1 reply 0 retweets 0 likes -
Yes, we have a BDFL model. I’m open to changing it, but the request has to come from members of the community not random internet people.
2 replies 0 retweets 0 likes -
Replying to @cramforce @seldo
It just means that the claim that "amp renders in every browser" is missing the most important issue.
2 replies 0 retweets 1 like -
Random internet people are interested in who makes the spec for "the web". You've found a hack where the answer is "Google"
1 reply 0 retweets 1 like
Yehuda Katz 🥨 Retweeted Malte Ubl, Immigrant
Random internet people are allowed to have a problem with that and reject this response to the critique.https://twitter.com/cramforce/status/900555298397487104 …
Yehuda Katz 🥨 added,
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.