Do not panic! About what Google did with XMPP
After the release of Google Hangout, the opinion that Google is closing XMPP has become popular on the Internet. In fact, it is not. However, such an impression could even have arisen from the previous article , which contained hellish nothing in itself - at least details, one link (irrelevant - apparently, from OpenNet) to the Maemo forum (which, of course, has nothing to do with Google) comments of varying degrees of truthfulness.
To understand what really happened, it was necessary to go through a lot of different discussions in various sources, which took time. I live with the understanding that Google has been troubled with XMPP for several months now and at least a couple of them with the understanding that Google is losing interest in XMPP, so I gathered and structured all the information in one place.
')
Under the cat a complete collection of incidents and facts around Google Hangout, GTalk XMPP, s2s, user and expert assessments of the situation.
Let's look at what is happening with GTalk from the first stage, when the first reports appeared that Google had closed S2S. S2S (Server-to-Server) or server-to-server communication allows users of one jabber server to send messages to users of another jabber server. This is the most important condition for server Orthodox, along with support for conferences, registration availability, and of course uptime.
The s2s issues became public in April. In the LiveJournal community of zhabberbovodov, a discussion was formed where people flooded about the closure of s2s with Google, and even on Habré an article appeared about the upcoming Google Babel - habrahabr.ru/post/176347 . In the club Jabber they wrote on this topic a little more restrained.
Let us turn to the origins. In fact, it all started back in February , when Google employees noticed spam activity from some servers and warned the community that they would limit the number of requests to add to the contact list from (all) other servers if requests continue to arrive:
You already know that this is exactly what happened in the end . Google has enabled subscription request blocking. As a true gentleman, Google also invited interested server owners to add to the white list. Large server invitation mainly ignored. Owners of several smaller ones have been added to the white list.
For two months, requests to add to the contact list were available only from GTalk users, and it was not possible to request a subscription from a GTalk user. In April, Google screwed up spam filters and removed the block.
Quite a long lockout caused some amount of inconvenience and even myths.
But if many wrote about blocking requests, for example, Opennet - www.opennet.ru/opennews/art.shtml?num=36409 - only the original source wrote about lifting the lock and restoring a full-featured s2s; / sysadmin / google-reinstates-federated-instant-messaging .
Why did you decide that Google has closed s2s?
Because in the announcement, federated domains were mentioned and affected.
Did Google close s2s?
No, did not close.
Findings?
Read the original sources is useful.
And now let's move on to the Hangouts situation.
GOOGLE DIDN'T TURN OFF XMPP. Google has released a new CLIENT for instant communication. New messenger.
One protocol. The protocol is closed.
Messenger functionality: sending messages, audio, video calls.
The primary source of information about abandoning XMPP in Google Hangouts is Nikhyl Singhal, head of communications services at Google, who, in an exclusive interview with TheVerge, stated the following:
From Nikhayl's words, it turns out that Google Talk was created to help communicate to corporate users, and while developing Hangouts at Google, they wanted to create something social and always accessible. This was at variance with the Talk ideology and Google made the difficult decision to abandon the very open XMPP standard that it helped develop.
To such a statement immediately raises a lot of questions. Google’s participation in XMPP was not as impressive as Singhal was trying to present in his statement. True, this is no longer a direct quotation of Singhal, but a statement by a journalist from TheVerge, so one cannot exclude an error in the wording. But not like. What was the fact? GTalk was launched in August 2005. In December of the same year, the library libjingle was published - an open implementation of the standard XEP-0166: Jingle . Since then, they have practically not been involved in either GTalk or XMPP standards. From standards-related, in 2006 S2S was solemnly launched - that's all. Correct me if you can, but Google didn’t do any other work with XMPP standards on Google.
Google had interesting initiatives in the form of a web chat in Gmail, transport in AOL (which at the same time allowed to work with ICQ until ICQ was sold at DST, now known as Mail.ru Group). But this did not concern and did not help the protocol, the XMPP standard .
Another possible explanation for the abandonment of XMPP is the most notorious spammy invites. However, attempts to solve the problem through the creation / modification of standards and other-other by Google, too, was not noticed. Moreover, the previous 10 years no one has encountered such a problem on an industrial scale. And on the side of Google, too, did not notice. That is, about this method of solving the problem worked with a bang:
I exaggerate, of course, but nonetheless. Spammers are quite successfully cut off at the server level with various monitoring tools, at the user level with bots, captcha and so on. In especially serious cases, you can temporarily block s2s with the spammer server or close the registration.
Thus, the mention of XMPP minuses from Google employees looks more like an attempt to justify in the eyes of the public the transition to Hangouts. But the attempt is weak. Of course, distribution across all Android devices is a much more significant factor and everyone understands that.
Thanks to bobuk , we have a letter from Google stating that bots on AppEngine will no longer always work correctly - they will not be able to send messages to Hangout users. But this concerns not only AppEngine bots, but all XMPP users.
Translated into Russian, this means:
The same is true not only for App Engine, but for any XMPP server and not only for bots, but also for regular Google Talk accounts.
For third-party XMPP clients, there has been no change in GTalk, and it will not happen in the near future. The official position regarding third-party clients is also quite clear and has not changed - use any Jabber client. Google just stopped making jabber client.
Can I save GTalk somehow?
They say that you can put Hangouts from apk , then Talk will not be demolished. I have a hangout from this apk anyway replaced the Talk. Removing Hangouts from Google Play allows you to roll back to the GTalk pre-installed on Android. In the new versions of Android, most likely there will be no GTalk and it will be more difficult to install it.
Do you have to dump from gmail.com (GTalk) to another Jabber server?
No, I do not have to. Just make sure that neither you nor your friends are using Google anymore. For reliability, you can use the same client - then everything will work exactly.
If you need a web client, use open source Jappix .
And if you still throw, then where?
yandex.ru, qip.ru, jabber.ru/xmpp.ru
to your domain - pdd.yandex.ru, hosted.im,
to your server - ejabberd, prosody, openfire
Nota bene: With Yandex, everything is also not so rosy. The last days of Yandex, and as a result of Jabber.ru, which is hosted nearby, also have problems in their work. But do not wake yourself paranoid, this has happened before. It should get better.
However, Yandex Jabber is not interesting. The only question is when they get tired and when they decide to close. Of course, it will not be very soon. But it is possible that all the same will be.
How do Jabber fans communicate with Google Hangouts users?
Only through the client hangouts.
If you are sent from Hangouts to your GTalk account, which is enabled through the jabber client, you will receive a message, but your contact will not receive a response. Therefore, if you do not respond for a long time to a message sent from a jabber, you will have to either launch Hangouts and check whether the message was delivered at all.
Uncomfortable?
Inconvenient. Try to use either only Hangouts, or only GTalk through jabber clients.
So, what is next? From SMTP and POP3 do not think to refuse?
Yevgeny Vaganych, isn't it you? Google changed the client and went to reinvent the wheel. Well, OK. XMPP continues to live and develop. XMPP on Google continues to work. What are these assaults?
I loved the gtalk mobile. What to use next?
Under Android, perhaps, try IM +. By the simplicity of the interface, it is most similar to the original GTalk.
Alternatively, consider Jasmine IM and the recently updated QIP, depending on the requirements for functionality and design, respectively.
And yet, by the way, Xabber is also an option.
Under iOS - Talkonaut, IM +, Imo.im
Talk has been my main IM for many years now that Skype is starting to use ??
Skype or Viber, if you call in principle. If it doesn't matter, use any normal jabber-client.
Third-party jabber-clients are still working, but they will probably be banned soon in this way.
I hope after this article it became clear that this is speculation.
How can you prevent a jabber client from connecting to a jabber server? Why would Google spend resources on it if XMPP doesn't have a basic solution?
The question can only be whether the entire Jabber server will be closed. You can speculate that they will close, and I - that they will not.
Only an official announcement will resolve this dispute. Let's wait. I think we will have to wait another year at least. So for now - use.
In addition to all the inconveniences that obviously arise from the actions of Google, there is another side to the issue. After all, Google Talk was the most awesome XMPP service! GTalk's S2S did indeed fall off with various servers. Sometimes there were problems with connections. And all at least some major players in the voice claim that GTalk is under XMPP.
Since its inception ...
Anton Ugnich ( ugnich ), founder of the Jabber microblogging service Juick.com:
About the death of Google Talk:
This proposal, of course, should be taken with a bit of humor, but the message is generally true: despite the fact that XMPP is a very rich and open protocol in theory, it should be supported by practice. The implementation of clients and servers should change, or the protocol as a whole can be replaced in the future with something more dynamic. After all, there is always such a guy:
I am very impressed with the position of the Xabber developers, who have crystallized in the last three months:
The problem is that the development of the XMPP itself also needs a lot of work to make it comfortable and versatile. This is quite complicated and none of the end-user client developers are doing this. And those who are engaged are far from the mass user. XMPP doesn't have a development vector right now. So, they do something little by little in standards and nothing is introduced that we could use in life. Interesting standards are adopted, but their implementations are not distributed in popular Jabber clients and therefore new functions cannot be used to communicate with an arbitrary interlocutor. There is a segmentation on clients.
It is necessary to distinguish the Hangouts messenger, GTalk messenger and Google Talk jabber service. C2S in Hangouts is supported, S2S is not.
Nothing happened to the GTalk jabber servers.
But GTalk's jabber clients have been replaced with a client for the new protocol, and in this sense, Google really refuses XMPP. Not technically, but ideologically. Google deprives the XMPP community of its support and starts moving in the direction of the Skype-like model. Including focusing on sound and video.
Hangouts -> Gtalk
Gtalk -> Hangouts
youserver.org <-> Gtalk
Gtalk <-> Gtalk
youserver.org X Hangouts
Hangouts X youserver.org
1. It is unpleasant that now not all mail jabber.
Previously, any large mail in RuNet, with the exception of Mail.ru, was a Jabber: GMail, Yandex, QIP (Pochta.ru, etc.) formed the big three Jabber players.
2. One of the most convincing arguments in favor of XMPP - “you are already using jabber” stopped working. Although it still works "you already have a jabber."
3. Maybe “don’t be evil”
Peter Saint-Andre
It did not start yesterday or today.
On the question of what we should expect, but in relation not to the XMPP protocol, but to other Google services, the article Nojitter is trying to answer - Google I / O Silent Announcements .
View original Hangouts report on Google I / O - www.youtube.com/watch?v=9pmPa_KxsAM&feature=youtu.be&t=1h42m34s
This article also relies on many private opinions on which you can observe the degree of relevance of the issue . Many sources are listed in the article, other - here:
www.theverge.com/2013/5/15/4318830/inside-hangouts-googles-big-fix-for-its-messaging-mess
techcrunch.com/2013/05/16/googles-new-hangouts-chat-and-messaging-app-to-incorporate-sms-soon
http://productforums.google.com/forum/#!topic/chat/Yvaa70u-AOI
juick.com/tag/jabber - user stories
juick.com/tag/google
plus.google.com/u/0/105319907965825397218/posts/a3DTDC59wn4
plus.google.com/u/0/116630836705915947538/posts/Lr1beAgc14o
readwrite.com/2013/05/16/google-io-2013-google-hangouts-google-plus-changes-messaging
To understand what really happened, it was necessary to go through a lot of different discussions in various sources, which took time. I live with the understanding that Google has been troubled with XMPP for several months now and at least a couple of them with the understanding that Google is losing interest in XMPP, so I gathered and structured all the information in one place.
')
What has Google done with XMPP? Nothing.
Under the cat a complete collection of incidents and facts around Google Hangout, GTalk XMPP, s2s, user and expert assessments of the situation.
Chronology
Let's look at what is happening with GTalk from the first stage, when the first reports appeared that Google had closed S2S. S2S (Server-to-Server) or server-to-server communication allows users of one jabber server to send messages to users of another jabber server. This is the most important condition for server Orthodox, along with support for conferences, registration availability, and of course uptime.
The s2s issues became public in April. In the LiveJournal community of zhabberbovodov, a discussion was formed where people flooded about the closure of s2s with Google, and even on Habré an article appeared about the upcoming Google Babel - habrahabr.ru/post/176347 . In the club Jabber they wrote on this topic a little more restrained.
Let us turn to the origins. In fact, it all started back in February , when Google employees noticed spam activity from some servers and warned the community that they would limit the number of requests to add to the contact list from (all) other servers if requests continue to arrive:
Hi
I’ve been seeing lots of spammy domains, including jabberes.org, jabber.se, jabber-hosting.com and jabber.org. If you’re not aware of the situation,
Per gustafsson
You already know that this is exactly what happened in the end . Google has enabled subscription request blocking. As a true gentleman, Google also invited interested server owners to add to the white list. Large server invitation mainly ignored. Owners of several smaller ones have been added to the white list.
For two months, requests to add to the contact list were available only from GTalk users, and it was not possible to request a subscription from a GTalk user. In April, Google screwed up spam filters and removed the block.
Quite a long lockout caused some amount of inconvenience and even myths.
But if many wrote about blocking requests, for example, Opennet - www.opennet.ru/opennews/art.shtml?num=36409 - only the original source wrote about lifting the lock and restoring a full-featured s2s; / sysadmin / google-reinstates-federated-instant-messaging .
Total
Why did you decide that Google has closed s2s?
Because in the announcement, federated domains were mentioned and affected.
Did Google close s2s?
No, did not close.
Findings?
Read the original sources is useful.
And now let's move on to the Hangouts situation.
Google refuses XMPP?
Google refuses XMPP?
Google refuses XMPP?
WHAT REALLY HAPPENED?
GOOGLE DIDN'T TURN OFF XMPP. Google has released a new CLIENT for instant communication. New messenger.
One protocol. The protocol is closed.
Messenger functionality: sending messages, audio, video calls.
What do we have officially?
The primary source of information about abandoning XMPP in Google Hangouts is Nikhyl Singhal, head of communications services at Google, who, in an exclusive interview with TheVerge, stated the following:
Talk, for example, was better, Singhal says. "Talk. It’s a notion of creating something." that it helped pioneer.
From Nikhayl's words, it turns out that Google Talk was created to help communicate to corporate users, and while developing Hangouts at Google, they wanted to create something social and always accessible. This was at variance with the Talk ideology and Google made the difficult decision to abandon the very open XMPP standard that it helped develop.
To such a statement immediately raises a lot of questions. Google’s participation in XMPP was not as impressive as Singhal was trying to present in his statement. True, this is no longer a direct quotation of Singhal, but a statement by a journalist from TheVerge, so one cannot exclude an error in the wording. But not like. What was the fact? GTalk was launched in August 2005. In December of the same year, the library libjingle was published - an open implementation of the standard XEP-0166: Jingle . Since then, they have practically not been involved in either GTalk or XMPP standards. From standards-related, in 2006 S2S was solemnly launched - that's all. Correct me if you can, but Google didn’t do any other work with XMPP standards on Google.
Google had interesting initiatives in the form of a web chat in Gmail, transport in AOL (which at the same time allowed to work with ICQ until ICQ was sold at DST, now known as Mail.ru Group). But this did not concern and did not help the protocol, the XMPP standard .
Another possible explanation for the abandonment of XMPP is the most notorious spammy invites. However, attempts to solve the problem through the creation / modification of standards and other-other by Google, too, was not noticed. Moreover, the previous 10 years no one has encountered such a problem on an industrial scale. And on the side of Google, too, did not notice. That is, about this method of solving the problem worked with a bang:
I exaggerate, of course, but nonetheless. Spammers are quite successfully cut off at the server level with various monitoring tools, at the user level with bots, captcha and so on. In especially serious cases, you can temporarily block s2s with the spammer server or close the registration.
Thus, the mention of XMPP minuses from Google employees looks more like an attempt to justify in the eyes of the public the transition to Hangouts. But the attempt is weak. Of course, distribution across all Android devices is a much more significant factor and everyone understands that.
Thanks to bobuk , we have a letter from Google stating that bots on AppEngine will no longer always work correctly - they will not be able to send messages to Hangout users. But this concerns not only AppEngine bots, but all XMPP users.
Hello from Google!
Google App Engineers can be impacted by an upcoming product product release. Google Talk. The new service does not support XMPP.
As a result, XMPP bots such as the App Engine. There are two ways to keep your App Engine working:
1) Your users may use XMPP. App Engine XMPP service.
2) It goes live. For Google Apps domains. End users and google app. There is no change to their existing functionality, such as the App Engine XMPP bots. XMPP based chat users in Gmail.
Note: The XMPP clients have been affected by the App Engine XMPP service. If you have any questions, comments, or concerns, please contact us at app-engine-xmpp-questions@googlegroups.com.
Sincerely, The Google App Engine Team
Translated into Russian, this means:
2) End users will be asked to switch to the new [Hangouts] service when it is launched. Please note that the launch date for Hangouts for Google Apps domains may vary. End users and administrators of Google Apps domains will be able to refuse to switch to the new system. If they refuse to go to Hangouts, Google Talk will continue to work for them and there will be no change in the current functionality, including the ability to exchange messages with XMPP bots App Engine.
...
Please note that all the above changes do not have any impact on third-party XMPP clients that will continue to work with the App Engine XMPP service as usual.
The same is true not only for App Engine, but for any XMPP server and not only for bots, but also for regular Google Talk accounts.
For third-party XMPP clients, there has been no change in GTalk, and it will not happen in the near future. The official position regarding third-party clients is also quite clear and has not changed - use any Jabber client. Google just stopped making jabber client.
2. Which other clients can connect to the Google Talk service?
Any client that supports Jabber / XMPP can connect to the Google Talk service. Here is a list of popular clients .
Questions and answers. Why does everything work for me?
Can I save GTalk somehow?
They say that you can put Hangouts from apk , then Talk will not be demolished. I have a hangout from this apk anyway replaced the Talk. Removing Hangouts from Google Play allows you to roll back to the GTalk pre-installed on Android. In the new versions of Android, most likely there will be no GTalk and it will be more difficult to install it.
Do you have to dump from gmail.com (GTalk) to another Jabber server?
No, I do not have to. Just make sure that neither you nor your friends are using Google anymore. For reliability, you can use the same client - then everything will work exactly.
If you need a web client, use open source Jappix .
And if you still throw, then where?
yandex.ru, qip.ru, jabber.ru/xmpp.ru
to your domain - pdd.yandex.ru, hosted.im,
to your server - ejabberd, prosody, openfire
Nota bene: With Yandex, everything is also not so rosy. The last days of Yandex, and as a result of Jabber.ru, which is hosted nearby, also have problems in their work. But do not wake yourself paranoid, this has happened before. It should get better.
However, Yandex Jabber is not interesting. The only question is when they get tired and when they decide to close. Of course, it will not be very soon. But it is possible that all the same will be.
How do Jabber fans communicate with Google Hangouts users?
Only through the client hangouts.
If you are sent from Hangouts to your GTalk account, which is enabled through the jabber client, you will receive a message, but your contact will not receive a response. Therefore, if you do not respond for a long time to a message sent from a jabber, you will have to either launch Hangouts and check whether the message was delivered at all.
Uncomfortable?
Inconvenient. Try to use either only Hangouts, or only GTalk through jabber clients.
So, what is next? From SMTP and POP3 do not think to refuse?
Yevgeny Vaganych, isn't it you? Google changed the client and went to reinvent the wheel. Well, OK. XMPP continues to live and develop. XMPP on Google continues to work. What are these assaults?
I loved the gtalk mobile. What to use next?
Under Android, perhaps, try IM +. By the simplicity of the interface, it is most similar to the original GTalk.
Alternatively, consider Jasmine IM and the recently updated QIP, depending on the requirements for functionality and design, respectively.
And yet, by the way, Xabber is also an option.
Under iOS - Talkonaut, IM +, Imo.im
Talk has been my main IM for many years now that Skype is starting to use ??
Skype or Viber, if you call in principle. If it doesn't matter, use any normal jabber-client.
Third-party jabber-clients are still working, but they will probably be banned soon in this way.
I hope after this article it became clear that this is speculation.
How can you prevent a jabber client from connecting to a jabber server? Why would Google spend resources on it if XMPP doesn't have a basic solution?
The question can only be whether the entire Jabber server will be closed. You can speculate that they will close, and I - that they will not.
Only an official announcement will resolve this dispute. Let's wait. I think we will have to wait another year at least. So for now - use.
Google "well done"
In addition to all the inconveniences that obviously arise from the actions of Google, there is another side to the issue. After all, Google Talk was the most awesome XMPP service! GTalk's S2S did indeed fall off with various servers. Sometimes there were problems with connections. And all at least some major players in the voice claim that GTalk is under XMPP.
Since its inception ...
- The server does not send or receive messages if there is no authorization (subscription). This is done in case of spam. Those. without mutual authorization, you will not be able to send and receive messages, and you will always be “Offline” with each other.
- Only two-way authorization is supported (one-way authorization is equivalent to the absence of authorization).
- When connecting the transports to your account on Google, there may be problems. For example, the transport is “lost” with a new login or is not connected automatically.
- Storage of bookmarks on the server is not supported.
- Jabber conferences are not supported.
- Private lists are not supported (list of those who see, those who do not see and are ignored)
- No user search for any data.
- The server does not allow you to change information about yourself by the client.
- The server does not allow changing the password from the account by the client.
- When you delete a contact from the contact list, it is deleted from the Google address book. Also, when you delete a contact from your address book, it is removed from the contact list.
- The server, when connected, adds to the resource a random sequence of letters and numbers, because the official client does not support resources.
Anton Ugnich ( ugnich ), founder of the Jabber microblogging service Juick.com:
About the death of Google Talk:
Well, [if soon] it is not necessary [will] to support this pitiful similarity of XMPP, one less headache. juick.com/ugnich/2360253
Philip Kulin ( schors ), DiPhost:
Google is really well done. I was upset and stopped here. Well, he did not draw free service, so he left and does not interfere with commercial services. The same XMPP is not clear at all what lives. For more than 10 years of its existence, nobody really supports it. There are standards, but no intelligent implementations have arisen. Vaughn, Juick - then so he is not this, then this. So this is an opportunity for us, brothers and sisters, to make our standard, for students to create clients and servers for it, for a business to sell it. Maybe our new standard will be a hundred times better than stillborn streaming XML.
This proposal, of course, should be taken with a bit of humor, but the message is generally true: despite the fact that XMPP is a very rich and open protocol in theory, it should be supported by practice. The implementation of clients and servers should change, or the protocol as a whole can be replaced in the future with something more dynamic. After all, there is always such a guy:
I am very impressed with the position of the Xabber developers, who have crystallized in the last three months:
GoogleReader news reminded us of the #GoogleWave death. We are not sure that Xtmp will survive in gtalk. March 14th
We assume once #GTalk is no longer compatible with #XMPP. This will be the day we stop using it. "Don't be evil", is it? April 16th
We'd better run #kickstart to create a #xmpp client that implements all the things from the Hangouts based on XEPs on May 22
The problem is that the development of the XMPP itself also needs a lot of work to make it comfortable and versatile. This is quite complicated and none of the end-user client developers are doing this. And those who are engaged are far from the mass user. XMPP doesn't have a development vector right now. So, they do something little by little in standards and nothing is introduced that we could use in life. Interesting standards are adopted, but their implementations are not distributed in popular Jabber clients and therefore new functions cannot be used to communicate with an arbitrary interlocutor. There is a segmentation on clients.
XMPP vs Hangouts
Hangouts does not support XMPP federation. At all. Fundamentally. And not going.He's worse. And then, who knows what the hangouts have inside? Perhaps, at some point, Google will switch to some standard protocol again :) Never say never.
It is necessary to distinguish the Hangouts messenger, GTalk messenger and Google Talk jabber service. C2S in Hangouts is supported, S2S is not.
Nothing happened to the GTalk jabber servers.
But GTalk's jabber clients have been replaced with a client for the new protocol, and in this sense, Google really refuses XMPP. Not technically, but ideologically. Google deprives the XMPP community of its support and starts moving in the direction of the Skype-like model. Including focusing on sound and video.
Cross-server Hangouts and XMPP
Hangouts -> Gtalk
Gtalk -> Hangouts
youserver.org <-> Gtalk
Gtalk <-> Gtalk
youserver.org X Hangouts
Hangouts X youserver.org
PostGool Era
1. It is unpleasant that now not all mail jabber.
Previously, any large mail in RuNet, with the exception of Mail.ru, was a Jabber: GMail, Yandex, QIP (Pochta.ru, etc.) formed the big three Jabber players.
2. One of the most convincing arguments in favor of XMPP - “you are already using jabber” stopped working. Although it still works "you already have a jabber."
3. Maybe “don’t be evil”
Peter Saint-Andre
It did not start yesterday or today.
We are unpleasant.
We will not die.
Let's not panic.
What to read
On the question of what we should expect, but in relation not to the XMPP protocol, but to other Google services, the article Nojitter is trying to answer - Google I / O Silent Announcements .
View original Hangouts report on Google I / O - www.youtube.com/watch?v=9pmPa_KxsAM&feature=youtu.be&t=1h42m34s
This article also relies on many private opinions on which you can observe the degree of relevance of the issue . Many sources are listed in the article, other - here:
www.theverge.com/2013/5/15/4318830/inside-hangouts-googles-big-fix-for-its-messaging-mess
techcrunch.com/2013/05/16/googles-new-hangouts-chat-and-messaging-app-to-incorporate-sms-soon
http://productforums.google.com/forum/#!topic/chat/Yvaa70u-AOI
juick.com/tag/jabber - user stories
juick.com/tag/google
plus.google.com/u/0/105319907965825397218/posts/a3DTDC59wn4
plus.google.com/u/0/116630836705915947538/posts/Lr1beAgc14o
readwrite.com/2013/05/16/google-io-2013-google-hangouts-google-plus-changes-messaging
Source: https://habr.com/ru/post/180159/
All Articles