News for hackers. Stuff that matters.
Re:Google AMP case study: leads dropped by 59% by setquk on Sunday December 16, 2018 @10:29AM (#18693451)
Definitely.

I can’t understand why the hell anyone would want to use it anyway. The experience is terrible.

Re:Google AMP case study: leads dropped by 59% by tyingq on Sunday December 16, 2018 @11:22AM (#18693695)
Publishers use it because otherwise their stories don't end up in the carousel widget for Google searches. I don't think many of them are actually buying into the AMP hype. They are just backed into a corner.
Re:Google AMP case study: leads dropped by 59% by frandroid on Sunday December 16, 2018 @12:08PM (#18693908)
I can confirm this. Source: working at my country's largest newspaper.
Re:Google AMP case study: leads dropped by 59% by untog on Sunday December 16, 2018 @11:03AM (#18693602)
It isn't though, really. Page load really is nearly instantaneous. I'm no fan of AMP, but I see the reasons why users like it.
Re:Google AMP case study: leads dropped by 59% by dep_b on Sunday December 16, 2018 @12:19PM (#18693961)
You're right about that, but AMP'ed pages not coming from Google's cache are already really fast. Actually they're only preloading those pages while you're on the results page, which is something they could do as a reward for all pages that have a reduced page weight.
Re:Google AMP case study: leads dropped by 59% by jefftk on Sunday December 16, 2018 @08:35PM (#18696348)
> something they could do as a reward for all pages that have a reduced page weight

This would leak information to sites that came up in your search results but you didn't visit. Webpackages should make it be possible to safely prerender sites without AMP though: https://wicg.github.io/webpackage/draft-yasskin-webpackage-u...

(Disclosure: I work at Google, on making ads AMP so they don't get to run arbitrary JS anymore)

Re:Google AMP case study: leads dropped by 59% by lern_too_spel on Sunday December 16, 2018 @03:46PM (#18695131)
It is not safe to preload arbitrary web pages. The user will be deanonymized to a site they never visited. It is safe to preload AMP pages by design.
Re:Google AMP case study: leads dropped by 59% by manigandham on Sunday December 16, 2018 @04:52PM (#18695498)
And yet now you never leave Google's servers when browsing. They know your entire path from search to site and back again.
Re:Google AMP case study: leads dropped by 59% by lern_too_spel on Sunday December 16, 2018 @05:53PM (#18695755)
Google would have known you clicked on the link anyway. You would prefer the publishers and ad networks track users on pages they never even visit?
Re:Google AMP case study: leads dropped by 59% by manigandham on Sunday December 16, 2018 @06:16PM (#18695860)
AMP pages mean Google has 1st party access to your browser no matter what you browse, which is far more than normal.

I didn't state any preferences, and how would sites track you on pages you don't visit?

Re:Google AMP case study: leads dropped by 59% by lern_too_spel on Sunday December 16, 2018 @06:45PM (#18695971)
> how would sites track you on pages you don't visit?

As I stated in GGGP, the benefit of AMP is that it allows a user to safely preload pages.

Re:Google AMP case study: leads dropped by 59% by manigandham on Sunday December 16, 2018 @07:22PM (#18696102)
Because you never leave Google's domain, thereby allowing it track you far more. Preloading is a minor detail considering how much privacy is removed.
Re:Google AMP case study: leads dropped by 59% by lern_too_spel on Sunday December 16, 2018 @10:48PM (#18696799)
Google already scraped the page to show the snippet, so they know what you're looking at. Whatever the privacy loss might be, people are happy to make that tradeoff with Facebook Instant Articles and Apple News. Similarly, they're happy to make that tradeoff on the web, which explains why AMP is used by so many search engines and link aggregators, not just Google.
Re:Google AMP case study: leads dropped by 59% by manigandham on Monday December 17, 2018 @12:25AM (#18697053)
People have no choice in the matter. Facebook and Google trade higher visibility for publishers that participate, in exchange for the same data tracking capabilities and limitations in 3rd-party ad networks from making money.

Apple News is entirely different and more comparable to using any other news app (like Flipboard) or an RSS reader rather than a website.

Re:Google AMP case study: leads dropped by 59% by Tsubasachan on Monday December 17, 2018 @12:47PM (#18700571)
People is so nebulous. I am people and I don't make that tradeoff.
Re:Google AMP case study: leads dropped by 59% by lern_too_spel on Monday December 17, 2018 @01:50PM (#18701060)
Tell me what privacy you think you're losing. Then avoid clicking on AMP results.
Re:Google AMP case study: leads dropped by 59% by Filligree on Sunday December 16, 2018 @10:34AM (#18693466)
It's wonderful when browsing. Pages load in less than half a minute, unlike nearly the entire rest of the internet.

Hacker News doesn't need it, but they're nearly unique in having written a good website.

Re:Google AMP case study: leads dropped by 59% by zzleeper on Sunday December 16, 2018 @10:51AM (#18693538)
I abhor it on mobile. I can't navigate away from it easily, it's hard to copy paste annurl to share with others, etc. I wish Chrome had the option to disable it, but of course they don't.
Re:Google AMP case study: leads dropped by 59% by madeofpalk on Sunday December 16, 2018 @11:57AM (#18693852)
> I can't navigate away from it easily

eh? You can't hit 'back'?

Re:Google AMP case study: leads dropped by 59% by tyingq on Sunday December 16, 2018 @12:08PM (#18693909)
It does hijack the back button for carousel loaded pages in a way that's odd.

Search for some newsworthy word, say "trump". Click a carousel story. Swipe right (another hijack), and the page loads a story from a competitor to the publisher of the original loaded AMP page.

Now, hit the back button. One assumes it would go to the original loaded story, right? Nope, it goes back to Google. Surely that wasn't intentional, right?

Re:Google AMP case study: leads dropped by 59% by grogenaut on Sunday December 16, 2018 @12:37PM (#18694061)
Going back to google makes sense as my intention is to read the news of the day, not cross reference. Stack behavior would drive me crazy here.
Re:Google AMP case study: leads dropped by 59% by tyingq on Sunday December 16, 2018 @12:42PM (#18694089)
I suppose, but that sort of reinforces the real purpose of AMP. No publisher in their right mind would give up the top part of their page and enable left/right swipe to navigate to competitors, give up the back button control, etc. It's basically a protection racket. Pay up (in control terms), or get pushed down the search results page.

Feels a lot like the old "digg bar" (https://moz.com/ugc/die-diggbar-die-die-should-you-kill-the-...)

Re:Google AMP case study: leads dropped by 59% by criddell on Sunday December 16, 2018 @12:56PM (#18694164)
> No publisher in their right mind would give up the top part of their page and enable left/right swipe to navigate to competitors

Publishers usually do not make good decisions. That behavior is for users and (IMHO) it's great.

Re:Google AMP case study: leads dropped by 59% by notahacker on Sunday December 16, 2018 @03:59PM (#18695202)
That behaviour is for Google, not for users.
Re:Google AMP case study: leads dropped by 59% by grogenaut on Sunday December 16, 2018 @12:46PM (#18694115)
For me though, they already have. I don't browse via their nav. I spearfish articles and I'm out. I find most news sites navigation and search garbage and have to resort to site: searches
Re:Google AMP case study: leads dropped by 59% by AnssiH on Sunday December 16, 2018 @12:11PM (#18693926)
They might also mean "go to the non-AMP version", which is my main issue with AMP.

I'd like to get the non-AMP page to e.g. see user comments (if any) which are often omitted from the AMP version, or for posting the non-AMP URL to friends or social media.

Sometimes there is an easy way to go to non-AMP page, depending on how you got there, but most of the time for me there is not. For example, this article just appeared on my Google feed on my phone, with no way to open the non-AMP version: https://www.vice.com/amp/en_uk/article/wda7jm/where-does-he-...

My preferred option would be to have AMP permanently disabled on my phone.

Re:Google AMP case study: leads dropped by 59% by yorwba on Sunday December 16, 2018 @01:16PM (#18694263)
How to disable AMP permanently on your phone:

- stop using Google feed. I can't recommend a one-stop replacement, since I use RSS to follow sites I trust to produce high-quality content and HN to discover new stuff.

- stop using other Google products that link to AMP pages. DuckDuckGo is good enough these days.

- use Firefox. That in itself might prevent Google search from showing AMP results, if you can't bear to use DDG. At least someone said so two years ago in this thread on Google's product forums https://productforums.google.com/forum/?_escaped_fragment_=t...

- install https://addons.mozilla.org/en-US/firefox/addon/amp2html/ in Firefox. It still needs to load the AMP page to grab the canonical URL, but then it redirects to the non-AMP version. You can also add an adblocker like uBlock Origin while you're at it. The ability to install addons is what makes Firefox the best mobile browser in my opinion.

Re:Google AMP case study: leads dropped by 59% by emayljames on Sunday December 16, 2018 @03:32PM (#18695052)
I just thought of this great Ffox addon that I use too. AMP pages are not real web pages. They are awful.
Re:Google AMP case study: leads dropped by 59% by freedomben on Sunday December 16, 2018 @01:11PM (#18694232)
I couldn't agree more. The problem with AMP is that it isn't possible to disable it. Other than that, I appreciate what Google is trying to do, even if their implementation has a few flaws.
Re:Google AMP case study: leads dropped by 59% by ryanwaggoner on Sunday December 16, 2018 @12:09PM (#18693913)
It constantly breaks the back button and screws up my history.
Re:Google AMP case study: leads dropped by 59% by freedomben on Sunday December 16, 2018 @01:07PM (#18694213)
I'm agnostic on AMP, but I very much agree with you that they should add the option to disable. Android is all about choice and user empowerment! That's why I love it
Re:Google AMP case study: leads dropped by 59% by cronix on Sunday December 16, 2018 @01:38PM (#18694398)
> Android is all about choice and user empowerment!

I disagree, strongly. I believe Android is really more about keeping you in the Google ecosystem. So is AMP, so is Chrome. I'm an Android user, but let's not pretend they are really about "choice and user empowerment." That's just the sales pitch. Every single thing Google creates is to collect information on/from us, because that's their revenue model. Selling our data. If you disagree, compare the ad revenue from all of them. Who's is miles ahead? Why? How? You're giving them your data. A LOT of it.

Re:Google AMP case study: leads dropped by 59% by freedomben on Sunday December 16, 2018 @02:10PM (#18694572)
Agreed regarding ulterior motives (keeping you in their ecosystem). In the excellent book "In The Plex" by Steven Levy, he talks about Google's motivation of essentially building a browser, mobile OS, etc just to ensure that some other party (like Apple) doesn't cut them out and reduce their search/ad domination. I believe protecting search/ads is at the base of their motives (as is, undeniably, vacuuming up tons of data and mining it for ML purposes).

But that said, why do so much for open source? Why not keep big things proprietary? Why sell Chromebooks that can be unlocked, put in dev mode, and flashed with FOSS BIOS implementations? Why allow unlocking the bootloader on Nexus and Pixel phones? There's lots of things they do that clearly aren't for the bottom line or just to trap you in their ecosystem (they do offer versions of basically everything for iOS as well, which makes it easier to switch to iPhone even if you are deep in the Google ecosystem).

Some of my argument is emotionally based tho, I will admit. After being trapped in Apple's very proprietary, anti-competitive, you-dont-own-it-we-do system, I find the ability to reclaim some freedom (tho not all, they could do better) very nice.

So I think our only real disagreement is likely regarding motives.

Re:Google AMP case study: leads dropped by 59% by pdkl95 on Sunday December 16, 2018 @03:33PM (#18695059)
> why do so much for open source?

For the low price of working under an open source[1] license, they bought over a decade of support from a large portion of tech industry professionals. Google (along with the other FAANG businesses) was able to simply ask people to supporting their increasingly monopolistic position.

When some of us attempted to warn about the long term consequences of giving Google/etc even more power, we were ignored or accused of being "crazy conspiracy theorists"; with a lot of open projects to use as counterexamples, and not many current, specific examples of Google actually abusing their power, a lot of people simply couldn't believe that Google might be doing anything bad.

Open sourcing anything that overlapped with a competitor's proprietary software was a highly successful strategy to undermine the market and hurt their competitor's revenue. The minimax best move isn't always the move that maximizes your benefit; sometimes it's the move that minimizes your opponent..

[1] Note that while they use FSF/RMS-style free Software, Google generally doesn't license their open source software under the GPL. Their openness has a carefully considered limit.

Re:Google AMP case study: leads dropped by 59% by yorwba on Sunday December 16, 2018 @03:44PM (#18695119)
> But that said, why do so much for open source?

It gets them more users for their services if people make use of their open-source libraries that happen to be optimized for Google, e.g. by integrating better with Google's cloud offerings.

> Why not keep big things proprietary?

They do keep big things proprietary. If it directly makes money for Google, you're not going to see it's source code, unless you work for Google.

> Why sell Chromebooks that can be unlocked, put in dev mode, and flashed with FOSS BIOS implementations? Why allow unlocking the bootloader on Nexus and Pixel phones?

Most people don't change their OS ever, so it doesn't really matter whether bootloaders are locked or not. Even if more people did it, many of them would still install Google apps, so it would continue not to matter.

> There's lots of things they do that clearly aren't for the bottom line or just to trap you in their ecosystem (they do offer versions of basically everything for iOS as well, which makes it easier to switch to iPhone even if you are deep in the Google ecosystem).

Google is not in the phone business. Their phones are just funnels for their advertising business. If they were in the phone business, offering those indispensable apps to iOS users would decrease their ecosystem lock-in. But because they're not in the phone business, offering apps for iOS increases their ecosystem lock-in, because even going to Apple, you still stay with Google.

Nexus/Pixel phones exist only as funnels into the Android ecosystem. Android exists only as a funnel into default-installed Chrome, Gmail and Google Search. Chrome itself is a funnel for Google Search, while Gmail's purpose is to make people sign into an account for easier tracking. Then there's the general ecosystem pull of being the one-stop shop for a bunch of online services. But in the end it all boils down to ads.

Because the majority of their products are only funnels, they'll happily cooperate with competitors for some of those products, if that helps them keep people in the wider Google ecosystem. So you get Chrome for iOS, Google Search for Firefox and so on.

When a company seems to be hurting their own bottom line by giving away stuff for free, it's usually because the free stuff isn't that important to them and their real bottom line is elsewhere.

Re:Google AMP case study: leads dropped by 59% by cronix on Sunday December 16, 2018 @04:15PM (#18695283)
> Most people don't change their OS ever

Or the default search engine, which is Google. So most Apple users are still using Google, and Google pays a ton for Apple users data. $12B is not a trivial chunk of change. That's more than most companies make, and that's only from search! http://fortune.com/2018/09/29/google-apple-safari-search-eng...

Re:Google AMP case study: leads dropped by 59% by tylerl on Sunday December 16, 2018 @01:09PM (#18694222)
But not QUITE as terrible as the UX of news sites without AMP. Which I suppose was the point.
Re:Google AMP case study: leads dropped by 59% by pacifika on Sunday December 16, 2018 @10:54AM (#18693548)
Purely to keep the SEO positioning everyone enjoyed before it came into being.
Re:Google AMP case study: leads dropped by 59% by PaulHoule on Sunday December 16, 2018 @11:39AM (#18693769)
"Recycling of lost faculties".

They take it away from you and then you will bend over and kiss Matt's Butt.

Re:Google AMP case study: leads dropped by 59% by JustSomeNobody on Sunday December 16, 2018 @12:19PM (#18693963)
It only takes a couple business to start using it and always winding up at the top of search before everyone else feels they have to like it or not.
[dead]
Re:Google AMP case study: leads dropped by 59% by cronix on Sunday December 16, 2018 @01:45PM (#18694429)
Reader view in firefox makes it very fast. Like how the web used to be. It just displays the images/text of the actual content and strips everything else out. I immediately hit that button on most sites now, and they load in under 1s (usually way under). It even has a dark mode! No videos playing, no ads changing in sidebars distracting your eyes, no popups making your click through. Just the content you wanted to see. I just wish you could make it the default mode.
Re:Google AMP case study: leads dropped by 59% by baobrain on Sunday December 16, 2018 @03:13PM (#18694940)
Often times the websites are completely broken under reader mode: images are in the wrong locations, image captions are treated as article text, article text doesn't appear on websites that have awful scrolling behaviour.

I completely understand why people have problems with AMP. However, AMP is a drop-in replacement (for the user) and Firefox's reader mode is simply not equivalent, as much as I use it.