How is hijacking the domain with Google for AMP not anti-competitive? I'm surprised a class action lawsuit hasn't erupted because of that.
Bing also uses the AMP standard: https://blogs.bing.com/Webmaster-Blog/September-2018/Introdu...
All these certificates do is make it so Google's browser (and only Google's browser) will mask the fact you're on Google's domains if you sign the file a certain way.
If anything, this shows more anti-competitive practices -- they're adding features into their browser that specifically benefit a features of their search engine.
If the criteria is just "needs extra work" then unfortunately almost nothing can change and we're all going to live with the existing technology. Change inherently has friction and requires "extra work" with the hope that's an investment which provides returns long term.
In other words, say you are a large Internet company that is trying to improve web page loading times. You profile why most web pages are slow and identify issues. You publicly report on those issues and develop guidelines and criteria. Nobody bothers because "extra work". You develop new technology that directly addresses those issues, this technology works within the existing environment but it requires both client and server support to be most effective. Do you think anyone cares? No, because of "extra work". That's why there needs to be incentives. Now you have a "penalty" for not doing that "extra work". You can file it under "it's anti-competitive" (maybe it is) but if you do the "extra work" then suddenly the anti-competitive part works for you, not against you. IMO that's why it's not anti-competitive.
Other examples: why do you think there are so many people that complained when iPhone released with Flash reader? "extra work". Similarly when it removed the audio jack. Change is friction and friction is extra work. But most of the time that's not anti-competitive...
HTML is already fast (see HN for an example). HTML is already universal across devices and browsers. HTML is already published and easily cached for billions of pieces of content.
AMP is a fork of HTML that only targets mobile browsers specifically linking from Google search results. It's useless on its own, but AMP is required to get higher placement on search results pages, so publishers are effectively forced to spend technical resources to output an entirely new format just to maintain that ranking.
If Google wanted faster pages then it can do what it always does and incentivize that behavior by ranking results based on loading speed. These signals are already collected and available in your Google webmaster console. There's nothing new to build, just tweak ranking calculation based on existing data. Sites would get faster overnight, and they would be faster for every single user because HTML is universal.
Do you know why they didn't do that? Because it's the ads and tracking that's slow, not the HTML. Google's Doubleclick and Google Analytics are the biggest adserver and tracking systems used on the web. This entire AMP project is created to circumvent their own slow systems. It creates more work for publishers while increasing data collection by running a "free" CDN that never leaves a Google-owned domain and thereby always supports first-party cookies. It's a perfect solution to protect against anti-tracking browsers and why Chrome now will also block 3rd-party cookies, because it won't affect AMP hosted on Google domains.
Probabilistic techniques are used for anonymous users or environments like iOS Safari that are very strict.
https://amp.businessinsider.com/lambda-school-online-coding-...
If you visit the page from search results (which is the only place it would be linked) then it would never leave Google's domain.
Here's the actual URL used from search results: https://amp-businessinsider-com.cdn.ampproject.org/v/s/amp.b...
In other words: if it behaves exactly as a page hosted on your site (just faster), why do you care?
I'm getting the impression that HN users care a whole lot about seeing the request in the nginx log they are tailing.
Google is strong-arming the entire web to switch to AMP in order to increase their control over the distribution of content, and to be in a better position for tracking users.
The fact that Microsoft and Cloudflare have joined the party does not change the fact that you're about to lose control over your own content if this is not stopped.
Please disclose your affiliation to Google either in your bio or in comments, and don't post the same comment in multiple places.
This...doesn't make sense. You lose the value of a CDN (both to you and to the consumer of your content, in this case Google and the end user) if you're rolling your own.
We were talking about CDNs because your collegue mentioned AMP CDNs, but the main point doesn't change: we cannot serve our own content from our own servers and get the same placement in search results as AMP content, even if our content loads verifiably fast and is as performant as an AMP page on the client.
I have no clue who bdeurst is. They certainly aren't a colleague of mine.
> even if our content loads verifiably fast and is as performant as an AMP page on the client.
Can you explain to me how your page load time is 0ms? My understanding is that a correctly functioning AMP-cached page will load for the user in a whopping 0ms, because it can be preloaded.
The entire design of AMP starts from a fairly straightforward premise: "How do we reduce (user-visible) page load times to 0, safely, cross origin?" If your pages user-visible loading time is longer than 0, you're failing to keep up with AMP.
prefetching isn't private cross origin:
> Along with the referral and URL-following implications already mentioned above, prefetching will generally cause the cookies of the prefetched site to be accessed.[1]
IDK about you, but I'd generally prefer that my cookies and IP not be exposed to all of the links that happen to be in the first page of search results.
[1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Link_prefe...
Yes, for example Signed Exchanges, which on a technical level solves all of the problems of rel=prefetch (and a number of the problems with AMP, like link pasting and copying).
> Should we allow a handful of companies to be pinged every time we load a page on the web
I'm hopelessly confused here: you're only going to "ping" one of the handful of companies if you were referred by that company. (In a world with signed exchanges) You're not going to come across an AMP-cache link organically. You'll navigate to example.com directly, without anyone except example.com (and your DNS provider) knowing. The cache provider will only know if you navigate to the cached site via the cache provider. Concretely, you don't go to the Google amp-cache unless you're navigating there directly from Google's search results. Same for Microsoft/Bing.
So if your metric is
> Should we allow a handful of companies to be pinged every time we load a page on the web
Then yes, absolutely, because nothing changes!
Edit: To address your other question,
> should we give Google and a handful of other companies disproportionate control over how we publish and consume content, for 50ms of load time?
Alright: how is AMP materially different from <whatever other algorithmic choices rated search results before>?
You seem to be claiming that AMP is harmful to someone but who? It's not harmful to competitors or to end users, and its only harmful to developers if you make the most strained argument.
My premises here are that users actually prefer AMP results. You may not, but my understanding is that most users do. So from the perspective of an end user browsing the internet, AMP leads to an improved experience.
So it's good for users.
No one has yet been able to explain to me how its actually harmful to a web developer who now has an incentive to make AMP-compatible sites. Like sure, you now have to work with a framework you may not like, but that's not a compelling argument when people are claiming that AMP is a threat to the sanctity of the internet.
So it's not like bad for web developers, it's just sort of a lateral move.
That leaves competitors to the giants. But AMP is an open standard, and DDG could, if they wished, implement an AMP cache themselves today and it would just work. And they'd, if anything, benefit from the bigger players pushing that ecosystem. There's the potential for abuse via the caches.json registry, but the AMP project is aware of this and notes that the registry could be decentralized using Subresource Integrity or similar, if such a standard was adopted[1].
So again: I'm confused by how exactly it's bad, beyond the "I am forced to develop in a way I don't want to if I want to appear near the top of the search page", which isn't new.
[1]: https://github.com/ampproject/amphtml/pull/18495/commits/c5d...
> So if your metric is
Google being pinged obviously isn't my main metric, as you can see from all my posts in our discussion. My main concern is that publishers will be forced to use specific publishing mechanisms (AMP, Signed Exchanges) to appear at the top of Google Search results. That loss of control puts publishers in a vulnerable position, and hurts innovation across the web.
> Then yes, absolutely, because nothing changes!
Everything changes. Google's influence and control won't end at the moment the user navigates away to a top result on Google Search.
And iiuc, sites are still free to revoke their certs. So this is actually probably more secure compared to something like https in that regard.
[0]: https://github.com/WICG/webpackage/blob/6cc3237b36c2f9ce7534...
Also, everything I say on HN reflects my own opinion and not any organization, which is what my profile states. I do not hide behind an anonymous username precisely for this reason. Poisoning the well by doxxing me doesn't change how the AMP standard works for CDNs either, and only serves to derail the conversation.
Sorry, but I agree with dessant. Your profile doesn't disclose your affiliation and nor do your comments. It's absolutely relevant to the discussion, because whether you want to admit it or not (or try your best to act neutral), your day job will have some influence over your opinions on these sort of projects.
You're right that it doesn't change objective facts about the specification, but I think it's misleading to suggest that, in general, external third-party CDNs are first class citizens in the AMP ecosystem when they're not treated the same within search.
Enjoy the popups, video ads, autoplay, bloated sizes, etc.
I find the non-AMP version to be superior every single time, but I use NoScript so I don't see the popups, video ads, autoplay, etc.
Your "choice".