Comment by buboard | Hacker News Reader

Comment by buboard | Hacker News Reader

Parent Full thread

- fundamentally changes the way the web works. Websites suddely became second citizens, essentially making google search the primary citizen who serves other people's content as if it s their own.

- It splits each webpage in two.

- Hiding the real domain means fake sites and phishing are possible

- Prerendering downloads on average 1.4 MB of data with every search results page that the user may not even want or ever choose to see (it might even become a huge secuyrity hole). This probably renders server-side analytics useless too. only google now knows the truth about your traffic

- single point of failure for a government to shut down / censor articles / delete specific information from all news websites

- obvious google's control of your content / and manipulatively ranking higher the content they render - I expect this to cause an anti-trust fine very soon

- Replacing HTML with an abomination , which WILL be abused in a few months, the same way that html is currently abused in news sites.

i m curious how they manage to preserve privacy if they route api requests through their servers

See https://webmasters.googleblog.com/2019/04/instant-loading-am... which addresses the concern about the URL. You can see it for a number of sites already. For example, search for an AMP result from collins dictionary.

As reported in the paper, prerendering only affects amp pages in the first viewport of the search results, which is reported as 10% of the results in their sample. Prerendering does not have any security issues. AMP guarantees that all resources in preload are served by the AMP cache, and custom javascript is prevented by your browser via CSP.

Javascript based analytics works fine, with support for all major vendors and custom setups.

That "standard" is an abomination. What's next, we 'll upload our SSL certs to google so they can masquerade more efficiently? IETF should not back standards introduced by and benefiting only google.

> Prerendering does not have any security issues.

Currently. Are you saying it is impossible that someone will hide a hack in an amp page that steals data or sth without the user ever visiting that amp page?

> AMP guarantees that all resources in preload are served by the AMP cache,

What about privacy? are user data sent through google's servers?

> Javascript based analytics works fine, with support for all major vendors and custom setups.

How do those analytics handle prerendering?

AMP documents are delivered with a Content-Security-Policy which instructs the browser not to load javascript resources outside the AMP origin, including inline scripts. The AMP Cache ensures no remote images or other remote resources can be loaded in preload.

When using signed exchanges, the preload does not even parse the document until navigation, as per the signed exchange spec.

Analytics loading is deferred until after user navigation, which makes sense as the user has yet to navigate to the document.

The AMP Cache serves publicly cached HTML documents, and the static fonts/images within those documents. If a document wants to render user specific data, it can load that directly from the publisher's origin upon navigation (not routed via the AMP Cache). See, for example https://amp.dev/documentation/components/amp-list/. Analytics, ads, etc are all fetched directly from the vendor or publisher origin and the AMP Cache will neither proxy nor otherwise see this data.

Thats not really loading it from the remote site is it, its more the url bar lying to the end user? What happens if you copy the url or enter it directly?

Yes and no. The browser is making an HTTPS request to the AMP Cache for the document. The document's integrity is ensured by the cryptographic signature of the publisher's origin which the browser verifies. As far as the integrity of the document, this is the same conceptually as the fact that your wifi router is actually serving the document to your browser. The AMP Cache cannot modify the document, and the publisher may choose what to sign or not sign.

Entering the URL directly will make an HTTPS request to the URL's origin server, as it always has. There will be no AMP Cache involved in that request, but it will work just the same.

Reply on news.ycombinator.com