3 ms·
This is the first convincing argument I've read against AMP email. On the other hand, if someone sends you a link to a web page, sure the link didn't change, b
by skybrian 9y ago
This is the first convincing argument I've read against AMP email.
On the other hand, if someone sends you a link to a web page, sure the link didn't change, but that's not very useful, since anything can happen to the web page that the link points to.
So it might just be about not confusing the user about what's immutable? Which is itself pretty important.
- brongondwana 9y agoSure - and as I said in the blog post - this is already an issue with embedded images - which can be made to look pretty good and, if remote, can be changed later. Spam scanners penalise messages that are just a remote image for good reason.
- SpikeDad 9y agoThen you should use Apple Mail for macOS which has the option of including a PDF of the webpage rather than the obviously fragile URL.
- TehCorwiz 9y agoHey, Thunderbird team, this is a feature I'd want.
- toomuchtodo 9y agoThunderbird team: Generate a request to the URL, and include the attachment as a WARC file, not a PDF. The client or any other system can then render that content however they desire at a later date.
- notatoad 9y agoIt's the first convincing argument i've read against AMP email, assuming it's a valid argument. It doesn't look like amp4email is any less immutable than standard email is - it fetches some resources from external servers, but mandates that those resources must be static and cacheable. Gmail's current behaviour is to download and store all images in emails when they are first opened, which makes the images in emails as immutable as fastmail wants them to be, and i don't see why they would treat any other resources delivered in amp emails differently to images. To me, this seems perfectly reasonable - the responsibility to store email contents in the state they were first recieved should be on the recipient's client, not the sender's server. i love this blog post, because it's great to write down in clear terms why email being a read-only log is so important. but it looks like in the case of amp it might be a bit of a straw man.
- brongondwana 9y agoThat is absolutely a good point. I should have shown my working a bit more. static is boring, because every email can still have a custom endpoint. proxyable is more interesting. You say "cacheable" - I don't see that in the AMP project notes: https://github.com/ampproject/amphtml/issues/13457 https://github.com/ampproject/amphtml/issues/13457 @ras9929 yes amp-list allows you to generate dynamic content populated from a json endpoint. The demo shown today did exactly what you are suggesting. See https://www.youtube.com/watch?v=p8Eo4gAoDBA&feature=youtu.be https://www.youtube.com/watch?v=p8Eo4gAoDBA&feature=youtu.be The only reason to host images remotely rather than including them as cid: links inside a multipart/related is size and encoding overhead. Likewise, a new dynamic multimedia format could be entirely self-contained within the email if you wanted to design it that way. Instead what we have is something which is very tightly coupled to short-lived online services. It's a really poor archival format, but it has just enough sweet bits that people will want to use it for things that it shouldn't be used for. It's really short-term design.