7 ms·

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, obs

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.

mthoms 8y ago
Indeed. If a web page is being served or loaded "from your own domain" that implies something very specific. What Google actually means here is "We make AMP pages _appear_ to come from your own domain". That's something entirely different. This whole thing is just more doublespeak.
- sametmax 8y ago
  It's even worse than that. When I had a website with embed videos from other sites, I had user contacting me because the other sites had some problems. They couldn't tell the difference between megavideo/youtube/dailymotion content and my site, so they came to me and blamed me. So what this means is that not only Google bullies you into putting your traffic under their control, but now, any problem on their part will be blamed on you by the user.
  - AlexandrB 8y ago
    > So what this means is that not only Google bullies you into putting your traffic under their control, but now, any problem on their part will be blamed on you by the user. I hadn't even considered that. Add to this Google's notoriously absent customer support department and you have a recipe for a lot of frustration.
- deleted 8y ago
  [deleted]
josteink 8y ago
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.
foota 8y ago
At this point, if you ignore the amp aspect, how is this any different from plain http caching?
- deleted 8y ago
  [deleted]
- josteink 8y ago
  When I click a search result for company.com I expect to be taken to the resulting page at company.com, not Google’s HTTP-cache of that page.
- carnagii 8y ago
  the consumer is being lied to about who is serving their request and who is tracking their online activity as a result.
leeoniya 8y ago
next month they'll also style it like your browser's native address bar for a better user experience and intoduce a w3c standard API for hiding the real address bar. /s?
- gsich 8y ago
  They already had the braindead idea of hiding parts of the URL like "www." or "m." so it's not that unrealistic unfortunately.
  - 48309248302 8y ago
    They have been trying to make it so that users can't tell if they are on real webpages or AMP pages, and it looks like they finally implemented it. AMP is about Google, tracking, and ads, not page speed, even if they have convinced many of their engineers that it's about page speed.

mthoms 8y ago

Indeed. If a web page is being served or loaded "from your own domain" that implies something very specific. What Google actually means here is "We make AMP pages _appear_ to come from your own domain". That's something entirely different. This whole thing is just more doublespeak.

sametmax 8y ago
It's even worse than that. When I had a website with embed videos from other sites, I had user contacting me because the other sites had some problems. They couldn't tell the difference between megavideo/youtube/dailymotion content and my site, so they came to me and blamed me. So what this means is that not only Google bullies you into putting your traffic under their control, but now, any problem on their part will be blamed on you by the user.
- AlexandrB 8y ago
  > So what this means is that not only Google bullies you into putting your traffic under their control, but now, any problem on their part will be blamed on you by the user. I hadn't even considered that. Add to this Google's notoriously absent customer support department and you have a recipe for a lot of frustration.
deleted 8y ago
[deleted]

josteink 8y ago

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.

foota 8y ago

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

deleted 8y ago
[deleted]
josteink 8y ago
When I click a search result for company.com I expect to be taken to the resulting page at company.com, not Google’s HTTP-cache of that page.
carnagii 8y ago
the consumer is being lied to about who is serving their request and who is tracking their online activity as a result.

leeoniya 8y ago

next month they'll also style it like your browser's native address bar for a better user experience and intoduce a w3c standard API for hiding the real address bar. /s?

gsich 8y ago
They already had the braindead idea of hiding parts of the URL like "www." or "m." so it's not that unrealistic unfortunately.
- 48309248302 8y ago
  They have been trying to make it so that users can't tell if they are on real webpages or AMP pages, and it looks like they finally implemented it. AMP is about Google, tracking, and ads, not page speed, even if they have convinced many of their engineers that it's about page speed.