pull down to refresh

The guy in the article mentions a few standards that make email far less scammy / phish-y, how does your idea differ from those? Cause I do agree with the OP article, that the standards and tech are fine, it's really a business / cartel style thing stopping perfectly serviceable open standards.
If your recipients are largely captured by the email giants, which is kind of the "held constant" assumption as time goes on, it's really a chicken and egg question -- does one focus on a new standard or on changing behaviour of the majority of recipients... Because I also really hate the modern "we sent an email conf" flow where random companies who I know aren't fucking it up get bounced by gmail and I have to wait around for a confirmation email or ask them to re-send... Most people don't think about that human/business aspect and just want the email conf "to just work (in less than 1 min)"
The guy in the article mentions a few standards that make email far less scammy / phish-y, ...
DKIM, SPF, and DMARC only reduce spam which is sent from misbehaving email servers/senders. But those standard don't stop spammers who send spam from email services like Gmail and iCloud, and from corporate email accounts whose credentials the spammers stole. All those email servers have perfect DKIM/SPF/DMARC records. And yet, I see a lot of spam coming from Gmail, iCloud, and corporate email servers.
it's really a business / cartel style thing stopping perfectly serviceable open standards.
Standards rise and fall; corporations and nation-states can't stop people from switching from one protocol to another. The reason email hasn't been replaced is because a sufficiently better replacement has not been made yet. And if that replacement was good enough, corporations and nation-states would switch too.
how does your idea differ from those?
See my other comment for an incomplete description. In short, my idea was to make a completely different protocol to replace email.
reply