For 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!
AMP pages displaying your own domain
101–110 of 340 posts
Re: AMP pages displaying your own domain
#102Alternative title: why you shouldn’t be using Chrome. Split Alphabet already.
Yep, I'm off to the Firefox world. I hate amp with a passion. Straight garbage.
Re: AMP pages displaying your own domain
#103This calls for several billions EU fine...
Re: AMP pages displaying your own domain
#104The 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?
Re: AMP pages displaying your own domain
#105Earlier 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.
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
#106We need to decouple two things that are mashed together in this post:
Web packaging and Signed exchanges seems benign and beneficial, you can sign a particular page inside a package (let's say a zipped folder of some kind) and now anyone can cache that data and show it, while both the browser and the user knows that it's safe to display it. Since the AMP format is similar, it seems quite beneficial to now have all your AMP content support this feature. And anyone who made some of their pages AMP can use that same process to support other Signed Exchanges (such as p2p networks or CDNs) . This is great since it makes distributed caching much easier.
The bad part is that google search uses this signed exchange format not to show the actual URL but rather put it in an iframe inside chrome (and only chrome). The real question is whether we will be able to use this functionality outside search, if I have my own site and show a large iframe with signed exchange page, will I also be able to change the browser url bar? mmph, probably not.
Re: AMP pages displaying your own domain
#107So now there's literally no way to 'break out' of the AMP version and get the real webpage. Great.
Re: AMP pages displaying your own domain
#108The 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?
[deleted]
Re: AMP pages displaying your own domain
#109Earlier quoted context omitted.
And how is this all that much different? In fact I would say it's more secure. DNS can be spoofed pretty easily. This is a cryptographically signed package. If anything, I'd have more faith in this changing my URL than a proxy via DNS. Just because Google invented it doesn't make it bad.
> And how is this all that much different? It changes the meaning of the address bar from "this is who I'm talking to" to "this is who (at some point in time) signed this content".
But when there is a CDN there, "who I'm talking to" is really just an intermediary who pretends to be you, and may have in fact modified the content. With this, it is still an intermediary pretending to be you, but at least now the package is signed and can be verified.
Re: AMP pages displaying your own domain
#110Here's the real question - how is this implemented in chrome? are signed exchange website that are clicked in google search page and whose url is switched is still running the google search page's code?
If this is so, and it only works for google search's page and not some generic web strategy, this is a massive breach of browser/web-content separation, bigger then even the auto-sign-in to google from chrome.