2 ms·
As near as I can tell, all the new stuff is a strict subset of what is fairly standard in the XMPP world. The only novel addition is that instead of supporting
by jerf 11y ago
As near as I can tell, all the new stuff is a strict subset of what is fairly standard in the XMPP world. The only novel addition is that instead of supporting many clients, there is one blessed client, which is web-based. This means that rather than wondering if a given client supports some feature, or has some emoticon set installed and turned on, you know exactly how the client behaves and can implement features faster as a result. The configurability, flexibility, and client choice that XMPP offers appear to be drawbacks rather than advantages. Plus web browsers are so capable now that using them as a programming base for something like chat immediately gives you a huge UI step up.
Tone note: I'm dead serious, no sarcasm anywhere in there. Things that are self-evidently true to developers like "choice is good!" aren't always true in the market. Being able to count on a specific client really helps with the feature development.
If you're interested in getting in on the action you could probably do worse than start a startup shipping an open source XMPP server, using an open source XMPP web client, and doing the rather minimal modifications it would take to make it support some manner of embedding YouTube videos and inline images. (Seriously, like, two weeks, from a standing start.)
- fjarlq 11y agoHonest question: who here is using open source XMPP software today in a Slack-like manner? If so, what is your software+config, and how do you like it? When I last investigated XMPP for this, back in January 2014, I found that open source support by both servers and clients, for Slack-like features such as search and persistent chat history, were at least rough around the edges, if not lacking entirely.