you are viewing a single comment's thread.

view the rest of the comments →

[–]Dragonerne 6 insightful - 1 fun6 insightful - 0 fun7 insightful - 1 fun -  (3 children)

What happens is that websites using AMP will be loaded faster from Google. Google "renders" the entire website on their platform, so you basically never leave google. If you run chrome, it wont even show that you're still on Google, it will just show the url of the website that google is "rendering". On other browsers you will at least see that you're still on google but you might not care because its running faster.

Then google starts promoting AMP websites in their rankings. Slowly google is the "visible" internet. Then they can start removing stuff from websites that they don't want shown, because you're still on google. They're just rendering a different website for you like they want you to see that website. Etc.

[–]ThePlague 4 insightful - 1 fun4 insightful - 0 fun5 insightful - 1 fun -  (2 children)

Sooo, it sounds like Amp is Stadia for web pages. Like stadia, I'm not sure how remote rendering can be faster than local hardware, particularly for something like even a complicated web page. There's also the latency issue.

[–][deleted]  (1 child)

[deleted]

    [–]ThePlague 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

    The downside is that you never see the original site and their ad revenue is stolen.

    Hmmm, that sounds similar to "deep linking", or using frames to display the content of a web site while cutting off the ads and displaying your own. There was a court case about 15 years ago that addressed that, and made it actionable, possibly even illegal.