4 ms·

I've been critical of AMP in some previous posts, but an AMP like infrastructure has the impressive advantage of trying out such optimizations and solutions, wi

I've been critical of AMP in some previous posts, but an AMP like infrastructure has the impressive advantage of trying out such optimizations and solutions, without a large affect on the users. I'd still like to push for an open, standards based approach to tackling the issue of content delivery under resource constraints.

wmf 10y ago
Here's an open version of AMP in the works: https://wicg.github.io/ContentPerformancePolicy/ https://wicg.github.io/ContentPerformancePolicy/
jgrahamc 10y ago
Cloudflare just launched its own AMP viewer and cache: https://blog.cloudflare.com/accelerated-mobile/ https://blog.cloudflare.com/accelerated-mobile/
- sdfhbdf 10y ago
  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.
  - jgrahamc 10y ago
    It's the same standard but it's Cloudflare's own viewer, cache and the AMP URLs are managed by Cloudflare and not Google.
neilcarpenter 10y ago
AMP is open - https://github.com/ampproject/amphtml https://github.com/ampproject/amphtml
- e12e 10y ago
  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!
- pmlnr 10y ago
  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.
  - deleted 10y ago
    [deleted]

wmf 10y ago

Here's an open version of AMP in the works: https://wicg.github.io/ContentPerformancePolicy/ https://wicg.github.io/ContentPerformancePolicy/

jgrahamc 10y ago

Cloudflare just launched its own AMP viewer and cache: https://blog.cloudflare.com/accelerated-mobile/ https://blog.cloudflare.com/accelerated-mobile/

sdfhbdf 10y ago
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.
- jgrahamc 10y ago
  It's the same standard but it's Cloudflare's own viewer, cache and the AMP URLs are managed by Cloudflare and not Google.

neilcarpenter 10y ago

AMP is open - https://github.com/ampproject/amphtml https://github.com/ampproject/amphtml

e12e 10y ago
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!
pmlnr 10y ago
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.
- deleted 10y ago
  [deleted]