(these all have their builders as active users AFAIK)
(these all have their builders as active users AFAIK)
Let me add another one or two. How about SMTP and BGP?
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:
Either of those outcomes would result in a poorer world.
The fact that facebook, telegram, whatsapp, etc are all centralized doesn't seem to stop criminals using those platforms.
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].
Federation in email is used constantly and ubiquitously. Why would anyone want to turn it off?
I see any value in TMTP in the improvements as a protocol and I think it will be only be hurt by having no provision for federation in the protocol.
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 :-)
I agree with your point but has this not happened with Gmail, Microsoft and Yahoo! for email anyway?
And it’s certainly a much better situation than other chat systems, where your identity is fundamentally tied to your account on that particular service. You can’t move to signal without moving everyone else to signal at the same time. I only need one email provider and one email app. But for messaging, everyone ends up needing signal, and WhatsApp, and Facebook to talk to each other. Imagine if you needed half a dozen email apps and accounts for each one to use email. “Oh, you’re emailing a company who uses Microsoft? Better open the Microsoft email program and remember your Microsoft login”.
No thanks!
SMTP has means to identify servers and domain ownership, web browsers have infrastructure to identify and verify arbitrary websites, and S/MIME exists. Most MUAs ignore basically all of this and instead trust whatever address is in a message's From header.