16 ms·
The meaning of AMP
- andy_ppp 9y agoGreat article, I despise AMP and Google using its monopoly to peddle these lies, and using this position to embrace and extend open web standards. We have seen this pattern from a monopoly before and they are currently being taken to task for this behaviour in the EU. I’m still a bit amazed that the devs who work on this don’t understand what they are doing is squarely on the side of evil but I guess it’s a pay check. A few other things AMP lies about: * Wastes bandwidth downloading content in the background * Wastes battery rendering content in the background * Downloads Google links you haven’t given permission you want to see * You can’t even opt out * Breaks the web url extending it for Google’s own purposes * Copying URLs to send to friends or post online no longer works correctly * Breaks the understanding that the domain you are on is the authority for it’s own content * Traps publishers further inside Google’s web, not the open web.
- brainfire 9y agoJust to be clear, you work for a company that presents itself as "The best way to charge for content." Are you already losing money due to AMP adoption?
- donohoe 9y agoI doubt that is relevant (and you make a very wide and sorta non-specific insinuation). You can use/integrate paywalls etc. with AMP.
- dang 9y agoIt's a serious violation of HN's rules to haul someone's personal details into a thread as ammunition against them. Please don't do this again. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- SimeVidas 9y ago> Wastes bandwidth downloading content in the background. Wastes battery rendering content in the background. That’s Google Search, not AMP. How much bandwidth does Search use? Is it big enough to be a problem for some users? > Downloads Google links you haven’t given permission you want to see. Google Search can load assets from its own domain, like any other website. The user can use browser extensions to block certain requests. > You can’t even opt out. You mean you can’t opt out of seeing AMP results on Google Search? Well, yes, for obvious reasons. AMP is Google’s product. It would make little sense for them to add such an option. > Breaks the web url extending it for Google’s own purposes. Breaks the understanding that the domain you are on is the authority for it’s own content. Yes, it does. > Copying URLs to send to friends or post online no longer works correctly. It works in iOS Safari and Firefox for Android (and probably other browsers as well), which use the canonical URL when the user shares the page. There is also a Share button in the header of the AMP page. > Traps publishers further inside Google’s web, not the open web. You can say that Google traps publishers, but not that AMP is not the open web. Google AMP Cache is a website on the (open) web.
- nailer 9y ago> That’s Google Search, not AMP. That's AMP. AMP prefetches content from AMP sites which must be hosted on google.com. The AMP team, when asked about hosting AMP content outside google.com, mention they can't prefetch from other domains with current tech as a blocker for this.
- SimeVidas 9y agoThat’s Google AMP Cache, to be specific, which is used by Google Search. I was pointing out that the (alleged) extra bandwidth and battery use happens then the user visits Google’s website. I’d limit the term AMP to the library and framework for creating AMP pages.
- tareqak 9y agoWhat term would you give for how Google Search treats AMP pages from regular HTML pages?
- tootie 9y agoAll of this is implicitly true for native apps as well. Google is in open war with Apple to keep users in the browser.
- wil421 9y agoI’d argue google is at war with Facebook and other app developers more so than Apple. Facebook mobile has become a “gateway” to the internet. Most links I click on my newsfeed are webpages opened in the Facebook browser.
- gaius 9y agoIt's meaning is: all your sites, sites, sites, sites, all your sites, are belong to us
- SimeVidas 9y ago> 1. AMP is a community project, not a Google project. It’s a community project and a Google project. > 2. AMP pages don’t receive preferential treatment in search results. They do due to the AMP carousel at the top, but that’s it. AMP pages don’t receive bonus points in the search ranking for being AMP. > 3. AMP pages are hosted on your own domain. They are, but they’re also hosted on Google AMP Cache.
- nwellnhof 9y ago> They do due to the AMP carousel at the top, but that’s it. They also get the AMP icon which users are starting to equate with faster loading times. Another form of preferential treatment.
- recursive 9y agoThat's not preferential. Users equate it because they've observed it. Speaking strictly as a consumer of the web, I have a strong preference for AMP for a few reasons. It's fast. The page doesn't jump around and lag. There are no popups. It's just a good experience. I know it's possible to have a good experience without AMP technically, but very few sites seem to be doing that.
- SimeVidas 9y agoTrue. I didn’t think of that.
- nailer 9y ago> They do due to the AMP carousel at the top, but that’s it. AMP pages don’t receive bonus points for being AMP. is just rewording this sentence from this article: > the Google Search team were at pains to repeat over and over that AMP pages wouldn’t get any preferential treatment in search results …but they appear in a carousel above the search results.
- SimeVidas 9y agoIt’s not because I’m saying they do, and Search team is saying they don’t ;)
- nailer 9y agoI dislike AMP too, despite being an author of an AMP library for node (https://www.npmjs.com/package/amps-in-the-trunk https://www.npmjs.com/package/amps-in-the-trunk), but: > AMP is, I think, best described as nominally open-source. That's not how open source works. Projects are either under an OSD license or not. See https://github.com/ampproject https://github.com/ampproject for the licenses involved. The article's premise still stands, but the author probably meant 'nominally open standard' or just 'nominally open', both of which are accurate.
- davethedevguy 9y agoGood article. My main objection to AMP is not that is it being portrayed as a community project (although, that does bother me). It is that Google are creating their own subset of already well established standards (HTML, CSS), and forcing developers to adopt them if they wish their content to appear at the top of search results. If this is truly a project to increase the speed and readability of the Web, as it was initially promoted to be, Google have better tools for achieving that outcome (demoting excessively slow sites in search results, for example). In it's current guise, AMP is little more than Google aiming to force all content on the web to be consistent with their own look-and-feel, and breaking the fundamental philosophy of the web in the process.
- SimeVidas 9y agoWhy do you think has Google created these restrictions on HTML and CSS code in AMP pages?
- davethedevguy 9y agoI do believe that it is an effort to increase the speed of pages, by preventing content creators from doing things that can harm the user's experience on slower connections - I just don't think it's the right way to go about it. It also has the side-effect that all AMP pages must look fairly similar and 'on brand' for Google - which I doubt is an accident.
- lllr_finger 9y agoWhat's the right way then? When I worked at a media conglomerate, AMP was the only thing that reigned in and enraged the biz-dev and ad-ops departments. I'm still proud that my AMP launch partner pages are out there and serving up content really fast. I hate that it took this to provide that experience, but I prefer it to the FB and AAPL walled garden syndication approach for business and tech reasons.
- falcolas 9y ago
- dmitriid 9y agoWorse still, if you mention any of these issues on AMPs GitHub page, they will be closed with “nothing to do with AMP, it’s how Google chose to implement it, ask Google”
- tboyd47 9y agoThat is hilarious!
- diggan 9y agoDo you have any concrete examples of this? Would like to see the actual issues and wording from the AMP team on it. Not that I don't believe you, just want to read it for myself.
- dmitriid 9y agoThe biggest discussion AFAIR is https://github.com/ampproject/amphtml/issues/6210 https://github.com/ampproject/amphtml/issues/6210 “This is a Google Search issue, not AMP issue”
- digitalbase 9y agoI've been pushing back hard on adding AMP as a feature on our product and I am glad I did. We host/publish millions of articles for our clients and I just don't feel comfortable enabling AMP and allowing the big boys to get away with this crap. All large CMS players and publishing platforms should read this post.
- tboyd47 9y agoI think a decent compromise (one I'd like to see more sites adopt) is only putting a subset of your page's content on the AMPed version, with a "Read the full article on XYZ.com" banner at the bottom. It gives you that preferred real estate while also acting as a funnel to your site.
- geofft 9y agoI've seen a bunch of sites do that, and honestly I appreciate that as an end user because I want to get to the actual site, but at that point, AMP's story that it makes the web faster is actively untrue: you have to wait for the AMP page to load, scroll, and then load the normal page.
- ocdtrekkie 9y agoDoesn't that make it win-win? It both gives the site the advantageous position AMP offers it, while undermining AMP's entire purpose and hence discouraging support of it.
- cobookman 9y agoEven in that case I find it useful. You get enough context to quickly drop out if the content didn't meet your needs. Try looking for recipes. I only click read more if the recipe met my needs. Else I swiped right to get the next matching recipe.
- vanadium 9y agoSo, lean splash pages? I mean, you can already see many publishers (Reddit, ebay, some newspapers like USA Today) doing it. Already gaming AMP. Technically speaking then, AMP isn't accomplishing a whole hell of a lot, and risks being relegated to "splash page technology", if that becomes a trend. I'm curious how long it'll take for spammers to start inundating AMP, personally.
- tboyd47 9y agoThe crazy thing about AMP to me is that we wouldn't have nearly as much front-end bloat on the web if it wasn't for the data-driven (read: click-driven) form of advertising championed by (who else?) Google. They put the burden on small time publishers for fixing a problem that they created. Some of the stuff I see Google and Facebook doing to the web developer community these days makes Microsoft in the mid-00s seem like a model citizen.
- cobookman 9y agoIf it wasn’t those two it’d be someone else. You might not even have the web as we kno it without the ad analytics. Unless you have a viable alternative monetization method?
- recursive 9y agoI kind of liked it better when it was hobbyists and enthusiast sites. The "web as we know it" isn't necessarily a great thing.
- fooker 9y agoHobbyists and enthusiasts do not scale to ~3 billion people.
- recursive 9y agoNeither do most other things done by hobbyists. I don't understand what you're saying. The only things that are good enough to do are those that scale to 3 billion people?
- fooker 9y agoI am saying, if you want a web by and for hobbyists and enthusiasts, billions of people has to be excluded. Where do you think new hobbyists come from?
- Touche 9y agoIt's hard to have a good-faith debate about AMP when Google says that AMP sites aren't given favor in search results, by defining the carousel as not being part of search results.
- SquareWheel 9y agoI think this one comes down to industry vs colloquial definitions. In the search industry, the organic search results are what you're referring to when talking about the ranking algorithm, and of a ranking factor being given an advantage. Having other verticals integrated like maps, news, or this carousal are seen as different elements altogether (eg. local search, shopping search). But of course, colloquially, "search" just means any result that comes up when you search on the page. So this has created some friction when Google says that Amp pages have no impact on search.
- Touche 9y agoI think Google is fully aware of what people mean when they say that AMP is given priority in search results. Insider terminology is an excuse to not confront the issue. This is why we can't have the discussion with Google; they are knowingly deflecting.
- rsoto 9y agoEven outside the carousel; three weeks ago we implemented AMP with our content marketing strategy and we have received 34% more visits. I don't think people our target is more inclined into clicking on AMP results as they're non-technical, I'm guessing we're higher in the results.
- marcus_holmes 9y agoIs it just me? I kinda stopped paying attention after they used "problematic". Where I am, this term isn't in common use in the sense that the author obviously uses it. The only places I see this used at the moment are, shall we say, opinion pieces with opinions that are not mainstream. I'm not really against its use like this, though I think there are better words in this case, like "inaccurate" or "misleading", or "manipulative", "lying cheating weasel-worded scumsucking", "blatantly f*cking untrue"... I dunno. It's probably just me...
- amiga-workbench 9y agoIts not just you, the SJW overuse of the term makes me cringe when I come across it.
- tambourine_man 9y agoSame link, submitted yesterday: https://news.ycombinator.com/item?id=15581276 https://news.ycombinator.com/item?id=15581276 I don't get HN dedup anymore.
- throwaway2048 9y agoarticles that get no real traction are not counted for dedup purposes. Its annoying when you submit them, but then this comment topic wouldnt have occured.
- tambourine_man 9y agoIMO there should be a window, say a year. That way evergreen topics can be rediscussed over and over. But the way it currently works fragments the comments over multiple links submitted on the same week. This one, for instance, is lost in the ether https://news.ycombinator.com/user?id=ocdtrekkie https://news.ycombinator.com/user?id=ocdtrekkie Why not aggregate on the same thread?
- seanwilson 9y agoIt's a shame there's so much controversy around AMP. It's not a simple task to set up a performant website. Ignoring the search result preference and caching, but AMP is an interesting attempt to tame website development so your pages load quickly. People keep commenting you can make a website fast without AMP, but this is difficult when you're working in big teams and with management that don't put priority on performance.
- jordanlev 9y agoIf Google just flat-out said they would penalize sites in rankings for poor performance, then management would very much prioritize it. Same thing happened with responsive design a year or two ago and now https this year -- my clients never cared about doing either of these when presented with the choice (since it would cost more money), but the second they received and email from Google about it affecting their search rankings (or showing the site as "insecure" in chrome, as per the recent push for https), they were asking us to do this for them.
- seanwilson 9y agoI'm curious about this as well. How easy would it be to game performance measurements? For example, when you can lazily load content it becomes much more difficult to measure. The advantage of the AMP restrictions for them is that they know for sure certain performance metrics will be met but this is much more difficult for arbitrary webpages.
- jordanlev 9y agoThat's a good point. I think google is able to measure this to some extent, but yeah I guess anything could be gamed.
- vanadium 9y agoRun a WebPageTest on an AMP link and tell me it fits within the 1 second promise AMP keeps making. Without prefetch, on a lot of the pages I've cross-checked manually, it doesn't. So there's already gaming from the other side of the aisle in a sense.
- cisanti 9y agoCopy of my comment from another thread: You can do your part as a developer and tell managers about the dangers of AMP. It is a stupid idea technically (we have HTML, you can build a slim sites, Google can rank them higher) and stupid business wise by giving away the control, branding, options. I have convinced one project manager to not implement AMP and will continue to try in the future. Please do your part by spreading word of the dangers of GOOG and FB.
- throw2016 9y agoLet all the hyper monetized, ad-funded, people stalking, profile building content head to amp, google and facebook ecosystems. The more egregious Google's creepy behavior becomes the more urgent the solution becomes. This is an opportunity to find a solution.
- gonational 9y agoI think Google should be allowed to do whatever they want, as long as they don’t lie to their visitors and pretend they are a search engine, which is what they’re currently doing. Perhaps this is the solution; require Google to stop calling itself a search engine.
- emodendroket 9y agoWhat else are people going to use, really?
- Sylos 9y agoAnd why do you think that? I could understand why you'd want to be thinking that, if you own lots of Google stocks, but either way this does not provide any resolution to anything. Whether you call it a search engine or a curated content platform, users aren't going to suddenly stop using it now.
- deleted 9y ago[deleted]
- elsewhen 9y agoof course google should be allowed to do whatever they want -- they are a private company in a (currently) unregulated industry. users, developers and publishers should also be allowed to do whatever they want. the author of the article is recommending that others realize what google is actually doing with AMP and to stay away from the technology (despite is positive sides).
- danso 9y agoHow is it not a search engine? Opinions about what constitute proper search results has always been at the core of Google’s algorithm from the very beginning.
- cobookman 9y agoI honestly love amp pages. They load in rural areas unlike other bloated pages. When you've got good service they load quick without annoying popups / ads. If people hate amp, maybe it’s time to adjust the web standards to enable amp experience with the html6 web. (Disclaimer, I do work at Google)
- dx034 9y agoSame for me, if I'm in the tube or in an area with weak coverage I only click on AMP links (and Facebook equivalent) whenever possible. That way I can search and load the result in the ~15-20 sec time window where I have wifi. (I don't work at Google or Facebook or wherever)
- pcwalton 9y ago> If people hate amp, maybe it’s time to adjust the web standards to enable amp experience with the html6 web. What does that mean exactly?
- strictnein 9y agoWeb 4.0
- lucb1e 9y agoIs that supposed to be enlightening / a thing, or is this another buzzword to mix in with HTML6 (which I've never heard of either)?
- strictnein 9y agoIt's supposed to be nonsense.
- tree_of_item 9y agoI think it means a future revision of the web could explicitly identify a subset like AMP, to encourage web developers to target it without Google being involved. One advantage of a setup like this would be the possibility to instruct your browser to reject any non-AMP pages (or make them click to play, or otherwise indicate them), if you were on rural internet and didn't even want to bother loading a slow page.
- johnhenry 9y agoGoogle promised a way to make your content more powerful, but it turned out to be just an easy way to control it themselves... It's like they took on the role of Sauron almost immediately after giving up their "don't be evil" slogan.
- dblooman 9y agoI have found some sites have made the "main" site better than AMP in terms of speed and download, but because its often the first result, sometimes you get an inferior experience. As someone who built and deployed the bbc news amp experience, i didn't really know how it was going to be used, but i would have raised serious concerns knowing what we know now.
- waytogo 9y ago> AMP pages don’t receive preferential treatment in search results. Think it’s true. At the beginning AMP pages got a huge rank bonus. Now, it’s much less. I feel Google sees AMP just for news pages. Guess the project got a lot resistance internally which is understandable: With the hundreds custom AMP components they are actually rebuilding the web.
- callalex 9y agoDid you read the article? The whole point is that amp pages are _above_ the search results, which is massive preferential treatment in its own way.
- waytogo 9y agoHaven’t news been always above the search results? And only AMP news pages are currently above the search results. Non-news AMP pages have to rank like non-AMP pages. I don’t like the entire AMP thing either but a bit more differentiation would be helpful here.
- lucb1e 9y ago> At the beginning AMP pages got a huge rank bonus. That they ever got such a thing is ridiculous to begin with. One of Google's principles is that they're neutral, besides clearly labeled paid-for ads which have always been the business model. I don't think they succeed 100% in setting aside unconscious biases that the programmers must have that build and tweak/configure the thing, but I believe that it is one of the basic ideas. If you say that was not the case, and is "much less" not the case now, then saying it's not biased is just weird.
- elsewhen 9y agoif they are "clearly labeled" now, what terms do you use to describe what he ad labels were in the past? http://www.benedelman.org/adlabeling/google-colors-oct2014.html http://www.benedelman.org/adlabeling/google-colors-oct2014.h...
- tcsf 9y agoFor a bit deeper understanding of AMP pages and how Google makes all of this work – check out this talk from Segment co-founder Calvin French-Owen https://www.heavybit.com/library/blog/get-ampd-an-introduction-to-accelerated-mobile-pages/ https://www.heavybit.com/library/blog/get-ampd-an-introducti...
- erikb 9y agolol. This doesn't even need a discussion. If you have a website hooking nearly all over websites without asking the users consent and without giving the user a recognizable way to opt out, then of course it is toxic. It is toxic by nature.
- generalpf 9y agoI just googled “house of cards cancelled” in Firefox on my iPhone and every result for a several screens worth of scrolling are AMP. I can’t find a single result that isn’t AMP.
- deleted 9y ago[deleted]
- FloNeu 9y agoHmm, while some of the critic i see here may be valid and justified, i like the enforcing of this strict rule set... i am senior frontend-dev and imho we wouldn't need AMP if in 99% of the cases devs, or better their customers would give a damn about doing their job right ( most of the time they just don't know better, because they are just beginners and never learned much about 'advanced' html/css - i haven't seen to much senior devs lowering themself to do html/css work and/or are knowleadgable in this areas ). Most of AMPs advantages regarding FOUC, Jumping-Content and Performance is to enforcing good HTML/CSS practices. Again citing guardian as example... So at least know i have a way to simple enforce a minimum best practice for mobile pages... Whenever i had to sign off a responsive/adaptive mobile page loading 'insane' amounts of unused styles and/or javascript i wanted to hit something with a hammer... I am for giving it some time and see how it develops..