Mutt, for instance, discards "html" and renders just the "plaintext" version. AMP emails would just be another part of the same email. Nothing would stop working.
Mutt, for instance, discards "html" and renders just the "plaintext" version. AMP emails would just be another part of the same email. Nothing would stop working.
Is people or the communication what stops working, and then the involved system, not a piece of software by itself.
"Please view the HTML version of the e-mail"
Which is annoying, because I have a preference set for plain text if it is included. If a sender doesn't have a plaintext alternative, they should not include any of this garbage plaintext, that just confuses the preference logic in MUA.
Anyway, it shows that we may start seeing:
<p>You need AMP supporting MUA.</p>
as a html "alternative".
AMP for email has support by Outlook, Yahoo, and Mail.ru, so it very much isn't under Google's control.
https://github.com/ampproject/meta-tsc
I would hardly consider Yahoo to be a leader in anything at this point, not sure about mail.ru. From an outsider's perspective AMP looks Google controlled.
It looks like from your comment history you are part of Google's AMP team. It would be nice to disclose that.
The TSC requires majority consensus. Google does not have a majority.
I remember you talking about how transparent the process is, but, alas, you never described it. And to quote another member of the discussions back then, anyone raising concerns:
> were closed or locked, and the head of AMP blocked us.
You being the head of AMP, of course.
mail.ru is owned by the same mafia group, that controls majority of Russian internet. They are either very stupid or want the same thing as Google (to destroy email as we know it). It is probably both.
Participation of mail.ru implies, that Russian mail providers won't ban Google in retaliation for this crap (neither on SMTP level nor via country-wide firewall).
Suggesting any part of AMP is open still feels very disingenuous when you recognize the monopoly position of the company spearheading it.
...which means nearly nothing.
Open in what sense? For example, there's no open standard (to the best of my knowledge) for the HTML used in emails right now and different email clients render HTML in emails differently.
On the other hand, the protocol itself is standardized, but AMP is not working on protocol level.
Not often enough. These days, people who are rude enough to send HTML emails are also rude enough not to include a plain-text version of the email.
I don't expect AMP to be any different.