This seems like a bad idea and goes against years and years of open systems design.
This seems like a bad idea and goes against years and years of open systems design.
Also addressed here: https://news.ycombinator.com/item?id=25804869#25807379
(I'm the author.)
Or watch on Twitter: https://twitter.com/mnmnotmail
It should have sender authentication. E2E encryption that's easy and works by default. Those would be more than enough killer features, SMTP is just too broken and all the workarounds we have in place like DKIM, SPF, Spam ratings etc etc don't make up for it. We still have spam, important mails still end up in our junk boxes, and nobody trusts it enough anymore to put important content in emails. The war has long been lost.
The difference seems to be that ProtonMail don’t allow you to use normal imap and your own client with pgp, but force you to use their client. This is probably a trade-off made to protect users against them selves in one way (disabling encryption for grandpa) and hiding the non tech-savvy from all the technical details.
Again, many assumptions here.
So, to me, mentioning proton here doesn’t make sense as the underlying tech: smtp & pgp have existed and been industry standard for a long time. So there is not issue of adoption.
"War"
Few, outside small, likely familiar tech circles, use these terms when discussing email.
Not being SMTP usually means being another messaging island or other, which has only strengthened email.
Lists have huge value today, still!
Now, there is one exception: Marketing
The reason? Everyone else is busy getting work done.
Whatever may transcend email needs that quality, or it will, in fact be, yet another messaging island.
Email must be: * Secure and encrypted; * Have proven identity; * Have easy to fabricate and predictable rendering;
I feel like the ability to have forms and charts is very nice, but adds a lot of complexity, especially from a security point of view. I'd be looking at this kind of "application level" functionally being a layer added optionally on top, not being in the core protocol.
https://www.cyberscoop.com/jabber-xmpp-cybercrime-russia-enc...
There was a major deep web counterfeiter about a decade ago that remained active on Jabber even as a federal fugitive, not sure what ended up happening to him.
Federated/decentralized, secure, non-real-time messaging is the problem space. If it can make some overwhelmingly common use cases of current e-mail that much easier, then so be it.
If history has any say on this, communication solution based on proprietary technology will meet their death sooner rather than later. How many network protocols have been invented before and after TCP/IP? I know we are talking about messaging now, but messaging is just another overlay network over TCP/IP.
I'd envision in the future that the open messaging systems will be more pervasive. It will be based on local-first software and probably based on the automerge capabilities. The automerge community is focusing on collaborative editing at the moment but could someone please work on automerge solution for messaging system? This can be an excellent new paradigm for open world of messaging. I am seriously tired of people asking me to install the proprietary software of WhatsApp, Line, Wechat, etc.