So according to Eugen, he's been using XMPP during a time when people let their desktop PCs run all the time, which is ideal for XMPP's requirement to maintain an active connection from sender to recipient in order to actually deliver messages.
But when the world transitioned from desktop PCs to mobile phones, XMPP's requirement to stay always on was just not practical, and the world moved on from XMPP and onto other platforms.
The only way people used XMPP was through Facebook and Google Talk, but the mainstream really didn't have a strong appreciation for XMPP.
According to Eugen, Email is still going strong because everyone knows how to work with it
Effectively, embracing, extending, extinguishing is just not a thing for email yet.
> maintain an active connection from sender to recipient in order
Nope, XMPP is classically not P2P. Ideally, you maintain a connection from sender to sender's server, but if it is interrupted, it works just fine when it comes back. And if you absolutely need to kill your client https://dontkillmyapp.com/ and insist on using privacy-unfriendly push notifications, there is spec for that: XEP-0357: Push Notifications. This never-ending FUD is tiring…
@manlycoffee@mike@Gargron XMPP does not have a requirement to "always stay on". The server can send a push notifications to mobile clients to wake them up and retrieve messages like any other chat app.
@manlycoffee That doesn't make a lot of sense. Google, or anyone else really, could have implemented push notifications for their app also in the early days.
If the client and the IM service come from the same vendor, you don't even need to standardize on some protocol extension.
Add comment