> I think the only thing that I would miss is the apps can dismiss notifications that are no longer relevant. That's something I was thinking about a lot a few

> I think the only thing that I would miss is the apps can dismiss notifications that are no longer relevant. That's something I was thinking about a lot a few years ago. I think this could work with a tiny email extension: If the email would include 2 extra header called e.g. "X-Revisable-by-public-key: <public key here>" and "X-Revision-signature: <signed sha512/256 hash of message>"; Then, a future message with the same message ID (or perhaps X-Revises-Message-ID:...) properly signed, would replace a previous message in the notification UI - perhaps giving an indication/view of the previous revisions. A mail client that does not support this header would simply not dismiss the no-longer relevant notifications but would still be fully compatible/capable, and the "message read" among different clients would still operate properly. The main thing that makes me cringe about using email for everything, e.g. things like delta.chat, is that I accidentally do "view source" on one-body-line messages: The modern overhead hurts my engineering sensibilities. Seems like Google easily adds 3K of envelope and metadata to a 120 character email. Acceptable as transport for a 3MB email with attachment; Unacceptable for a 6-char "ok lol" delta.chat message.