Hacker News new | past | comments | ask | show | jobs | submit login
Kill Google AMP before it kills the web (2017) (theregister.co.uk)
148 points by coliveira on Jan 21, 2020 | hide | past | favorite | 20 comments



> By Scott Gilbertson 19 May 2017 at 08:25

Please add in a (2017) to indicate this article is quite dated at this point


Also, see previous discussion[0]

[0] https://news.ycombinator.com/item?id=14384187


Don't worry, AMP is just an interim step on the path to Google's ultimate vision, which is to answer all search queries directly with a fact, passage, or knowledge graph datasheet, using information it extracted from your content and without providing any url at all.



Google wants to get rid of the address bar and have as many queries come through them as possible.


Basically the whole web has no single point of failure, with the exception of DNS, and even that is decentralized. So what do you do with that?-- obviously introduce a single point of failure in the form of a private service.


If / when that service fails, won't people just do whatever they did when they didn't have that service?


Like pasting the domain into googles searchbar, as a lot of my older relatives (50+) did/do?

I'm afraid a lot of people don't even know how to get from an "amp" page to the "original" webpage.


Like doing the search that got them to the amp page in the first place in another search engine.


I swear to never implement AMP pages for any of my employers.


Is there a more recently updated analysis on why AMP is/isn't bad for the internet? Using my Google-fu to look for criticisms of AMP seems to yield little to no results


In an attempt to do my part in killing AMP, I just disabled it on my Wordpress-hosted site. If you've got a Wordpress blog hosted on their servers, you can go to Settings > Performance and disable AMP completely.


Did that myself a while back. Annoyed it was on by default in the first place! Why would they do that?


I just want a way to permanently opt out.



Nice! Excellent link... Making the move to Firefox better. uBlock origin is a must. Anything else you'd recommend?


NoScript breaks some sites but makes many run faster. Everything defaults to blocked, but I've marked some known ad servers and Google/Facebook trackers as specifically blocked so I don't accidentally unblock them.

Also, setting up custom searches is very nice: when editing a bookmark, attach a keyword to it and put "%s" in the URL. If you type the keyword first, the rest of the search string will replace the %s. I use it for the usual Wikipedia search, but also I've set "@r tf2" to take me directly to the subreddit called tf2, and @i immediately throws the query at DDG's image search.


My personal basics are Adnauseaum (uBlock origin based, makes exceptions for non-tracking ads, and clicks all tracking ones to pollute data), Decentraleyes, HTTPS Everywhere, and multi-touch zoom if I'm on a 2-in-1


Firefox on mobile. uBlock Origin on mobile.


* Multi-Account Containers

* Temporary Containers (works with Multi-Account Containers)

* Cookie AutoDelete




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: