AMP for email is bad
tutanota.com
AMP for email is bad
1–10 of 161 posts
Re: AMP for email is bad
#2Re: AMP for email is bad
#3Decrying that without presenting an alternative sustainable monetization model for the web is just pointless yelling.
Re: AMP for email is bad
#4Retaining a familiar interface across devices leads to faster site usage than any speed gains that might be happening because of amp. Measuring the speed of a website in kb/s alone isn't a good enough metric, and the standardisation attempts of amp are ugly imo.
Re: AMP for email is bad
#5And the author completely disregards the elephant in the room. Why do websites slow themselves down with trackers, etc.? It pays to do so. Decrying that without presenting an alternative sustainable monetization model for the web is just pointless yelling.
Nobody needs to provide an alternative sustainable business model to fuel my desire for sports cars and travel I just need to live with what I can make from legitimate work.
Most of the web is either, cheap to run, paid for by other commercial activity, or crap and if it went away tomorrow because people could not pay for it by shoving their crap in your face nobody would care.
Re: AMP for email is bad
#6Starting with google: AMP does not actually make loading any faster. Google just uses it's search monopoly to make it seem so. When you use google search with javascript enabled AMP results are both prioritized in the listing and pre-loaded in the background. This makes up the entire increase in load time you perceive. AMP pages not pre-loaded by google are just as slow to load.
At Cloudflare there are other problems. If you're a CF customer and have the option enabled, your AMP page hosted on CF servers will do some nasty stuff. Specifically outgoing links to third party domains will be mirrored onto cloudflare's servers and re-hosted. Presented to anyone clicking off your CF AMP page as the actual site but not. Instead CF gets the hits and you never see it. I've seen the CF bots doing this to my domain. But CF never responds to emails from anyone that isn't a customer.
As for AMP for email I don't know the specific downsides besides the obvious corporate centralization and control this gives. But it certainly doesn't have any purpose. And I say this as a guy that only reads email as text and never renders HTML.
Re: AMP for email is bad
#7Maybe one should first ask: Is AMP currently good for anyone but GOOG?
I am seeing far fewer AMP sites today than before though - Google promised higher search results rankings in exchange for a modest amount of work to make websites AMP-compliant - but I guess media publishers see the end-result being more work for less reward, especially if they can’t use their user-tracking scripts.
What’s the advantage of doubling pageviews from higher ranking when it means you get less than half the advertising revenue?
Re: AMP for email is bad
#8AMP is bad for everything. To be clear, this starts by it not being good for anything. Like on the web the form of AMP used by Google and Cloudflare. Starting with google: AMP does not actually make loading any faster. Google just uses it's search monopoly to make it seem so. When you use google search with javascript enabled AMP results are both prioritized in the listing and pre-loaded in the background. This makes…
Or Bing search or Baidu search or Yahoo! Japan search and so on. The whole point of AMP is that it can be safely preloaded and prerendered, making it faster than any other web page you can create for people coming from a link aggregator. One of the big advantages it has over Facebook Instant Articles or Apple News is that a publisher has to create an AMP page once and then gets to integrate with the multiple link aggregators that support AMP for free. If I want to create my own link aggregator, I don't need a FAANG's clout to get publishers to integrate with me for instant-loading pages — I can use their existing AMP pages.
Re: AMP for email is bad
#9AMP is bad for everything. To be clear, this starts by it not being good for anything. Like on the web the form of AMP used by Google and Cloudflare. Starting with google: AMP does not actually make loading any faster. Google just uses it's search monopoly to make it seem so. When you use google search with javascript enabled AMP results are both prioritized in the listing and pre-loaded in the background. This makes…
> When you use google search with javascript enabled AMP results are both prioritized in the listing and pre-loaded in the background. Or Bing search or Baidu search or Yahoo! Japan search and so on. The whole point of AMP is that it can be safely preloaded and prerendered, making it faster than any other web page you can create for people coming from a link aggregator. One of the big advantages it has over Facebook…
Re: AMP for email is bad
#10Earlier quoted context omitted.
> When you use google search with javascript enabled AMP results are both prioritized in the listing and pre-loaded in the background. Or Bing search or Baidu search or Yahoo! Japan search and so on. The whole point of AMP is that it can be safely preloaded and prerendered, making it faster than any other web page you can create for people coming from a link aggregator. One of the big advantages it has over Facebook…
You could do that with regular HTML. Google crawling everything would easily let them know if a page is light and easy to preload, giving and incentive to web dev to make it so, instead of creating a lock in solution.
You ignored the safely qualifier. You would deanonymize a user to the publisher and the third party trackers on their page even if the user never clicks through to visit the page.