News for hackers. Stuff that matters.
Re:Message from Facebook: this could be war by lmm on Wednesday March 25, 2015 @10:34AM (#9263183)
> What is wrong with jabber group chat?

The presumably protocol-level problems are that you can't "upgrade" a two-person conversation to a groupchat, and that a groupchat is an entity in its own right belonging to a particular server, which is something the user really shouldn't have to care about (and also causes reliability issues). And that there's no history.

Beyond that the user experience in every client I've used is terrible: open a dialogue to list available groupchats, manually join one, accept the notification, manually rejoin if you're disconnected. And then you tend to get notifications on every message, rather than just on messages that mention you; purely a client problem, but fundamentally if there are no good clients then it leads me to suspect there's a deeper problem.

Just compare with the groupchat experience in Slack or Skype or heck, AIM.

> You don't like the jabber priority based method of dealing with multiple connections. What would be better?

Send messages to all connected clients for the account, like virtually every other protocol does. And sync history between them. I can accept that that's hard without a centralized server, but it's vital.

Re:Message from Facebook: this could be war by upofadown on Wednesday March 25, 2015 @11:01AM (#9263364)
My instance of Ejabber will send to all connected clients in the case where the priorities are identical.
Re:Message from Facebook: this could be war by lmm on Wednesday March 25, 2015 @12:04PM (#9263811)
Really? Cool. That's explicitly contrary to the XMPP spec (unless it's changed since I last looked), but good on them for doing the pragmatic thing.