networkimprov

See also:

https://en.wikipedia.org/wiki/Self-sovereign_identity

https://identity.foundation/

https://human-id.org/ (a non-profit startup)

This is about SNMP, and says nothing about SMTP.

I don't mean to be impolite, but it seems like you haven't read any of the links I posted.

A TMTP server could act as a proxy between a client and service; there are a few use cases for that (mentioned in FAQ, but not in current protocol draft).

I'm not aware of any use cases for store-and-forward federation that aren't better served by a client-server network. And I've been thinking about this around the clock for four years :-)

Zillions of websites have active discussion boards, despite the success of Reddit and FB Groups.

A handful of webmail providers have centralized a large fraction of all email users. They already have the control you're concerned about.

Non-federated email means you have accounts at several sites, and most sites have membership requirements (customers-only, employees-only, etc). A client app keeps track of all your accounts. A webmail intermediary is unnecessary. The mnm demo gives a sketch of this [1] and the FAQ gives more detail [2].

[1] https://mnmnotmail.org/demo.html

[2] https://mnmnotmail.org/faq.html

Most phishing attacks originate on webmail accounts, which implement DMARC.

The incredibly damaging and widespread exploitation of SMTP for cybercrime (via phishing, etc) implies that the correct model for Internet messaging is non-federated, i.e. more like HTTP than SMTP. That's not to say that federation isn't valuable in other applications, e.g. social media.

Federation in SMTP was necessary given the Internet's topology when email was invented. That network is long gone.

See TMTP, from the mnm open source project, which implements both the client & server:

https://mnmnotmail.org/

My understanding is that most phishing attacks are launched from webmail accounts, which implement DMARC.

You're most welcome! Patreon link on website ;-)

Have you looked through the FAQ and protocol draft?

https://mnmnotmail.org/faq.html

https://github.com/networkimprov/mnm/blob/master/Protocol.md

The mnm client app isn't chat-oriented like Slack & Discord, altho it does provide presence status for contacts who've opted into that.

A second root problem is the insanity of public SMTP on today's Internet: allowing anyone, claiming any identity, to send you any content without limits.

I started the "mnm" open source project to enable a new email network, on a new protocol.

More: https://mnmnotmail.org/

Follow: https://twitter.com/mnmnotmail

This is a relatively deep look into the bottomless task of considering a candiate for a role in an organization. It bears multiple readings.

It suggests that you may not learn much from interviews with the candidate, and may learn much more from face to face interviews with their references.

It encourages the reader to seek both the genius and dysfunction of every person (candidates and references), for each context they've worked in. (Altho I'd refer to these as their inherent irrationality and ingenuity; dysfunction and genius are the extremes.)

Yes the client stores your mail, and the messaging service (aka server) simply relays it between clients.

Thanks for the encouragement!

Follow mnm: https://twitter.com/mnmnotmail :-)

For personal backup/archiving, there's replication to multiple clients, also described on the website.

Someone will create a web service that implements a TMTP client to replicate your account in the cloud. That's fine for many consumers, but must not be the default.

Dear Internet,

For 25 years you've pleaded for an SMTP replacement. But all you got was SaaS, sans interop.

Now at long last, here it is. (We're so sorry it's taken so long, but we're only human!)

TMTP is a sane network protocol for email, to end attacks and promote productivity. You can download client and server, written in Go, from the mnm open source project:

https://mnmnotmail.org

Why now? The cybercrime crisis, a huge portion of which is facilitated by social engineering attacks via email.

Website: https://mnmnotmail.org

The FAQ describes a likely path to mass adoption. Intranet and B2B scenarios are the first two phases.

Consumer adoption happens later, and doesn't depend on support by webmail providers.

Rationale: email has become a universal cybercrime portal, as it enables social engineering attacks.

Stephen is really fun to listen to. This is from the Event Horizon podcast:

https://www.youtube.com/watch?v=LpK1d8mTEhI

JMAP is an extension of the email protocol stack; it only replaces IMAP.

TMTP is an alternative to the entire email protocol stack. It will be standardized after it's been proven in a range of real-world scenarios.

The mnm client & server, which implement TMTP, work well today, and have nearly all the features most users need. See docs menu in the online demo.

https://mnmnotmail.org/demo.html

Re "serious money", could you elaborate?

There's TMTP, "a sane network protocol for email, to end attacks and promote productivity."

https://mnmnotmail.org/

https://twitter.com/mnmnotmail

Short answer: evolution.

"Legitimate" because it is open protocol (TMTP), decentralized, store-and-forward, n-identity, and open source.

Email is a network, not a product or service. TMTP is the basis for a new network.

"Legitimate" because it is open protocol (TMTP), decentralized, store-and-forward, n-identity, and open source.

Email is a network, not a product or service. TMTP is the basis for a new network.

See also https://mnmnotmail.org/

"Legitimate" because it is open protocol (TMTP), decentralized, store-and-forward, n-identity, and open source.

Email is a network, not a product or service. TMTP is the basis for a new network.

Both hey.com[1] (from the Basecamp folks) and TMTP from the mnm project[2] (proposed successor to SMTP) disallow background downloading of remote URLs.

TMTP also specifies Markdown formatting (not HTML), fwiw.

[1] https://hey.com

[2] https://mnmnotmail.org

This idea assumes that email is an irreplaceable source of personal or organizational identity.

I believe that assumption is a misapplication of email. Universal identity is a complex issue, and is not addressed well by email addresses. Portability is one example.

Also the cybercrime crisis, which is substantially enabled by email phishing, may well drive email off the public Internet. We no longer need an Internet messaging system which makes you accessible to everyone else on the net, without consent or limits.

For a next-gen take on Internet messaging, see the mnm project, which proposes and implements TMTP. That system supports separate site-specific identities for every user (and multiple aliases per identity), which is a better match to the real world.

https://mnmnotmail.org/

The essential feature is subjective experience of sensations, referred to as qualia. I've seen no debate about that.

https://en.wikipedia.org/wiki/Qualia

Cybercrime vs cybersecurity is an arms race, and arms race scenarios are not necessarily resolvable.

I can read the WaPo article in a private/incognito browser window.

The IETF in particular has had a huge role in facilitating phishing via SMTP.

This overlooks the cybercrime crisis, which in 2020 did ~4x more financial damage than weather & climate disasters. And it's expected to get much worse this year.

https://twitter.com/mnmnotmail/status/1372201054213787660

Silicon Valley probably has a role to play in suppressing cybercrime.

References:

Cybercrime, $945B: https://www.washingtonpost.com/politics/2020/12/07/cybersecu...

Climate, $258B: https://yaleclimateconnections.org/2021/01/world-hammered-by...