4 ms·
Ironically, Whatsapp started out by using ejabberd — the XMPP server written in Erlang — as their main chat infrastructure, and then modified it to the point wh
by lobster_johnson 13y ago
Ironically, Whatsapp started out by using ejabberd — the XMPP server written in Erlang — as their main chat infrastructure, and then modified it to the point where it no longer implements XMPP.
- e12e 13y agoAnd google talk and facebook chat both used xmpp, and are both(?) avoiding federation -- and both(?) phasing out even supporting xmpp clients. For a little while I actually bothered using IM, as I actually had someone to talk to (most of my friends had facebook or gtalk -- and I could talk to them in the same interface I used for xmpp at work) -- and I could keep all the logs in one place (if I needed them) -- and it all supported secure texts (OTR). Now all my friends have access to crappy html5 chat silos that I'd rather not touch with a stick if I can help it. The things are all but impossible to use in a sane way without having to use a mouse -- and even if I could use them, I can't aggregate the logs, keep them independently of whether or not I keep the account(s) and I can't have access to everything in one application. Why would anyone use this or slack.com rather than setting up a jabber server? If you desperately want to restrict your choice of interface, you could always deploy a html5 jabber client, and pretend there aren't good native clients out there. I'm not sure why anyone would do that, though.
- lobster_johnson 13y agoHipChat actually supports XMPP, if you don't want to use the native apps. Doubt it's popular enough that services like Slack will do it too.