AMP pages displaying your own domain • Hacker News Board

Re: AMP pages displaying your own domain

#91

Post by josteink » Wed, Apr 17, 2019, 8:39 AM UTC

millstone wrote: post #35

The headline is an outright lie: these AMP pages are loaded from Google and not your domain. The new feature is that Google's browser displays your domain, obscuring the fact that Google is doing the serving. The change is what is displayed, not the server.

WTF. Lost for words.

So Google’s browser now directly lie to the user about what’s being loaded?

I bet the SSL mark is still there though?

How can anyone trust this Googlan horse?

This is why you don’t make a browser and control major web-assets at the same time. These lines should not be muddied.

Re: AMP pages displaying your own domain

#92

Post by Moru » Wed, Apr 17, 2019, 8:45 AM UTC

Kiro wrote: post #81

48309248302 wrote: post #12

Earlier quoted context omitted.

Brussels sprouts are good for you. AMP is more like medical experiments performed on you during an alien abduction.

What's up with this extreme hatred for AMP? I personally love AMP.

Most people do not like to be forced to do things a certain way. Especially if they have a working site already and now have to remake it from the ground up just because some other actor decided it isn't good enough to get visitors.

Just you wait until you notice you can't go to town in your car any more. Only teslas are allowed into city.

Re: AMP pages displaying your own domain

#93

Post by thx-i-hate-it » Wed, Apr 17, 2019, 8:48 AM UTC

Thanks, I hate it.

Re: AMP pages displaying your own domain

#94

Post by josteink » Wed, Apr 17, 2019, 8:49 AM UTC

gregable wrote: post #36

48309248302 wrote: post #11

This sounds terrible. Does it mean that browsers will begin lying to users and say that the users are visiting the website's server when they are really visiting a restricted version of the website that is hosted in Google's cache? I don't want my content restricted or hosted in Google's cache. AMP doesn't load in a privacy sensitive way. It's on Google's servers and it takes many seconds to load if you have JavaScri…

The browser displays the URL from the origin that digitally signed the unmodified content. A browser already doesn't show you what server delivered the content. That would be your wifi AP, cell phone tower, or ISP node. The internet has already long established that we can trust content without trusting intermediaries. There are two elements that are important: integrity and privacy. The content integrity is protecte…

> A browser already doesn't show you what server delivered the content. That would be your wifi AP, cell phone tower, or ISP node.

No. Incorrect. Completely backwards. Factually wrong. You just failed your networking-exam.

Those things you mentioned would be transparent networking nodes forwarding your TCP-packets and they have nothing to do with any layers above that.

The fact that you don’t even know this completely invalidates any other point you may have.

Re: AMP pages displaying your own domain

#95

Post by Kiro » Wed, Apr 17, 2019, 8:50 AM UTC

Moru wrote: post #92

Kiro wrote: post #81

Earlier quoted context omitted.

What's up with this extreme hatred for AMP? I personally love AMP.

Most people do not like to be forced to do things a certain way. Especially if they have a working site already and now have to remake it from the ground up just because some other actor decided it isn't good enough to get visitors. Just you wait until you notice you can't go to town in your car any more. Only teslas are allowed into city.

That's a bad example for me personally since I think all cars should be banned (except maybe electric cars but I haven't done the necessary research to see the actual environmental impact). I haven't used my driver's license in years and always take the train (I've also stopped flying).

But anyway, that's off topic. I understand that it's a pain for developers but for users like me who are often on a bad connection it's a life saver.

Re: AMP pages displaying your own domain

#96

Post by noncoml » Wed, Apr 17, 2019, 8:51 AM UTC

Alternative title: why you shouldn’t be using Chrome.

Split Alphabet already.

Re: AMP pages displaying your own domain

#97

Post by jonplackett » Wed, Apr 17, 2019, 8:56 AM UTC

I hate AMP. Not just for google thinking they own the internet. They never seem to load right on my phone and crash a lot too.

Re: AMP pages displaying your own domain

#98

Post by foota » Wed, Apr 17, 2019, 8:57 AM UTC

millstone wrote: post #35

The headline is an outright lie: these AMP pages are loaded from Google and not your domain. The new feature is that Google's browser displays your domain, obscuring the fact that Google is doing the serving. The change is what is displayed, not the server.

At this point, if you ignore the amp aspect, how is this any different from plain http caching?

Re: AMP pages displaying your own domain

#99

Post by themacguffinman » Wed, Apr 17, 2019, 8:58 AM UTC

abc-xyz wrote: post #54

eitally wrote: post #24

Earlier quoted context omitted.

No it isn't. It's designed to make the user experience better on sites that frequently host Google ads (and also often contain a ton of bloat, 3rd party js, poorly constructed DOMs, awful CSS, etc). The only way Google could proactively "solve" this problem was by creating a "standard", and then also offering to absorb end user traffic for sites that adopted the standard. FWIW, AMP is an open standard not solely owne…

Why is that the only way? Seems like they could easily have achieved the same result by significantly penalizing sites based on load time and number of external requests.

Because users want relevant search results much more than fast websites. Google already factors in a website's performance in their rankings, but weighing it too much over content relevance will make search results worse.

Re: AMP pages displaying your own domain

#100

Post by themacguffinman » Wed, Apr 17, 2019, 8:59 AM UTC

mthoms wrote: post #84

abc-xyz wrote: post #54

Earlier quoted context omitted.

Why is that the only way? Seems like they could easily have achieved the same result by significantly penalizing sites based on load time and number of external requests.

This question cuts right to the heart of the matter. I've yet to see a Google engineer, executive, or "fanboy" address this question adequately. This thread will be no exception. Queue the crickets.

Because users want relevant search results much more than fast websites. Google already factors in a website's performance in their rankings, but weighing it too much over content relevance will make search results worse.