"I would use a browser with javascript disabled".
See, this is the point where AMP provides actual benefit. Many sites don't function at all without JS. AMP gives me a site that actually works without the extra crap.
I decided to disable AMP on my site
161–170 of 360 posts
Re: I decided to disable AMP on my site
#162I have a visual impairment and one of the things I love about Chrome on Android is the ability to override sites blocking pinch to zoom (i.e. "force enable pinch to zoom"). AMP, also made by Google, seems to somehow get around this browser setting, making AMP sites unreadable and therefore completely useless to me. Why does Google have these obvious discrepancies between their own products?
AMP with Chrome on Android also breaks the back button on many (all) sites? If you pass through several links within a site, then hit back, Google will forget all that and dump you back to search results. Disable AMP and the problem goes away.
Re: I decided to disable AMP on my site
#163Earlier quoted context omitted.
You remember Akamai, right? AMP is just another CDN. Back in the 90s, when Akamai was fighting to establish themselves, you'd see tons of fetches from hosts like a123.d.akamai.com on big name properties like CNN. Nowadays it's pretty much hidden, and pervasive. Google is attempting to entrench a reverse proxy cache the same way Akamai has for years. AMP is nothing new. The only difference here is that they make it ob…
Yeah but Akamai is optional. Google's CDN / cache in AMP isn't. Big difference.
How is Akamai optional for a user? If you're saying that it's optional for publishers, then your argument doesn't make sense since AMP is optional for publishers as well (I mean, the author disabled it and all).
Re: I decided to disable AMP on my site
#164Earlier quoted context omitted.
And as I user, I've never had any issues and I still don't really see the whole fuss about "copying the link being much harder ". I love the much much faster load times and couldn't be happier.
As a user, I don't mind AMP. The Web is a mostly hostile place for end users. Malicious ads, 5MB+ pages just so you can read a 1 minute text article, auto-playing videos with volume set to 100%, obtrusive ads - AMP aims to fix this crud and give users a better browsing experience. Ideologically, I'm opposed for all the reasons listed in TFA. People work to create something, yet the content and website are being ferri…
You make good points on the size of pages and load speed. How about instead of AMP we have something that's hosted on the server instead? Something like RSS but with built in single-article views and a standard (or at least lightweight) framework?
On the other hand you say AMP aims to fix this - anyone doing that for the ad views etc would simply not enable AMP on their site. AMP does not fix this.
Re: I decided to disable AMP on my site
#165> On iPhone, AMP seems to override the default browser scrolling. As a result scrolling of AMP pages feels off. Good news! iOS 11 fixes this. Safari actually has an inconsistent scrolling speed compared to the rest of the OS. iOS 11 makes all Safari pages scroll at the same speed as AMP sites (-webkit-overflow-scrolling: touch) Also important distinction for people to remember - AMP is two products: - CDN with preloa…
In my mind I actually separate it into three (from Google):
- The specs/docs for building AMP pages, which can be found on www.ampproject.org - note that, a lot of these are non-free, like standardized components for specific media/social sites, and requires you to include script tags for cdn.ampproject.org component implementations. This all tells you how to add an AMP version of your page to your site, and how to link it to the original content.
- The "Google AMP Cache" CDN that hosts cached versions of AMP pages under .cdn.ampproject.org - it seems that anyone can use this...? Note these are in a separate context than the google search result page (that people think of as "AMP pages") which means a generic XSS on AMP isn't an XSS on google.com.
- The integration into Google Search. On the frontend this looks like some javascript that preloads iframes to the .cdn.ampproject.org page for results, and also uses History.pushState() to give you the google.com/amp/foo.com/ urls. If you go to those URLs directly you'll get redirected (that's the server-side implementation of them and why you don't ). There's also some crawler (and ranking?) implementation too, presumably.
A lot of discussion about AMP seems to muddy all three of these things together, which is a bit unsurprising considering Google's messaging muddles them together, but I think it's important to distinguish between them. In the "Twitter AMP redirect" case of the article, only the first portion is coming into play.
As an aside - if you're interested in seeing how AMP works under the hood I highly recommend the Chrome Android USB debugging - I hadn't played with this before trying to figure out how AMP worked and it was really a godsend to be able to "Inspect Element" on my phone, especially because anything AMP-related is very aggressive about only AMPing to phones on cell networks.
Re: I decided to disable AMP on my site
#166The author has some very valid points against AMP from a technical standpoint, but for me there is a single reason that is sufficient: the Web is, and should stay, free and open . Indeed, I'm having really hard time trying to understand how people can be fine with AMP while fighting for the net neutrality and so on.
AMP is opt in. Full stop. You choose to participate in AMP. You can't choose to not be throttled by an ISP, or to bypass censorship.
That's an over-simplification:
1. Users have no control: if you want real URLs or the full experience, you have to work around AMP or stop using Google.
2. It's technically true that publishers can choose whether to use AMP but Google rank is a make-or-break issue for many publishers and that means the decisions is made under the threat of losing out to competitors who use AMP even if your site is already just as fast using non-proprietary tooling.
It would be much better for the open web and innovation in general if Google maintained a separation between the two and only used the real user experience when deciding ranking or placement in the special top results carousel.
Re: I decided to disable AMP on my site
#167There's a deep irony in AMP also, purely anecdotally it doesn't seem to help with slow connections. I'm traveling and as such my US carrier restricts me to 2G speeds while roaming somehow, which is resulting in me seeing a lot of butchered pages. As the author mentions: > AMP tries to load an image only when it becomes visible to the user, rendering a white square instead of the image. In my experience I’ve seen it f…
You're saying that AMP doesn't help with slow connections, based on AMP not loading all resources on 2G. But you're missing the data point for non-AMP pages on 2G. Are you sure it's not even worse? It's hard to believe how bloated many modern websites are, before trying to load them over 2G. We're talking megabytes of data and tens of connections to display what should be a 20kB of text.
If a regular page doesn't load on a 2G connection and an AMP page doesn't load on a 2G connection.. what's the point of AMP?
Re: I decided to disable AMP on my site
#168Earlier quoted context omitted.
AMP is pretty much mandatory. If you don't do it you're "left behind."
Unless everybody drops it. These Google incited arms races in the end help nobody but Google, it's a web scale version of the prisoners dilemma.
I hope publisher's drop it and take with them a few lessons about showing a little respect for the audience.
Re: I decided to disable AMP on my site
#169Earlier quoted context omitted.
Yeah but Akamai is optional. Google's CDN / cache in AMP isn't. Big difference.
How is Akamai optional for a user? If you're saying that it's optional for publishers, then your argument doesn't make sense since AMP is optional for publishers as well (I mean, the author disabled it and all).
It's not when the technology gives you an advantage in search ranking through the AMP green square in the search results and the quick answer tiles.
Re: I decided to disable AMP on my site
#170Earlier quoted context omitted.
you are forced to login to FB, is the same true with AMP?
Whatever Google wants you to do to access the content. Once it is on their domain, they have full control over it.
It's not on their domain though. Or at least, it's not _only_ on their domain. Google is just caching content served from the publisher's domain; you can access that content just fine without going through Google.