3 ms·
This is a really old article, but as long as we're here: just a quick reminder that the AMP standard still includes platform-specific components that favor indi
by danShumway 7y ago
This is a really old article, but as long as we're here: just a quick reminder that the AMP standard still includes platform-specific components that favor individual companies[0] over smaller creators. It's still not clear what will happen to the components when those services disappear[1], and it's still not clear whether Google has the guts to tell someone like Facebook that a new component feature isn't performant enough to be included.
Quick reminder that the only way to do captchas in AMP is to use Google ReCaptcha.
There are a lot of reasons to hate AMP, but one big reason I hope doesn't get drowned out is that it's not just anticompetitive in the sense of handing control of traffic or hosting to Google. It's anticompetitive in the sense of reducing functionality on the web to a handful of large corporations that have every incentive to reduce diversity and place harsher performance restrictions on competitors than they place on themselves.
[0]: https://amp.dev/documentation/components/?format=websites https://amp.dev/documentation/components/?format=websites
[1]: https://amp.dev/documentation/components/amp-vine/?format=websites https://amp.dev/documentation/components/amp-vine/?format=we...
- buboard 7y agoa website owner converting to amp is no longer an owner, it's a gig worker for google.
- mcv 7y ago> "Quick reminder that the only way to do captchas in AMP is to use Google ReCaptcha." That is terrible. ReCaptcha is the worst. Also, ReCaptcha seems to discriminate against Firefox, and if AMP discriminates against other captchas, this might actually count as monopolistic abuse by EU rules.