Did you know that #Zoom uses #XMPP for their chat? Isn't it ironic that while large parts of the software freedom movement consider XMPP as outdated and refuse to use it, companies building commercially successful proprietary and centralized solutions on top of it... 🤔 #OpenStandards #FreeSoftware

@bjoern I think no one doubts qualities of XMPP as a base for closed solutions, but unfortunately it utterly failed as a federated service.


@sesivany @bjoern Failed?

More like killed.

> While during their growth periods both Google Talk and Facebook Chat adopted XMPP technology. After some time, both removed first some features from it — most notably, of course, the federation ability.


@ashwinvis @bjoern Google kept the federation for years and the main reason why it left XMPP was that it was too slow to adopt new features. Their extension for audio/video call Jingle was not accepted into the standard even after 10 years. That's just painfully slow in an area of such rapid development as instant messaging.

@sesivany The first version of Jingle for A/V calls was accepted as an experimental XMPP standard in Dec 2005, about 4 months after the initial release of Google Talk. It's considered a stable draft since 2009. libTelepathy (Empathy, KDE) and Jitsi added support for Jingle in 2007 and 2011 respectively. Google announced to drop XMPP support in 2013, so this is hardly related to XMPP being to slow to accept and adopt the standard. xmpp.org/extensions/xep-0167.h

@sesivany Also I doubt there is rapid development in instant messaging. The huge new features in IM in the last years have been what? Animated stickers and dark mode? That's hardly protocol related, but merely a UI thing.


Jirko, Google killed their #XMPP service for the same commercial reasons that drive every part of their business.

@ashwinvis @bjoern

Sign in to participate in the conversation
Mastodon @ SUNET

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!