News for hackers. Stuff that matters.
Re:Google AMP lowered our page speed, and there's no choice ... by joegahona on Wednesday April 10, 2019 @08:48PM (#19630110)
I'd love for Google to explain the justification for putting _only_ AMP content in the "Top Stories" carousel. Google needs to either rename the carousel to be "Top AMP stories" or allow non-AMP stories to appear in the carousel. Isn't the whole purpose of search to prioritize the most relevant content, regardless of the type of HTML used to create it?
Re:Google AMP lowered our page speed, and there's no choice ... by justinph on Wednesday April 10, 2019 @09:36PM (#19630380)
I've asked the AMP team exactly this and they punted and demurred on the subject and said they have some vague plans to some day make it also contain sites that are as fast as AMP.

The AMP team will tell you that they are concerned with making the web faster, and it's the _search_ team that controls the carousel. Which is all well and good, but I can tell you that the _only_ reason any publisher is doing AMP is because they want the placement in the carousel and better search results.

As far as I can tell, google has no intention of ever allowing non-amp content they can't re-serve from their cache and add whatever analytics and tracking they want to from being ranked highly. AMP is a tactic to let them track the most lucrative mobile web users and take control away from publishers of original content.

Re:Google AMP lowered our page speed, and there's no choice ... by ehnto on Wednesday April 10, 2019 @10:30PM (#19630630)
There is nothing about an AMP page that makes it inherently faster until it lands in and is served by a Google regional cache server. Otherwise my site is going to be just as fast. I can make just as fast web pages and serve them from a server sitting in the same state as my customers. There will be no need for Google level scale for my site as it is regional. Yet I still get put below AMP sites.

From many different angles, AMP getting preferential treatment is heavy handed and clumsy, manipulative and forcing technology standards on the web that no one agreed on.

Re:Google AMP lowered our page speed, and there's no choice ... by underwater on Wednesday April 10, 2019 @11:26PM (#19630915)
AMP limits what the page can do, and allows Google to safely serve content through a cache. So Google can preload and prerender the page in an iframe. As a result clicks on the carousel are literally instant. That can't be done safely with a regular HTML page.
Re:Google AMP lowered our page speed, and there's no choice ... by ehnto on Thursday April 11, 2019 @03:18AM (#19631866)
I can serve content in miliseconds after the network request has been made. Near enough to appear instant to my users. I have caches too.

You can't help the network request if it has to be made when the user clicks but there is nothing stopping browsers from preloading my site and nothing stopping google from noting that my site could be preloaded when it crawls it. Limiting ranking influence to sites with the AMP structure is an option Google has decided to make and not an inherent restriction in the technologies at play.

The technology behind AMP is very cool mind you, I just find it being an exclusive ranking factor to be an unecessary pressure to use their technology when many other technologies could work just as well. Google is a major force in the way people make websites and they are being very heavy handed in this instance.

Re:Google AMP lowered our page speed, and there's no choice ... by joshuamorton on Thursday April 11, 2019 @03:31AM (#19631914)
> nothing stopping google from noting that my site could be preloaded

There's a whole host of security problems with trying to see if an arbitrary site can be preloaded. Logging, tracking, etc, not to mention more nefarious tricks like mining Bitcoin in the background.

Maybe Google could try to detect those things, but then you just end up in a cat and mouse game. A "safe" subset of html and js that can't do those bad things is much, much easier to analyze. One such subset is AMP.

Re:Google AMP lowered our page speed, and there's no choice ... by bryanrasmussen on Thursday April 11, 2019 @04:38AM (#19632145)
A safe subset of html that they can analyze could be summarized in a document and ranking things higher that conform to that subset. That is not what AMP is.
Re:Google AMP lowered our page speed, and there's no choice ... by jefftk on Thursday April 11, 2019 @07:46AM (#19633287)
That is exactly what AMP is attempting to be. It's a subset of HTML and CSS which guarantees that the site can be preloaded in a privacy-preserving way. There are a lot of things sites want to do that can't be done in pure HTML and CSS and allowing full use of JS would be incompatible with this goal, so that gap is filled with open source libraries.

(Disclosure: I work at Google on Ads, and I work with the AMP folks a bunch. Speaking for myself, not the company.)

Re:Google AMP lowered our page speed, and there's no choice ... by joshuamorton on Thursday April 11, 2019 @12:19PM (#19636182)
I'm curious what you think AMP is then, because what you describe is, quite literally the AMP projet. (Google, as well as Cloudflare and Bing also add a cache on top of things to make the preloading faster, but that's not technically a part of the AMP standard).

I'll grant you that the branding/communication here is atrocious, but as I'm reading this, what I'm seeing is "They should have implemented <description of AMP>, instead they implemented AMP, which is much worse."

Re:Google AMP lowered our page speed, and there's no choice ... by plorkyeran on Thursday April 11, 2019 @01:54PM (#19637302)
TIL <amp-img> is a standard HTML tag that works without loading the AMP JS.

AMP supports a subset of standard HTML, plus a whole bunch of AMP-specific extensions. That's a significantly different thing from being just a safe subset of HTML.

Re:Google AMP lowered our page speed, and there's no choice ... by joshuamorton on Thursday April 11, 2019 @02:37PM (#19637746)
https://developer.mozilla.org/en-US/docs/Web/Web_Components/...

Webcomponent custom elements are part of the HTML5 standard.

`<literally-any-element-name-i-want-here>` is a valid subset of html. You added the "standard" modifier, which like, I mean, WebComponents are part of the standard, so using them is still a subset of standard HTML.

If you mean "they should have limited themselves to using older HTML APIs and doing custom polyfills based on css-classes instead of element names", which is probably closer to what you actually mean, I'd ask why.

The behavior would, in general, still be the same. You'd be required to include some metadata information, you'd be restricted to some amp.js provided to you, and you'd need to use class='amp-html' instead of <amp-html>. And that would be the entire difference.

Re:Google AMP lowered our page speed, and there's no choice ... by bryanrasmussen on Thursday April 11, 2019 @04:00PM (#19638540)
So wait, the AMP project is just a document saying limit yourself to these things and we will rank you higher in search results because these things will make your site perform better and we want better performing sites?!?

Wow, color me disabused of the notion that AMP added stuff on top of that simple requirement to allow capture of publishers by Google, I had assumed bad intent and invented fanciful scenarios of what I would do if I were an evil corporation trying to control the web like requiring people to load my script on their pages and only using my analytics library so I would have all that data for me, or maybe just create a 'standard' set of components that I control and have people use those so they have tied up money in implementing my tech and I have lock in and in order to keep their ranking in my search app they sink more and more money into doing things the way I want, increasing my capture of them.

All sorts of evil stuff I might do, but gee, it turns out all Google did was publish a document saying use this stuff that is already standardized, and leave out these parts of the standards because they can be problematic and make things perform badly, and we will rank you higher in search results. Nothing else, just rank you higher.

Now I'm really sorry I thought Google was as evil as I am likely to be when working in a group of people trying to control a market. Google is as pure as the driven - gee, I don't know what, Snow? No, Climate Change means that metaphor is soon no more, what else can be driven, hmm, oh I know, a sociopath! Google is as pure as the driven sociopath, that sounds good.

Re:Google AMP lowered our page speed, and there's no choice ... by joshuamorton on Thursday April 11, 2019 @04:14PM (#19638680)
> So wait, the AMP project is just a document saying limit yourself to these things and we will rank you higher in search results because these things will make your site perform better and we want better performing sites?!?

Yes. Or at least, in practice its not really distinguishable from this other than technical nits that aren't practically relevant to the overall design or what anyone complains about.

>requiring people to load my script on their pages and only using my analytics library so I would have all that data for me, or maybe just create a 'standard' set of components that I control and have people use those so they have tied up money in implementing my tech and I have lock in and in order to keep their ranking in my search app they sink more and more money into doing things the way I want, increasing my capture of them.

These are the things you have to limit yourself to. You have to limit yourself to predetermined subsets of Javascript, because if not there's no way to ensure the safety/speed/etc. of the site.

You're shifting goalposts here. Now you want the set of things you're limited to using to be broader than is possible for valid technical reasons. You're also conflating AMP and Google, which like valid, because its confusing, but again, AMP doesn't require Google anything. So all of your complaints about forcing you to use Google's analytics library or include Google's JS aren't true. Yes, for AMP (JS) to work you need to include a Cache's JS, and Google is the biggest cache, but they aren't the only one.

As for the rest of your post:

> Don't be snarky. Comments should get more civil and substantive, not less, as a topic gets more divisive.

Could you at least try to be polite.

Re:Google AMP lowered our page speed, and there's no choice ... by feanaro on Sunday April 14, 2019 @06:49AM (#19658590)
Suppose that this is true and that there is no way to achieve this without AMP. Are we going to route the whole web through Google's server so that pages are rendered faster? This is getting silly.
Re:Google AMP lowered our page speed, and there's no choice ... by warent on Wednesday April 10, 2019 @11:46PM (#19630993)
I can't help but wonder what problem they're solving for. Is there a huge market of people clamoring to make webpages load faster than they already do?
Re:Google AMP lowered our page speed, and there's no choice ... by krageon on Thursday April 11, 2019 @02:23AM (#19631654)
You should try loading "the modern web" over a not great but passable phone connection (ie 3G maximum) on a non-flagship phone. Nearly every normal website you will have an exceedingly bad time on. That's what AMP claims to solve. Far be it from me to claim they succeeded or that they are doing it in the right way, but I think pretending the problem doesn't exist at all is disingenuous.
Re:Google AMP lowered our page speed, and there's no choice ... by emerongi on Thursday April 11, 2019 @03:40AM (#19631939)
AMP is a terrible user experience though. Google Search on mobile is - pardon my language - fucked now. I hate it. I get trapped in the cache, getting to the actual source is pain, there's some stupid bar on top, websites are showing their own bars to signify that the user is not actually on the website. And I'm a techie, I know how this works! I imagine regular users must be utterly confused.
Re:Google AMP lowered our page speed, and there's no choice ... by piva00 on Thursday April 11, 2019 @04:33AM (#19632115)
Thanks for voicing this out. I'm on the same boat, AMP is a terrible user experience. It takes me multiple clumsy steps to get to the content page I thought I was getting to when I clicked a link.

Apart from that a lot of websites started showing an overlay on top of the AMP pages, clicking on AMP pages don't work as expected a lot of times, it has a noticeable delay between actions (scrolling/tapping).

I disliked AMP when I first started seeing it but the way it has evolved has made the experience way worse than it started with... Probably because Google also caved in and tried to cater to customisations requests from big publishers.

Re:Google AMP lowered our page speed, and there's no choice ... by blunte on Thursday April 11, 2019 @04:42AM (#19632153)
I have 4G and a top end phone, and mobile web is getting worse by the day.

The first solution is not AMP. The first solution is to go back to when a web page was a "page", not a program made up of cobbled together bits of JavaScript.

Cookie preference popups, join the newsletter popups, animated or dynamic ads, and everything else stupid websites do that causes the browser's rendering engine to grind away non-stop...

The current user experience is worse than I think it ever was.

But as other posters have comments, AMP is probably intended to be a control and data tracking system first, with user experience being second or lower priority.

Re:Google AMP lowered our page speed, and there's no choice ... by JetSpiegel on Thursday April 11, 2019 @09:30PM (#19641107)
This is easily solved by installing Firefox for Android and uBlock Origin. I don't even understand how people tolerate the "modern" web otherwise.
Re:Google AMP lowered our page speed, and there's no choice ... by StreamBright on Thursday April 11, 2019 @03:01AM (#19631808)
Why not fixing “the moder web” then?
Re:Google AMP lowered our page speed, and there's no choice ... by michaelt on Thursday April 11, 2019 @05:17AM (#19632340)
Google can't block ads and tracking scripts in Chrome without either blocking their own, or facing (valid) claims of anti-competitive behaviour. Neither of which would get the person who did it promoted.

And no attempt to fix the slowness of the modern web will succeed without blocking ads and tracking scripts.

This is the downside of the dominant browser being made by and ads-and-tracking company.

Re:Google AMP lowered our page speed, and there's no choice ... by r3bl on Thursday April 11, 2019 @03:08AM (#19631825)
Because convincing all the website owners to do anything (even if it clearly benefits everyone) is an impossible task.

See HTTPS adoption.

Re:Google AMP lowered our page speed, and there's no choice ... by StreamBright on Thursday April 11, 2019 @03:41AM (#19631943)
HTTPS adoption:

https://storage.googleapis.com/cdn.thenewstack.io/media/2018...

Great example. You just proved my point that it is possible to have positive change in large communities.

Re:Google AMP lowered our page speed, and there's no choice ... by r3bl on Thursday April 11, 2019 @03:55AM (#19631996)
I'm not sure that graph shows what you think it shows.

That graph shows that there's an obnoxiously large number of websites that don't support something that there's zero reason not to support.

It costs $0 and takes maybe half an hour to implement, browsers are screaming "not secure" to each visitor, and one in five websites still don't support it. "Make websites faster", on top of being vague, is way more difficult to implement.

Re:Google AMP lowered our page speed, and there's no choice ... by piva00 on Thursday April 11, 2019 @04:34AM (#19632119)
1 in 5 NOT supporting it is much better than the opposite when I started working in the web where 90+% of websites didn't support HTTPS.
Re:Google AMP lowered our page speed, and there's no choice ... by StreamBright on Thursday April 11, 2019 @05:34AM (#19632422)
Well, I like the percentages and the direction that the graph is heading.
Re:Google AMP lowered our page speed, and there's no choice ... by manigandham on Thursday April 11, 2019 @10:21AM (#19634774)
You don't have to convince anyone, it's about incentives. The article and many others have shown exactly how to do this: make the metric a big part of search rankings.

If fast site performance ensures you get listed first, every site would get faster overnight.

Re:Google AMP lowered our page speed, and there's no choice ... by radus on Thursday April 11, 2019 @03:20AM (#19631872)
Isn't https over the hump in most of the world?
Re:Google AMP lowered our page speed, and there's no choice ... by yathern on Wednesday April 10, 2019 @11:53PM (#19631027)
Yes. In many areas where phones are the main tool used to access the internet, and coverage is primarily still 3G. Not defending AMP - but making pages load faster is still something people want and need.
Re:Google AMP lowered our page speed, and there's no choice ... by C1sc0cat on Thursday April 11, 2019 @06:28AM (#19632802)
For a lot of niches usage is > 50% mobile already.
Re:Google AMP lowered our page speed, and there's no choice ... by taytus on Thursday April 11, 2019 @12:16AM (#19631116)
There are billions of people with capped data plans and where 200kb/s is the standard.
Re:Google AMP lowered our page speed, and there's no choice ... by oarsinsync on Thursday April 11, 2019 @01:32AM (#19631421)
I don’t appreciate Google preloading pages that I didn’t ask for, resulting in my limited data allowance being wasted.
Re:Google AMP lowered our page speed, and there's no choice ... by dmitriid on Thursday April 11, 2019 @12:36AM (#19631185)
There are no AMP pages that weigh less than 1MB.

However, since Google aggressively preloads most of that data while you search, it gives you the illusion of AMP pages being lightweight.

Non-AMP pages? Oh, Google will happily penalize them even if they perform better.

Re:Google AMP lowered our page speed, and there's no choice ... by danso on Thursday April 11, 2019 @12:48AM (#19631234)
I did a mobile Google search for "Trump" to bring up the top news section on Google, and was able to find sites (generally non TV-news sites which aren't doing video with every story) that weighed less than 1MB:

USA Today (582KB, first item in the top news section) https://www.google.com/amp/s/amp.usatoday.com/amp/3431466002

Vox (486KB) https://www.google.com/amp/s/www.vox.com/platform/amp/policy...

The New Yorker (565KB) https://www.google.com/amp/s/www.newyorker.com/news/current/...

Re:Google AMP lowered our page speed, and there's no choice ... by geezerjay on Thursday April 11, 2019 @01:35AM (#19631436)
Unless those articles are packed with raster infographics that's pretty bloated just to send a couple of pages worth of text.

I meam, why exactly are 500kb of cruft is being served to present 5kb worth of data?

Re:Google AMP lowered our page speed, and there's no choice ... by rymate1234 on Thursday April 11, 2019 @02:46AM (#19631753)
The EU experience of USA today weighs on at 248KB and that's without AMP

So even if the AMP Pages are small, they're still much larger than the page ought to be

Re:Google AMP lowered our page speed, and there's no choice ... by v7p1Qbt1im on Thursday April 11, 2019 @03:38AM (#19631934)
Sure. But USA Today EU is not really a fair example. You can‘t really expect publishers to serve absolutely no ads and tracking at all. Unless you want them to die. There are initiatives like Apple News+ and Subscribe with Google but they are not mainstream yet. And individual subscriber options for news portals are way to cumbersome (and perceived as too expensive) for users.
Re:Google AMP lowered our page speed, and there's no choice ... by rymate1234 on Thursday April 11, 2019 @08:16AM (#19633586)
I agree, but the solution is for ad companies to improve so you don't need tons of JavaScript to display an advert. Why can't they be done server side, rather than handled by client side JavaScript? A lot of web apps now employ SSR, so having the adverts use SSR should considerably speed them up
Re:Google AMP lowered our page speed, and there's no choice ... by dmitriid on Thursday April 11, 2019 @05:44AM (#19632481)
I ran all links below with Google Chrome Tools enabled, no cache. Switched to mobile view to make sure that AMP pages are loaded. Cache disabled to see the actual weight of the page.

---

USA Today AMP page: 45 requests. 755 KB transferred. 1.6 MB resource

USA Today EU Experience: 10 requests. 209 KB transferred. 251 KB resources.

AMP version is significantly worse for essentially the same content (AMP version and EU version are nearly identical)

---

VOX AMP: 37 requests. 575 KB transferred. 1.4 MB resources.

VOX AMP not served from Google [1]: 22 requests. 403 KB transferred. 935 KB resources.

VOX non-AMP [2]: 19 requests. 627 KB transferred. 1.3 MB resources

So, AMP is worse when served from Google. And on par with non-AMP version

---

The New Yorker AMP: 129 requests (and they keep coming). 796 KB transferred. 1.9 MB resources

The New Yorker AMP not served from Google [3]: 70 requests (and they keep coming). 745 KB transferred. 1.5 MB resources

The New Yorker non-AMP page[4]: 245 requests (and they keep coming). 8.2 MB transferred. 13 MB resources.

So. The only example where the AMP page is significantly better than the non-AMP pages.

---

But the page weight is already accounted for in Google Search algorithms, and The New Yorker page should have been deprioritised from search. It's not, it's in the carousel, it will redirect to the 13MB version on desktop. Meanwhile, as Vox, and USA Today and many many many others show, the regular properly made website will not differ significantly from AMP versions.

[1] https://www.vox.com/platform/amp/policy-and-politics/2019/4/...

[2] https://www.vox.com/policy-and-politics/2019/4/10/18305175/t...

[3] https://www.newyorker.com/news/current/william-barr-goes-ful...

[4] https://www.newyorker.com/news/current/william-barr-goes-ful...

Re:Google AMP lowered our page speed, and there's no choice ... by tzakrajs on Thursday April 11, 2019 @12:24AM (#19631153)
Yeah, I am sure there is some sort of KPI tracking engagement which helped to inform this behavior.
Re:Google AMP lowered our page speed, and there's no choice ... by Godel_unicode on Thursday April 11, 2019 @12:12AM (#19631099)
Yes.
Re:Google AMP lowered our page speed, and there's no choice ... by C1sc0cat on Thursday April 11, 2019 @06:25AM (#19632782)
Yes have you seen as lot of websites these days
Re:Google AMP lowered our page speed, and there's no choice ... by systemBuilder on Thursday April 11, 2019 @12:47AM (#19631230)
As a former SRE for Google who cared for AMPHTML FROM BIRTH, NOBODY IS FORCING YOU TO USE AMP. In return for free hosting of the web content the publisher agrees to use the AMP format/subset. The whole point of the project was to stop walled gardens, like BBC app, like CNN app,etc., which arose because of crappy slow web pages! That was killing the searchable mobile web! AMP is to enable mobile search! The motivation is in the first page of every dang design doc for AMP at Google! You might be really surprised to learn that your supposed plan for world domination is run on a shoestring and a low priority at Google!
Re:Google AMP lowered our page speed, and there's no choice ... by millstone on Thursday April 11, 2019 @02:38AM (#19631709)
Wow, a "shoestring low priority" project gets top search result placement, a custom icon callout, and cannot be disabled. What do the high-pri projects get?
Re:Google AMP lowered our page speed, and there's no choice ... by majewsky on Thursday April 11, 2019 @04:41AM (#19632149)
High-prio projects get to be a requirement for commenting on Youtube.
[dead]
Re:Google AMP lowered our page speed, and there's no choice ... by dralley on Thursday April 11, 2019 @08:52AM (#19633897)
What's your response to this?

https://news.ycombinator.com/item?id=19632481?

If that's the goal, then it does not seem universally effective.

Re:Google AMP lowered our page speed, and there's no choice ... by ehnto on Thursday April 11, 2019 @03:27AM (#19631893)
When it affects your bottom line by changing ranking factors then it is no longer as optional as you make it out to be.

Google decided to dominate the search world, and it now underpins a huge portion of online businesses. That comes with a level of responsibility to be fair to it's patrons that in this particular instance I feel isn't being met.

Of course they can do whatever they want, it is their product, but we don't have to like it.

Re:Google AMP lowered our page speed, and there's no choice ... by JohnFen on Thursday April 11, 2019 @12:42PM (#19636433)
> NOBODY IS FORCING YOU TO USE AMP.

That sure doesn't seem to be true at all.

Re:Google AMP lowered our page speed, and there's no choice ... by AnthonyMouse on Wednesday April 10, 2019 @11:30PM (#19630926)
It's quite ironic that Google is getting into trouble with the EU for nonsense like excluding search engine spam from its results, when it's stuff like this that really has that classic Phone Company feel to it.
Re:Google AMP lowered our page speed, and there's no choice ... by jeltz on Thursday April 11, 2019 @02:51AM (#19631764)
The EU works slowly so it is way too early to say if Google will get in trouble or not for AMP.
Re:Google AMP lowered our page speed, and there's no choice ... by AnthonyMouse on Thursday April 11, 2019 @03:07AM (#19631823)
The problem is that doesn't work to produce desired behavior. If you slap them for the wrong stuff then one of two things happens.

The first is they conclude they're going to get slapped no matter what and then do whatever they want and write off the penalties as unavoidable because better behavior doesn't actually avoid them anyway.

The second is they conclude that the only way to avoid the penalties is to grease the right palms, you induce them to figure out how to do that, and then they still do whatever they want because once you force them to corrupt your institutions in order to not be treated unfairly, those institutions no longer threaten them even when they misbehave.

The only scenario that leads to behavior improvements is the one where all the penalties are assigned justly and proportionally, to behavior that could reasonably be predicted ahead of time as prohibited.

Re:Google AMP lowered our page speed, and there's no choice ... by geezerjay on Thursday April 11, 2019 @03:50AM (#19631977)
> If you slap them for the wrong stuff

None of the FAANG is being slapped by the EU for the wrong stuff. They aren't being slapped for your specific example (yet) but that doesn't mean that forcing their self-serving choices onto powerless users deserves a pass.

Re:Google AMP lowered our page speed, and there's no choice ... by AnthonyMouse on Thursday April 11, 2019 @12:49PM (#19636520)
> None of the FAANG is being slapped by the EU for the wrong stuff.

A lot of the other stuff is things like not putting links to another search engine's results page in their search engine's results page. It's pure nonsense.

Re:Google AMP lowered our page speed, and there's no choice ... by sergiosgc on Thursday April 11, 2019 @07:33AM (#19633199)
> The first is they conclude they're going to get slapped no matter what and then do whatever they want and write off the penalties as unavoidable because better behavior doesn't actually avoid them anyway.

European Commission fines are no small matter. They may be small at first, and may even be zero (just a warning), but the policy is to increase fines on non-compliance up to the point where the target complies. They can't write off penalties as unavoidable.

Re:Google AMP lowered our page speed, and there's no choice ... by AnthonyMouse on Thursday April 11, 2019 @12:41PM (#19636427)
And if the fines are being imposed on actions that it would be hard to predict ahead of time would result in a fine, that leaves them with the second option (use money to buy influence), which is probably the worst of all because it's stable.

Once you convince a company that paying whatever it takes to buy a government is the only way to avoid random multi-billion dollar fines, you've created a long-term structural problem, because it becomes the status quo and is hard to undo. And then the government can't even punish them when they're actually being bad.

Re:Google AMP lowered our page speed, and there's no choice ... by tyfon on Thursday April 11, 2019 @07:53AM (#19633348)
I'm not sure that amp is available in Europe. I live in a EEA country and I've never seen an amp page. Curious if this is the case in the rest of Europe.
Re:Google AMP lowered our page speed, and there's no choice ... by manigandham on Thursday April 11, 2019 @12:27AM (#19631162)
With the coming ITP changes in Mobile Safari, it also helps Google maintain 1st-party cookies by never leaving their domains.
Re:Google AMP lowered our page speed, and there's no choice ... by millstone on Thursday April 11, 2019 @02:46AM (#19631755)
Also often defeats Safari Reader Mode, though I guess there will be a bit of an arms race here.
Re:Google AMP lowered our page speed, and there's no choice ... by lern_too_spel on Thursday April 11, 2019 @11:21AM (#19635437)
Safari Reader mode is too stupid to use the canonical URL. That's Apple's problem.
Re:Google AMP lowered our page speed, and there's no choice ... by burtonator on Wednesday April 10, 2019 @11:07PM (#19630822)
Web users and independent sites need more stories like this as it's impossible to understand these things from their perspective unless you have this kind of traffic.
Re:Google AMP lowered our page speed, and there's no choice ... by codedokode on Wednesday April 10, 2019 @11:08PM (#19630825)
Is looks like Google just needs AMP to be able to display other sites' pages on its site and mobile app. But I don't understand why they just don't take a "Reader mode" implementation from Firefox to produce text-only pages instead of making publishers develop a second version of their sites.
Re:Google AMP lowered our page speed, and there's no choice ... by gowld on Wednesday April 10, 2019 @11:47PM (#19630997)
Reader Mode (Simplified View in Android Chrome) drops ads, which publishers would not appreciate.
Re:Google AMP lowered our page speed, and there's no choice ... by devoply on Wednesday April 10, 2019 @10:26PM (#19630616)
There should be a law!
Re:Google AMP lowered our page speed, and there's no choice ... by vinceguidry on Wednesday April 10, 2019 @10:30PM (#19630633)
There should be, but there won't be, at least not anytime soon. This is still the wild west. Google is the corrupt sheriff whose task is to keep the place relatively safe and productive and is politically clear to enrich himself by his position, as no one else is going to pay him and no one important cares.

Give it another fifty years and the web will finish civilizing.

Re:Google AMP lowered our page speed, and there's no choice ... by jacobolus on Wednesday April 10, 2019 @10:50PM (#19630747)
Does “civilizing” mean “entirely taken over by feudal lords instead of just mostly”?
Re:Google AMP lowered our page speed, and there's no choice ... by geezerjay on Thursday April 11, 2019 @03:55AM (#19631995)
The judiciary is quite literally the outcome of a feudal society (courts?), but that doesn't mean that civilized societies don't benefit from establishing rule of law.

In fact, the absense of laws just means that some random individual can and will have power over you without you having any say on the matter.

Re:Google AMP lowered our page speed, and there's no choice ... by Moru on Thursday April 11, 2019 @12:58AM (#19631276)
I chose to see that positively. In 50 years the Web has civilised into something that is not run by a big company and governed by sane rules.
Re:Google AMP lowered our page speed, and there's no choice ... by john-radio on Wednesday April 10, 2019 @10:39PM (#19630681)
> Give it another fifty years

I see you have not been following the CO2 news.

Re:Google AMP lowered our page speed, and there's no choice ... by snek on Wednesday April 10, 2019 @10:57PM (#19630786)
The reason I have gotten from google employees is that the top stories carousel preloads content, and that in order to preload content without leaking a user's searches, google needs to serve their own cached version of a page. in order to make sure that cached version of a page isn't doing anything tricky, they need to heavily limit what it can do.

it's not about making the internet faster, it's about making it easy for google's stupid scroller.

Re:Google AMP lowered our page speed, and there's no choice ... by tyingq on Wednesday April 10, 2019 @11:18PM (#19630873)
That's a bit circular. The carousel predates AMP, so they somehow knew how to manage this in the past.
Re:Google AMP lowered our page speed, and there's no choice ... by slumos on Thursday April 11, 2019 @12:56AM (#19631267)
Sure they did — partnerships and whitelists. Is that what you would prefer?
Re:Google AMP lowered our page speed, and there's no choice ... by tyingq on Thursday April 11, 2019 @07:32AM (#19633192)
I believe AMP to be a sort of trojan horse that leads to a fragmented internet. A way for Google to have some degree of a walled web garden. So yes...I'd prefer almost anything else. If you're signing a contract to be part of it, at least you know what is happening, and can read the terms.
Re:Google AMP lowered our page speed, and there's no choice ... by JohnFen on Thursday April 11, 2019 @12:44PM (#19636466)
Yes. Since I automatically ignore anything in the carousel anyway, I'd much prefer that AMP be nonexistent regardless of what that means for the carousel.
Re:Google AMP lowered our page speed, and there's no choice ... by snek on Thursday April 11, 2019 @11:33AM (#19635614)
but the carousel didn't preload content before amp
Re:Google AMP lowered our page speed, and there's no choice ... by tyingq on Thursday April 11, 2019 @12:08PM (#19636069)
It also didn't hijack the page header, back button, and left/right swipe actions on other people's pages.
Re:Google AMP lowered our page speed, and there's no choice ... by codedokode on Wednesday April 10, 2019 @11:12PM (#19630839)
Another thing might be that this way Google can observe user's behaviour: how much time they spent reading the article, what part did they read carefully etc. which is only possible if the user stays on Google's domain.
Re:Google AMP lowered our page speed, and there's no choice ... by thrwwysearcheng on Wednesday April 10, 2019 @11:23PM (#19630902)
Throwaway for a Google search engineer here. I can tell you we aren’t interested in that at search as a signal, but publishers who are interested can run their own analytics through our platform. I’m not aware of any that do it to that level of granular detail.
Re:Google AMP lowered our page speed, and there's no choice ... by brazzledazzle on Wednesday April 10, 2019 @11:58PM (#19631049)
It would seem odd for Google to focus on that level of detail unless they’re producing the content. They know what you searched for, what content is on the page and if/when you came back to Google. How long you spent on a specific paragraph or image doesn’t seem like it would help Google improve search or target ads better.
Re:Google AMP lowered our page speed, and there's no choice ... by indigo945 on Thursday April 11, 2019 @01:45AM (#19631480)
It does help with improving search, though, because you now have data that shows that the words in that paragraph are somehow closely related to the search term. This is relevant data to feed into the ML models.
Re:Google AMP lowered our page speed, and there's no choice ... by Ajedi32 on Wednesday April 10, 2019 @11:16PM (#19630863)
> it's not about making the internet faster

Are you saying preloading content _doesn't_ make the internet faster?

Re:Google AMP lowered our page speed, and there's no choice ... by 3xblah on Thursday April 11, 2019 @03:25AM (#19631886)
https://news.ycombinator.com/item?id=12542782

AMP is search engine "paid placement" reborn.

The "payment" is letting Google serve the pages and do the user tracking.

Re:Google AMP lowered our page speed, and there's no choice ... by petre on Wednesday April 10, 2019 @11:45PM (#19630988)
They're looking at another antitrust case in the EU.
Re:Google AMP lowered our page speed, and there's no choice ... by tjpnz on Thursday April 11, 2019 @12:13AM (#19631103)
It certainly smells of the shady shit Microsoft was doing back in the day.
Re:Google AMP lowered our page speed, and there's no choice ... by ben_jones on Wednesday April 10, 2019 @08:53PM (#19630155)
No the purpose of Google Search is to facilitate selling Ads.
Re:Google AMP lowered our page speed, and there's no choice ... by jeromebaek on Wednesday April 10, 2019 @11:20PM (#19630887)
What do you think? :-) it's obvious, it's capitalism, isn't it?
Re:Google AMP lowered our page speed, and there's no choice ... by lern_too_spel on Wednesday April 10, 2019 @09:04PM (#19630205)
I'm not Google, but the reason is obvious to anyone who understands AMP. Only AMP can be guaranteed safe to preload through static analysis, and a carousel lets the search results page figure out which pages to preload trivially (the results currently visible in the the carousel).
Re:Google AMP lowered our page speed, and there's no choice ... by geofft on Wednesday April 10, 2019 @09:51PM (#19630461)
> Only AMP can be guaranteed safe to preload through static analysis

This isn't how static analysis works. Yes, the halting problem says you can't determine safety of any possible input in a Turing-complete language, and yes, JS is Turing-complete. But it doesn't say you can't determine safety of some inputs. You can write an algorithm that outputs "Yes," "No," and "I don't know" just fine. Google can, if they desire, specify some rules / annotations that would help its analyzer answer "Yes" to more pages. They've chosen not to do that, and instead to only build an analyzer for AMP.

Besides, preloading pages is about fetching content, not rendering them, I think.

Re:Google AMP lowered our page speed, and there's no choice ... by cromwellian on Wednesday April 10, 2019 @09:57PM (#19630487)
> specify some rules / annotations that would help its analyzer answer "Yes" to more pages

Isn't that exactly what AMP is? Whatever "rules" Google specifies will in fact, define a DSL/subset of HTML that can efficiently answer "yes". As people demand more and more capability in this ruleset, eventually you'll end up with something like AMP, only the syntax will be slightly different, but the fact that it is a weird subset of HTML will remain.

Re:Google AMP lowered our page speed, and there's no choice ... by cyxxon on Thursday April 11, 2019 @03:04AM (#19631816)
In a way yes, but isn't one of the "rules" that is has to be cached/re-served from Googles servers as well? That is a rather problematic one, especially wrt antitrust issues...
Re:Google AMP lowered our page speed, and there's no choice ... by lern_too_spel on Thursday April 11, 2019 @11:13AM (#19635311)
No, those rules guarantee that the page is safe to preload. It will also be cached and preloaded by Bing, Baidu, and Cloudflare.
Re:Google AMP lowered our page speed, and there's no choice ... by lern_too_spel on Wednesday April 10, 2019 @10:11PM (#19630555)
AMP doesn't allow arbitrary JS. It only allows a fixed set of components. That's what makes it amenable to (trivial) static analysis -- just verify that the page contains only the elements allowed by AMP.
Re:Google AMP lowered our page speed, and there's no choice ... by realusername on Wednesday April 10, 2019 @09:43PM (#19630417)
> Only AMP can be guaranteed safe to preload through static analysis

No, AMP pages can't be proven safe, because with AMP you can include ads which are a very common vector of malware.(if I understand your comment)

Re:Google AMP lowered our page speed, and there's no choice ... by lern_too_spel on Wednesday April 10, 2019 @10:44PM (#19630708)
Ads aren't preloaded in AMP pages.

Also, I don't think you understood my comment. I mean safe as in not deanonymizing the user to pages they don't visit. If you preload a non-AMP page, you have deanonymized your user to a third party publisher and the ad servers on that page.

Re:Google AMP lowered our page speed, and there's no choice ... by realusername on Wednesday April 10, 2019 @11:22PM (#19630897)
> Ads aren't preloaded in AMP pages.

That does not make a big difference.

> Also, I don't think you understood my comment. I mean safe as in not deanonymizing the user to pages they don't visit. If you preload a non-AMP page, you have deanonymized your user to a third party publisher and the ad servers on that page.

Sorry I still don't get it, with AMP it's exactly the same except that 3rd party is the Google AMP server. You can also load analytics & trackers with AMP as well. There's no privacy in the AMP design goals.

Re:Google AMP lowered our page speed, and there's no choice ... by underwater on Wednesday April 10, 2019 @11:40PM (#19630970)
If Google allowed arbitrary pages in the carousel, and then preloaded those pages, then BBC and BuzzFeed could insert trackers that let them know what you searched for even if you never click on a result.

This is not true for AMP analytics because Google define the JS and can defer sending analytics events until after the user has clicked on an item in the carousel.

Google can either preload content, allow non-AMP pages, protect users from data leakage, but not all three at once. They have chosen to sacrifice non-AMP content.

Re:Google AMP lowered our page speed, and there's no choice ... by realusername on Thursday April 11, 2019 @12:17AM (#19631120)
> If Google allowed arbitrary pages in the carousel, and then preloaded those pages, then BBC and BuzzFeed could insert trackers that let them know what you searched for even if you never click on a result.

There's nothing you can do with the carousels that they can't do by just parsing the content or meta tags they could have defined. And when you click on the carousel, it could have redirected to their page.

And before you talk about the "speed" of preloading like I've seen this argument over and over again on AMP threads, AMP could have defined an HTTP header which would have made the browser understand it's an AMP page and load the cached AMP JS (among other stuff like refusing to load non-AMP content), there's no technical need for an AMP server.

Re:Google AMP lowered our page speed, and there's no choice ... by joegahona on Thursday April 11, 2019 @12:48AM (#19631236)
Google can choose to sacrifice non-AMP content. But the header above this feature should read something like "AMP Content," not "Top Stories." The latter strongly implies that those are the most relevant results from the user's web search, but they are not. They are a subset of the most relevant results from the user's web query. A more precise and less misleading heading would be appropriate.
Re:Google AMP lowered our page speed, and there's no choice ... by codedokode on Wednesday April 10, 2019 @11:15PM (#19630853)
Cannot this problem be solved by producing a text-only version of the page using Firefox's reading mode algorithm that removes everything except the article text? This way publishers don't have to invest resources in making a second version of their site.
Re:Google AMP lowered our page speed, and there's no choice ... by Godel_unicode on Thursday April 11, 2019 @12:20AM (#19631134)
Good luck browsing news stories with video content or image slideshows. Also publisher analytics, advertising, and all the other basic staples of web journalism. But yes, if you completely change everything about the business model of online news, reader mode might be viable.
Re:Google AMP lowered our page speed, and there's no choice ... by TeMPOraL on Thursday April 11, 2019 @07:18AM (#19633089)
> *Also publisher analytics, advertising, and all the other basic staples of web journalism. But yes, if you completely change everything about the business model of online news (...).

Yes, this is the solution and should be the ultimate goal to fight for. Those "staples" are precisely what's ruining the web journalism, and the Internet at large.

Re:Google AMP lowered our page speed, and there's no choice ... by dmitriid on Thursday April 11, 2019 @12:26AM (#19631161)
Let me introduce you to USA Today European Experience: https://eu.usatoday.com

It’s possible to create a non-bloated fast news website. Neither publishers nor Google are interested in that.

Re:Google AMP lowered our page speed, and there's no choice ... by Godel_unicode on Thursday April 11, 2019 @12:31AM (#19631177)
> Neither publishers nor Google are interested in that.

See previous comment about the way the online news business works.