3 ms·
It's mainly because XMPP is overcomplicated, but also they're for different use cases. XMPP: - is designed for chatting and P2P and VoIP over persistent HTT
by 0xbadcafebee 4y ago
It's mainly because XMPP is overcomplicated, but also they're for different use cases.
XMPP:
- is designed for chatting and P2P and VoIP over persistent HTTP connections
- requires everyone to be online
- servers have to implement 50 different specs
- works at the frontend and backend
SMTP:
- is designed to send one large message in bulk over a regular short-lived TCP session
- is a store-and-forward messaging system, highly resilient to slow or inconsistent networks and server issues
- is simple and the ecosystem is layered, so the core server doesn't have to implement a dozen specs
- is practically backend-only
The difference between "Can you hear me now?", and putting a letter in the mail.
- hkt 4y agoThis isn't really accurate: xmpp isn't p2p, it is hub and spoke. All comms (except optionally some VoIP and file transfers) go through the server. XMPP can also do store and forward pretty easily with common server addons. I'd not really describe it as fragile or bloated either, having used it for twenty years or so with no real problems except the now-solved absence of e2e encryption (OTR, OMEMO). Still, clients could be better.
- 0xbadcafebee 4y agoWhat an XMPP server supports: - XML - XHTML - vCard - Bookmarks - Message Archive - P2P - VoIP - Multi-user Chat - File Transfer - Data Forms - Service Discovery - Pub-Sub & Personal Eventing - Bidirectional Synchronous HTTP Streams - WebSockets - Push Notification - Protocol Gateways - TLS - OTR - PGP What an SMTP server supports: - SMTP - TLS 175 XMPP specifications (https://xmpp.org/extensions/ https://xmpp.org/extensions/) 24 SMTP specifications (https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol#Related_Requests_For_Comments https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol#...)