Follow: https://twitter.com/mnmnotmail
Protocol: https://github.com/networkimprov/mnm/blob/master/Protocol.md
1,070 karma · joined July 25, 2018
Architect of TMTP protocol, to let Internet sites message their members/customers directly (instead of email).
mnmnotmail.org || https://twitter.com/mnmnotmail
.
Follow: https://twitter.com/mnmnotmail
Protocol: https://github.com/networkimprov/mnm/blob/master/Protocol.md
Cybercrime: https://www.washingtonpost.com/politics/2020/12/07/cybersecu...
Climate: https://yaleclimateconnections.org/2021/01/world-hammered-by...
The demo[1] illustrates how a collection of TMTP services enable replacement of email, and the FAQ[2] describes the process by which TMTP would grow to supplant SMTP.
Law enforcement cannot cross international borders. Phishing email sails thru.
The protocol uses JSON, not node.js. The mnm client & server are written in Go.
If you wish to be insulting, just have at it; no need to extend "all due respect".
See also...
for i := 0; i < 10 i++ {
i := i // new variable i for every iteration
go func() { f(i) }()
} for i := 0; i < 10; i++ {
go func() {
f(i) // sees whatever value i has when f() is called, usually 10
}()
}home page: https://mnmnotmail.org/
on Twitter: https://twitter.com/mnmnotmail
client demo: https://mnmnotmail.org/demo.html
TMTP protocol: https://github.com/networkimprov/mnm/blob/master/Protocol.md
I'm not aware of any alternative email protocol that's implemented, except TMTP. I don't believe closed-source, walled-garden services, which don't allow third-party clients or servers, really count as legitimate alternatives.
There's Matrix, but that's a synchronization protocol for chatrooms, not a store-and-forward messaging scheme.
EDIT: you might never silence SMTP altogether, but a suitable protocol could supplant it for the great majority of its use cases.
Or to replace email for internal use altogether. TMTP is a new protocol with that goal:
I'm working on a live demo that runs from the website. Follow me on twitter to hear when it's available.
It uses websockets & JSON to connect the SPA UI (in Vue.js) to the app (in Go). That works well, and I can't imagine any advantages to generating HTML with Go, except perhaps less JS code :-)
If I may say so, the mnm project also deserves coverage like this. It prevents spy-pixels, and phishing, and provides unsubscribe (from threads, or senders, or whole sites). And a heck of a lot more :-)
mnm, an open source project to replace email & SMTP:
You don't have to keep the bike that still under you on the road, and that wastes energy.
Can I bribe a BBC editor to get them to write about mnm & TMTP? :-)
It also prevents spy-pixels, and phishing, and provides unsubscribe (from threads, or senders, or whole sites).
mnm, an open source project to replace email & SMTP:
Why Cats Paint - A theory of feline aesthetics
The TMTP server supports replication to multiple clients per account, which enables backup. I note in the FAQ that servers may perform archiving (which is not the same as retaining all the traffic).
Any network information system could be compromised. Zillions of them are trusted. If you're alluding to E2EE, see the FAQ.
FAQ: https://mnmnotmail.org/faq.html
Twitter: https://twitter.com/mnmnotmail
An FAQ addressing the Q's posted here will be live on the site late on Jan 18th.
Or watch on Twitter: https://twitter.com/mnmnotmail
See also https://news.ycombinator.com/item?id=25804869#25807379
Also on the drawing board is a live demo of the client in a webpage, with canned data.
All this -- TMTP, client, server, website -- are a work in progress (and a solo effort). This HN item is the first time any of it has received significant public attention. No one should be disappointed that it doesn't look polished!
I'm not concerned by the pessimistic comments, considering that it got 300+ up-votes :-) A lot of comments are from folks who didn't get a clear picture.
(I'm the author.)
Follow mnm: https://twitter.com/mnmnotmail
I've been asked to create a doc describing the architecture and infrastructure of TMTP. That should clear up the Q's you and others have raised.
(I am the author.)
John Doe <not.john.doe@example.com>