`With Hangouts, Singhal says Google had to make the difficult decision to drop the very “open” XMPP standard that it helped pioneer.´
Here we go…
Michael K Johnson May 16, 2013 06:52
https://developers.google.com/talk/open_communications was updated yesterday and doesn’t mention this. Does that mean that google will still federate (XMPP back end) but not use it for their own chat products? I think this deserves some further explication from +Nikhil Singhal
Eugene Crosser May 16, 2013 07:05
If the change means that I can no longer log in to my @gmail.com account using a third party xmpp client, I can live with that.
If it means that server-to-server xmpp federation stops to work, i.e. that a gtalk user cannot transparently IM with a user of any other jabber system, that’s really bad.
r herrold May 16, 2013 08:33
‘With Hangouts, Singhal says Google had to make the difficult decision to drop the very “open” XMPP standard that it helped pioneer.’ … because an Extensible Messaging and Presence Protocol is not, you know, designed to be Extended
Seems like a direct run at a big vendor using a local deviation from a standard RFC to lock out competitors. It was wrong with AD and Microsoft; it is wrong here, from the little color in the article
so, +Nikhil Singhal , what forced Google to NOT simply extend via the XMPP approach, and what is needed to open it as a new RFC, and when will Google be proposing that new RFC?
Jes Sorensen May 16, 2013 10:33
Please Google, just take hangouts and put them somewhere else, and stop putting everyone in my circles into my Jabber contact list - that is really all I am asking.
Imported from Google+ — content and formatting may not be reliable