3 ms·

You're making some fundamental assumptions about federation that I think are completely wrong. Are you telling me that you never need to communicate with anyone

You're making some fundamental assumptions about federation that I think are completely wrong. Are you telling me that you never need to communicate with anyone outside of your organization? How do you intend to receive invoices? How will you communicate with outside vendors? Sorry, but you need some text-based way of communicating with people and email is the best way, that's why it's survived so long despite being problematic. If you have internal, asynchronous chat, why would you need internal email? Sorry my dude, but business runs on email. Saying lets get rid of it is as naïve as saying lets get rid of Excel. It's just not going to happen.

networkimprov 6y ago
There are two ways to communicate with ppl outside your org without federation (this is covered on the website): 1) Set up a second TMTP service where customers and/or suppliers can create accounts, along with employees who need to interact with them. 2) Have some employees join a third-party service which is open to all involved in your field. There is a risk of phishing in this case, but: . a) anyone you haven't previously contacted is limited to short, plain-text communications to you (see Ping in protocol), and . b) such third-party services would typically charge a fee to members and impose a small cost per-ping, and . c) you know that you're dealing with unknown entities with possibly malicious intent. TMTP clients support active logins to accounts on any number of TMTP servers, just as browsers support multiple active connections to websites.