How is that happening? AMP renders in every browser. My proposal was to allow customizing share URLs. Generally useful.
-
-
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 -
It is a key distinction from tech like WAP.
1 reply 0 retweets 0 likes -
Replying to @cramforce @seldo
But it's not a key distinction from 90s MSFT, which for example openwashed OOXML.
2 replies 0 retweets 2 likes -
Bottom line is that I think it's reasonable to believe that the current structure is not a good fit for a web standard.
1 reply 0 retweets 2 likes -
It's also reasonable to believe that the reason for AMP's nominal success is anticompetitive use of Google's search dominance.
2 replies 1 retweet 2 likes -
Replying to @wycats @cramforce
I definitely feel like Google is cramming this down my throat, but "anticompetitive" implies competition to solve whatever it is AMP solves.
1 reply 0 retweets 0 likes
What I mean is that Google search is a monopoly, and they're abusing the monopoly to force publishers to use it.
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.