Linked by Thom Holwerda on Sat 25th May 2013 00:45 UTC
Google "So in summary... Google has pulled the plug on support on a protocol they've helped popularize, after years of promising interoperability, for reasons that are dubious at best, and in a way that leaves people who don't jump to the new Hangouts app unable to talk to their contacts without any feedback that their IMs aren't getting through... And they've done that with no warning to anyone. I imagine there's a bunch of people out there wondering where some of their buddies have gone, or why their messages aren't getting responses, because this isn't documented anywhere." Google really messed this up. Such a dick move.
Thread beginning with comment 562728
To read all comments associated with this story, please click here.
Comment by leos
by leos on Sat 25th May 2013 02:19 UTC
leos
Member since:
2005-09-21

Don't be evil...

LOL

Reply Score: 2

RE: Comment by leos
by nej_simon on Sat 25th May 2013 08:57 in reply to "Comment by leos"
nej_simon Member since:
2011-02-11

Q: Are you guys planning to open up the tech behind Hangouts? Also, is it based on Muji or was it built from scratch?

A: Yes, we plan to publish the specifications needed to interoperate with Hangouts. At a high level, it's based on XMPP MUC (XEP-0045) and Jingle (XEP-0166/167), with some other enhancements needed to handle our architecture. We looked at Muji but concluded it wasn't a good fit for our service.

Reply Parent Score: 10

RE[2]: Comment by leos
by shmerl on Sun 26th May 2013 03:46 in reply to "RE: Comment by leos"
shmerl Member since:
2010-06-08

This looks like an old conversation. Hardly relevant already. Any newer references?

Edited 2013-05-26 03:47 UTC

Reply Parent Score: 2

RE: Comment by leos
by bowkota on Sat 25th May 2013 09:09 in reply to "Comment by leos"
bowkota Member since:
2011-10-12

This should be the new definition for "bait and switch".

Well done Google, once again.

Reply Parent Score: 0