AMP email will silently be less used.

Email encryption, even if gmail is anouncing so, is not a win yet.

Email as the Interface can be a great way indeed. See https://shaarli.lyokolux.space/shaare/RT9psQ

Notion integrated emails in 2024. See https://www.notion.com/product/mail. All services want to integrate emails. Other tools are doing so.

1. Please make each program do one thing well
2. It's only an add-on
3. it more complexity than first though: dates of brith, email address patterns, time zones, diferent names of humans...
4. A waste of developer time

Advantages of email-first application:

• widespread corporate adoption
• asynchronous
• push system
• one less application: lots of business folks spend most of their days in email clients already.
• less features: email forces you to be very deliberate about design user interactions and simplifying processes
• easier to delight: getting a weekly email is more fun than logging into the service
• less competition
• scaling is crazy cheap
• interesting technical challenges

I fundamentally disagree with you. If a piece of technology allows for such mistakes, then it is at fault, not people

It has to be accessible but the software limiting the user
"So far, we’ve been lucky. When technologies try to protect you from yourself too much, they tend to die out in a few years"

In order to avoid user mistakes, what should the email client do?

Email is powerful beyond any other medium precisely because it does not try to wrest control from its users.

Trier les mails d'une boite mails selon les années.

Independant emails are not delivered to the major mail hosting providers such as gmail...

Right now institutions don't talk about regulating email simply because they take it for granted, but it's not.

Email has superpowers, one of which is unique subject lines. What I should have done is broken up the email into three separate ones, with different subject lines, each tailored to my desired outcomes.

1. Subject: Come visit my new place. Why I moved.
2. Subject: My availability reduced until February 10
3. Subject: New Address – Keep for reference and update your Contact for me.

This allows each recipient to ignore or archive each topic if not relevant or interesting to them, or to keep the actionable ones. It also not-so-subtly puts my desired outcome into their subconscious. It requires almost no additional work on my part to send three emails versus sending only one.

It is better to have small emails than bigger, so one email for each topic.

Emails are not good enough: they can change.

La plateforme officielle de signalement de spam

The problems lasted weeks and it is now solved in one day after being public...

It's amazing how quickly Microsoft can fix things if issues are made public: Yesterday we've reached out to Microsoft Germany along with the press release asking them - again - to fix the issue of tutanota.com emails going to Spam in Outlook. The issue was then fixed within one day (after we had been in direct contact for three weeks without any success)!

Why emails is a mess? Because there are a lot of email service providers that does not follow the standard...

A project to list all email issues.

and how to handle it properly?
It follows the SAML:

the identity provider gives some claims1. One that it provides is the NameID, inside of Subject.

What Atlassian/Jira is doing right is that they're actually using a static identifier to identify you, rather than your email address. This allows an incredibly smooth experience when any aspects of your attributes (such as email or name) change.