The End of AMP
51–60 of 166 posts
Re: The End of AMP
#52My favorite way to avoid AMP is to use DuckDuckGo. :)
Re: The End of AMP
#53In fact, I suspect it will only affect the small minority of sites that work better without AMP, the ones everyone who dislike AMP talk about. But for most mainstream news sites, I find AMP better than the typically bloated non-AMP version. And I bet Google will have the same opinion when ranking sites.
This is excellent news, but unfortunately, I don't think it will change the situation much. I wish it would, but most websites owners simply don't care about performance.
Re: The End of AMP
#54Whenver i am trying to share a news article with a friend, and Google throws up the AMP page at me, I take the time to select the original article link and share that. Websites deserve their own traffic, not Google's.
Is that very different from "Whenever I find a site hosted through CloudFlare, I look up the origin server's IP address and link to that. Webservers deserve traffic, not CDNs."?
If cloudflare removes your link, you can easily just change provider.
Re: The End of AMP
#55> AMP also came with the unfortunate requirement that publishers let traffic sources such as Google cache their content and serve it from their domain, such as google.com. I think this is backwards. Google offers to host your content on their domains, and if you want that it requires you to use certain markup, and only certain ads. If your job is monetizing content, or if you want to raise some abstract "time spend o…
But that was not the problem. There's nothing intrinsically wrong with Google offering AMP as a content hosting service subject to certain syntax and content limitations.
The problem was that, however fast your load times were in practice, all else being equal Google's search engine would penalise your ranking compared to using Google's AMP—all under the pretence of favouring "very fast load times".
Re: The End of AMP
#56Please don’t let your excitement take your focus off this part of the story: > The good news gets even better; non-AMP pages make considerably more revenue per pageview than AMP pages. Initially, I assumed this was due to the nature of how ads load on AMP, however, recent Antitrust lawsuits have proposed that hindering ad competition was a feature and that all non-amp ad tags, such as my company, Ezoic’s, were delaye…
Re: The End of AMP
#57Whenver i am trying to share a news article with a friend, and Google throws up the AMP page at me, I take the time to select the original article link and share that. Websites deserve their own traffic, not Google's.
Is that very different from "Whenever I find a site hosted through CloudFlare, I look up the origin server's IP address and link to that. Webservers deserve traffic, not CDNs."?
You cannot switch AMP cache to another vendor if you want Google rank your AMP site higher. [2] You also need a speical TLS certificate with the CanSignHttpExchanges extension that can only be get from DigiCert (for a price)[3] and not from Let's Encrypt [4].
[1] https://unlikekinds.com/article/google-amp-page-speed [2] https://stackoverflow.com/a/41683427 [3] https://web.dev/how-to-set-up-signed-http-exchanges/#step-1 [4] https://community.letsencrypt.org/t/cansignhttpexchanges-ext...
Re: The End of AMP
#58Whenver i am trying to share a news article with a friend, and Google throws up the AMP page at me, I take the time to select the original article link and share that. Websites deserve their own traffic, not Google's.
Is that very different from "Whenever I find a site hosted through CloudFlare, I look up the origin server's IP address and link to that. Webservers deserve traffic, not CDNs."?
Using a different CDN shouldn't significantly impact a site's income, but using AMP may have.
Re: The End of AMP
#59So I know nothing about AMP, but I've skimmed through the Google's documentation of signed exchanges, and it seemed like a good thing. I assume that it is the foundation of AMP. Isn't the point of signed exchanges that you, the publisher, don't have to invest in beefy servers and CDNs, and instead rely on third parties (for fee or free) to store the (signed) content? Of course AMP being a Google service the monopoly thing is hard to ignore.
> AMP created all kinds of problems, from analytics to ad serving to logins.
Oh no, it hinders competition with Google for surveillance and ad spam!
Re: The End of AMP
#60Please don’t let your excitement take your focus off this part of the story: > The good news gets even better; non-AMP pages make considerably more revenue per pageview than AMP pages. Initially, I assumed this was due to the nature of how ads load on AMP, however, recent Antitrust lawsuits have proposed that hindering ad competition was a feature and that all non-amp ad tags, such as my company, Ezoic’s, were delaye…
I’m as much against AMP as the next YC user, but jailing seems really excessive.