249. The speed benefits Google marketed were also at least partly a result of Google’s throttling. Google throttles the load time of non-AMP ads by giving them artificial one-second delays in order to give Google AMP a “nice comparative boost.” Throttling non-AMP ads slows down header bidding, which Google then uses to denigrate header bidding for being too slow. “Header Bidding can often increase latency of web page…
They're also pushing for the adoption of Signed HTTP Exchanges, with several Google employees defending the spec here on HN, comparing it to be merely like HTTPS in terms of publishers giving up control over their content. It's clear that Chrome must be separated from Google and Alphabet, nothing else will stop them from trying to colonize the web.
Where did you read that? I was under the impression that SXG is more similar to things like IPFS, where you can have content signed by its origin (or in IPFS, content addressed by its hash). Once that is achieved, any other site (e.g. a CDN like Google or Cloudflare) can cache and serve it securely and with authentication.
You can sign whatever content you want with SXG, it isn't limited to AMP.