To my Google AMP friends: I have nothing against the tech or the OSS project. Pls encourage your search colleagues to stop privileging AMP.
-
Show this thread
-
If you were involved in the strategic decisions that led to Search prioritizing AMP content, please reconsider.
1 reply 6 retweets 39 likesShow this thread -
If there are technical issues that makes the carousel impl coupled to AMP as a tech, unprivileging AMP should help us prioritize stds.
1 reply 2 retweets 15 likesShow this thread -
If you think there's nothing wrong with privileging AMP, or that it's only slightly dubious, please reconsider.
1 reply 16 retweets 35 likesShow this thread -
If we're all on the same side, as you so often say, please eliminate the handshake that is allowing you to avoid standardizing.
2 replies 4 retweets 16 likesShow this thread -
Replying to @wycats
And when standardizing—consider that AMP prioritizes sites monetizable by search engines, but may not benefit the open web powered by HTML.
1 reply 0 retweets 0 likes -
Replying to @trimryan
The top priority for standardization should be "instant" rendering from a cross-origin site.
1 reply 0 retweets 2 likes -
Next might be a rendering mode that effectively disables functionality that triggers multipass rendering.
1 reply 0 retweets 0 likes -
The fact that AMP requires the defacto standardization (by a private entity) of new HTML tags for interactive content must be temporary
1 reply 0 retweets 1 like
But seriously, if they keep privileging AMP, they have no incentive at all to prioritize standardization.
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.