Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Just to make sure I'm following this myself: this isn't about disabling AMP, it's about making sure that URLs that you send to other applications or the clipboard from Safari will be the true URLs of the original web page, not AMP URLs. Right? That's the only way I can read "strip AMP links from shared URLs," but a lot of comments here are piling on to AMP itself. Which I understand (I don't like it for a lot of the reasons already brought up here, both in terms of philosophy and usability), but I don't think that's what we're actually talking about.


There's a pile-on because now people are having to solve problems that AMP is creating instead of just killing AMP.


Yes, the natural extension would be doing a similar translation when you copy url from Google search results - replacing the Google.com/...?URL=whatyouwant.example.com with just whatyouwant.example.com (but maybe safari does that already).


Yeah, the article completely misunderstands what this is about, and so do most people in this thread. I expected more from HN.

This is something Chrome has implemented, and they've asked other browser vendors to do too. You want AMP to load the page quickly on your first load, but for sharing, the canonical link is the best to give to people.


It's a single twitter thread, not an article. And how do you think it misunderstands what this is about?


On HN you aren't allowed to discuss the details of AMP. It's AMP 101 all the time.




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

Search: