Re:Google AMP Cache, AMP Lite, and the Need for Speed
by jgrahamc on Thursday January 12, 2017 @10:13AM
(#13382772)
Cloudflare just launched its own AMP viewer and cache: https://blog.cloudflare.com/accelerated-mobile/
Re:Google AMP Cache, AMP Lite, and the Need for Speed
by sdfhbdf on Thursday January 12, 2017 @10:18AM
(#13382825)
It didn't launch its own AMP. They are now supporting Google's AMP by replacing all links on CloudFlare powered webpage into AMP ones with that little thunderbolt.
Re:Google AMP Cache, AMP Lite, and the Need for Speed
by jgrahamc on Thursday January 12, 2017 @10:21AM
(#13382854)
It's the same standard but it's Cloudflare's own viewer, cache and the AMP URLs are managed by Cloudflare and not Google.
Re:Google AMP Cache, AMP Lite, and the Need for Speed
by neilcarpenter on Thursday January 12, 2017 @10:39AM
(#13383025)
AMP is open - https://github.com/ampproject/amphtml
Re:Google AMP Cache, AMP Lite, and the Need for Speed
by pmlnr on Thursday January 12, 2017 @11:33AM
(#13383593)
If I can't host it, it's not open, end of story.
With AMP, it's always by google.
This is not open, there is no source, because AMP is a hosted service.
Re:Google AMP Cache, AMP Lite, and the Need for Speed
by e12e on Thursday January 12, 2017 @11:30AM
(#13383560)
That's what's so insidious.
You enable amp, like maybe you started using png over just gifs - and then Google takes your search hits hostage by rewriting the url, adding a banner - and forcing you to keep the amp version if it turned out to fit you and your users or not.
The amp spec looks friendly and harmless - a good use of html5's flexibility. On the surface the only odd bit is the reliance of js to get the "new" image tags to work (with resulting reduced flexibility wrt Web user agents, like w3m).
And suddenly Google controls your page design for everyone that finds your site through Google!
Re:Google AMP Cache, AMP Lite, and the Need for Speed
by wmf on Thursday January 12, 2017 @03:29PM
(#13385801)
Here's an open version of AMP in the works: https://wicg.github.io/ContentPerformancePolicy/
I'd still like to push for an open, standards based approach to tackling the issue of content delivery under resource constraints.