Heho,

> Brandon Long via mailop
> https://developers.google.com/gmail/ampemail is the Google developer 
> information about dynamic email, that link was about controlling the 
> content with Google Workspace.
Thanks for sharing, this has some rather interesting examples. Do I need to be 
specially vetted to send AMP email, or could I--as long as it is compliant to 
the standard--send one myself, i.e., without being a registered newsletter 
sender? The AMP page is somewhat unclear there.

> Brandon Long via mailop
> The standardization is via AMP, docs at https://amp.dev/about/email/ 
> and a pretty short list of other providers who support it.
I acknowledge that mail's UX is currently 'fresh and outstanding' and something 
will have to change. Still, change is naturally driven by those who do, 
which--in this case--is the group of organizations around AMP. However, I'd 
argue that changes will be aligned with the needs of these organizations in 
terms of providing consistent services to their customer base under their 
business model [1], which naturally inflicts on how these systems are being 
designed. This also inflicts on the governance of venues for organizing and 
coordinating such changes, as for example AMP, implementing a model that allows 
decision making to follow operational needs [2].  And, to be clear, I am not 
claiming that this is a google-specific thing, or try to pick on google, but 
instead argue that any rational actor with that scale of operations will 
ultimately operate in this way to match its objectives.

> Brandon Long via mailop
> The death of email will come from outside the eco-system, not from 
> individual attempts to extend it.
I wouldn't necessarily call AMP an individual attempt, given the market share 
of some of the involved parties.

Also, I was referring to the death of XMPP. If I remember correctly, XMPP's 
rise and fall actually started with major players [3,4] committing to XMPP 
federation.
However, over time, and with needs, roadmaps, and available features in clients 
diverging more and more, federation was discontinued by Facebook and Google [5].
At this point, the role of others being less sharing and more consuming--Page 
explicitly calling out Microsoft here [6]--certainly should also be mentioned. 
What ultimately broke the neck of XMPP was then its ill suitedness to the 
evolving User Experience on smartphones.
With its complicated protocol, and federation needs--the classical finding 
others problem--it was simply no match for centralized services using simple 
but usable identifiers (phone numbers), even if they may have been using XMPP 
'under the hood'.
That then is what gave us the current zoo of messengers we all love and like 
(if someone wants to further discuss this point, please feel free to write me 
on What'sApp, Signal, Telegram, Threema, Facebook Messenger, Skype, 
Skype4Bussiness/Lync, Google Meet, reddit, or via netcat on tcp/2342).

So, in the end, the dynamics around new features adopted by a few players 
representing a major subset of the ecosystem can have a long-lasting impact 
that may ultimately interact with, e.g., the deliverability discussions we 
regularly have. (Most recently, tightened SPF requirements by Google, and I am 
not claiming that _that_ move was necessarily a bad one; But one with 
consequences to consider that are not strictly technical in nature, but cross 
influence technology, i.e., in this case, mail.)

With best regards,
Tobias

[1] 
https://doing-stupid-things.as59645.net/burning/world/resillience/2022/06/30/propositions-part-4.html
[2] Page 78, Sec. VII.E.6, Point 206 ff 
https://www.texasattorneygeneral.gov/sites/default/files/images/admin/2020/Press/20201216%20COMPLAINT_REDACTED.pdf
  
[3] https://googletalk.blogspot.com/2006/01/xmpp-federation.html
[4] https://www.facebook.com/notes/10160197317616729/ 
[5] 
https://blogs.fsfe.org/hugo/2013/05/google-talk-discontinued-will-google-keep-its-promise-and-give-xmpp-users-a-way-out/
 
[6] 
https://www.theverge.com/2013/5/15/4334242/larry-page-to-tech-world-being-negative-is-not-how-we-make-progress

_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop

Reply via email to