> Instead of speaking in vague terms about "application-level MITM from Google's back end" I don't consider actual, verifiable, facts vague. > In real world t

> Instead of speaking in vague terms about "application-level MITM from Google's back end" I don't consider actual, verifiable, facts vague. > In real world terms, how can they choose to use AMP and how can they choose not to. They can use software that doesn't load AMP pages from Google and instead loads them from the host site. You can do this by using DuckDuckGo as a search engine which won't return URLs to Google's cache of AMP content. You can use messaging apps that will open your web browser and navigate to links rather than using the AMP version. Edit: Here is an example. Assuming you are on a desktop browser you should be able to navigate to this url and see a page: https://preview.amp.dev/documentation/examples/e-commerce/checkout_flow#development=1 https://preview.amp.dev/documentation/examples/e-commerce/ch... This is a Google made example of an AMP page. It's pretty bare bones but as you can see if you open up your browser's networking tab the browser is talking to `preview.amp.dev` not to the AMP caching URLs. Your browser is fetching content directly from the site. There is nothing stopping software from doing this with an AMP page.