3 ms·

> With prefetching my understanding (from what's been written publically) is that content will be allowed to be hosted on your own domain. Ie, your domain in th

> With prefetching my understanding (from what's been written publically) is that content will be allowed to be hosted on your own domain. Ie, your domain in the address bar. Are you saying otherwise? No. As I said, you can host it where you want. You can visit that domain and see your content. But Google are still going to rehost your content on their own server and direct their users to their copy, on their domain. > You think it causes an 8 second delay. It doesn't. Apologies, I assumed you'd have some understanding of frontend technologies when I posted the code above, so I'll explain how it works: - you have an inline CSS snippet that hides all page content for 8s (there is no reason for this). This is executed immediately. - you then have your amp.js file, pulled from Google's server, which should download and parse relatively fast (especially if you've put the script tag in the document head, as is recommended) - once amp.js is loaded and is parsed, it enables some further inline CSS which overrides the first inline CSS snippet, unhiding all page content instantaneously As I said above, the 8s delay is for non-AMP users; anyone not loading the amp.js resource from Google's servers, or anyone for whom the resource fails to load for any reason.

nailer 8y ago
> Google are still going to rehost your content on their own server and direct their users to their copy, on their domain. As long as my domain is in the address bar, and the content isn't modified - which I understand will be the case - I don't care. > As I said above, the 8s delay is for non-AMP users; No, that's not what you 'said' (wrote) above. You wrote: >> removing the artificial 8s delay on the CertSimple blog might be another line of inquiry. You wrote: >> The snippet I posted is a small bit of inline CSS at the top of your page that hides all page content for 8s. Implying there was an 8 second delay that normal users would see. Even now you're jumping through hoops to say 'non AMP users' where in reality you mean a tiny niche of users with broken network connectivity or who deliberate disable JavaScript, etc. Thanks for wasting my time. If you'd have said what you honestly knew "I dislike this as it won't show the site if users can't load the JavaScript" I would have said "fine I don't care". Instead you pretended something was actually wrong and I wasted time communicating with you and being insulted. Please do not communicate with me again. This is why HN needs a block button.

nailer 8y ago

> Google are still going to rehost your content on their own server and direct their users to their copy, on their domain. As long as my domain is in the address bar, and the content isn't modified - which I understand will be the case - I don't care. > As I said above, the 8s delay is for non-AMP users; No, that's not what you 'said' (wrote) above. You wrote: >> removing the artificial 8s delay on the CertSimple blog might be another line of inquiry. You wrote: >> The snippet I posted is a small bit of inline CSS at the top of your page that hides all page content for 8s. Implying there was an 8 second delay that normal users would see. Even now you're jumping through hoops to say 'non AMP users' where in reality you mean a tiny niche of users with broken network connectivity or who deliberate disable JavaScript, etc. Thanks for wasting my time. If you'd have said what you honestly knew "I dislike this as it won't show the site if users can't load the JavaScript" I would have said "fine I don't care". Instead you pretended something was actually wrong and I wasted time communicating with you and being insulted. Please do not communicate with me again. This is why HN needs a block button.