[HN Gopher] We disabled Google AMP at Tribune Publishing
___________________________________________________________________
We disabled Google AMP at Tribune Publishing
Author : danso
Score : 74 points
Date : 2022-08-26 21:33 UTC (1 hours ago)
(HTM) web link (kurtgessler.medium.com)
(TXT) w3m dump (kurtgessler.medium.com)
| dspillett wrote:
| ... yet they still use medium, with its collection of problems.
|
| The article doesn't state how the graphs are produced. I hope
| they are stacked rather than plain lines, otherwise the comment
| that people transitioned to normal mobile access is wrong and
| those visits just vanished.
| [deleted]
| ProAm wrote:
| The irony of disabling AMP but posting about it on Medium.
| s17n wrote:
| Tribune Publishing's websites are hot garbage and a perfect
| example of why we need AMP in the first place.
| [deleted]
| gerdesj wrote:
| Whatevs with respect to Tribune (whom I've never heard of). You
| may not like their message but AMP is the messenger here and it
| is Minerva's kid brother that flunked school and took up
| delivering class A drugs on their BMX.
|
| This article is about dumping AMP - discuss! I found the medium
| article extremely well written with loads of stats to back up
| assertions. It is also mercifully short. That is exactly what I
| want to see.
|
| For me AMP is an example of "insidious" - it looks shiny ("my
| precious") but it will suck the life out of you eventually.
| AMP, fundamentally puts your content distribution in the hands
| of a third party (G) that can change it at will and that breaks
| the promise of the web and ensures that you will have your
| testes tickled at first and then twisted off.
|
| AMP is not simply a CDN - it doesn't simply regurgitate your
| stuff faster. It changes it and does things to it and also
| gathers as much data as it wishes, from your customers. My
| Precious ...
|
| Oh look: I've managed to conflate some fictional seriously
| damaged goods from Star Wars and the Lord of the Rings with
| what Google will do to you.
|
| Silly me.
| jacquesm wrote:
| No, that's not why we need AMP. They should just fix the
| garbage.
| callahad wrote:
| "Just fix the garbage" doesn't work; it's there because
| _someone_ in favor of the garbage wanted it there, and the
| folks opposed to the garbage didn 't have the authority or
| influence to stop it.
|
| ...and that's the one thing AMP did right: it empowered
| developers to push back against the garbage by giving them a
| big ol' "Google says no" sign to wave around. Which is _all
| kinds of problematic_ in terms of existential threats to the
| Open Web, but it _did_ clean up that specific type of
| garbage.
|
| How do we give anti-garbage folks that same power in a post-
| AMP world, without resorting to centralized authority?
| karamanolev wrote:
| Be that as it may, we need to get rid of AMP altogether. It's a
| much bigger evil than a bad website here or there. After AMP is
| gone, we can worry about one (or N) bad websites instead of a
| corp controlling all of them.
| aliqot wrote:
| Yep, perfection it isn't, but this is a step in the right
| direction. Hopefully, the initiative that brought this
| forward also slowly rectifies the other issues with the site.
| khatkhati wrote:
| I don't know what you're talking about, they are nice, clean
| and snappy with JavaScript turned off :)))))
| wilde wrote:
| Good riddance. AMP pages loaded noticeably more slowly for me and
| were typically broken when they finally painted.
| [deleted]
| nightpool wrote:
| The whole point of the Core Web Vitals project was to provide a
| neutral measure of "quality" that could replace the search
| rankings boost that AMP got, so I'm not surprised. I just wish
| they did something about giant interstitials as well
___________________________________________________________________
(page generated 2022-08-26 23:00 UTC)