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.
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?
AMP pages displaying your own domain
111–120 of 340 posts
Re: AMP pages displaying your own domain
#112Earlier quoted context omitted.
They can already do that, and are doing so, through Search, Analytics (maybe), ads, etc. That war is long lost.
They can't if you block all their shitty domains and don't use google services. Things that many privacy-conscious users do.
Re: AMP pages displaying your own domain
#113Earlier 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.
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
#114Earlier quoted context omitted.
AMP allows Google to see exactly how you interact with every page on the internet. Just from the text of the pages you visit they can build a profile around you. What your interests are, how much of an article you're likely to finish, whether you're the type of person to highlight text as you read, etc. Unless you live on an island with a poor satellite connection AMP is useless as anything more than a corporate user…
They can already do that, and are doing so, through Search, Analytics (maybe), ads, etc. That war is long lost.
Re: AMP pages displaying your own domain
#115This 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…
I decided it's time to give DuckDuckGo another shot. I just realised it's a lot nicer to scroll through its results than Google is now.
Re: AMP pages displaying your own domain
#116For people who don’t like AMP, avoiding it is really easy: Don’t use Google search. That’s all. That’s really all there is to it. You should give it a try!
Re: AMP pages displaying your own domain
#117For people who don’t like AMP, avoiding it is really easy: Don’t use Google search. That’s all. That’s really all there is to it. You should give it a try!
One example: https://news.ycombinator.com/item?id=19679136 , luckily someone also provided the non-amp equivalent...
Re: AMP pages displaying your own domain
#118Re: AMP pages displaying your own domain
#119Now there's a solution that preserves the preloading and validation benefits of AMP caches but maintains the original URLs, in a way that's cryptographically sound, in the process of being standardized, and controlled by the publisher. This gets launched much faster than one would have expected. And suddenly everyone pretends that the AMP cache URLs were never a problem and this is some kind of a power-grab.
Re: AMP pages displaying your own domain
#120The 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?