The new Google Hangouts will not support XMPP
You are the administrator for one or more Google App Engine applications that may be impacted by an upcoming new product release. Google will be releasing a new communications product called Hangouts which users may choose to use instead of Google Talk. The new service does not support XMPP.
As a result XMPP bots such as the App Engine XMPP service will not be able to communicate with users who adopt the new service. There are two ways to keep your App Engine XMPP service working for end users:
1) Your users may use any chat client that supports XMPP. XMPP clients will continue to work as usual with the App Engine XMPP service.
2) End users will be asked to opt-into the new service when it goes live. Note that the go-live date may vary for Google Apps domains. End users and google app domain administrators may choose not to opt into the new system. If they do not opt in they will remain on the current Talk client and there will be no change to their existing functionality, including being able to exchange messages with App Engine XMPP bots. Users who already opted in may toggle back to the old XMPP based chat clients in Gmail.
Note that the changes discussed above have no impact on non-Google XMPP clients, which will continue to work as usual with the App Engine XMPP service.
If you have any questions, comments, or concerns, please don't hesitate to email us at app-engine-xmpp-questions@googlegroups.com.
Sincerely,
The Google App Engine Team
© 2013 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
You have received this mandatory email service announcement to update you about important changes to Google Cloud Platform or your account.
142 comments
[ 4.5 ms ] story [ 214 ms ] threadTalking here about Docs, Gmail and so on. Somehow it became embarrassing for a nerd to straight out clone the competition, much like AbiWord and suchlike once did, simply in the name of freedom. Nowadays we have to compete on "sexy" innovative site designs and related sundry crap, and how many cloud "services" we integrate with.
I'll keep hoping for this resurgence, in the meantime I'll continue privately working toward cloning some of these services myself, until such a time as there is an established community for me to join. We basically need something like the (early day) GNOME foundation, but for the web.
autonomo.us is one mostly silent place to talk about it.
You may be right that there needs to be a (I think you might mean GNU project, not GNOME foundation?), but for the web. My guess as to why there hasn't been one is that the task is far messier, and there are a lot more choices about implementation. The usual thought following this is that free services need to federate rather than be part of the same project. But this thought could be wrong.
Half the battle isn't producing the software, it's ticking all the boxes that make people "go cloud" in the first place – you never need to run software update for Google Docs, you simply don't need to care about it.
What I'd love to see is a Ximian-styled system where you could subscribe to some release cycle (bleeding edge, 6 months behind, long term support), and behind the scenes a vast team of idealist monkeys worked to provide some of that cloud comfort – at the very lest, security updates.
The concept can be extended to quite elaborate proportions. But the low hanging fruit - let an admin create user accounts, let users login painlessly, and figure out how to make updates work safely & painlessly - and I believe half the war would already be won.
Priv.ly has an interesting approach to this somewhat analogous to the above: http://www.kickstarter.com/projects/229630898/protect-your-c...
Tent is a protocol for distributed social networking that I'm very optimistic about. You can message me at https://elimisteve.tent.is (sign up at tent.is).
Or run your own xmpp service, if you are a business/company. I personally use prosody. Works great.
He didn't continue that idea, but I think he would've continued it with "...but since nobody wants to do that, then we won't do it anymore either". So they are probably responding in the same way they responded to the leeching of Gmail contacts by Facebook a few years ago, by blocking that API, or in this case replacing the XMPP protocol with a proprietary one. It's too bad it had to come to this, though.
[1] - http://www.theverge.com/2013/5/15/4334242/larry-page-to-tech...
"... which users may choose to use instead of Google Talk."
"Google demands Microsoft removes YouTube Windows Phone app, cites lack of ads "
https://news.ycombinator.com/item?id=5714520
That was after they started serving a degraded experience to Windows Phone on Google Maps, and restored access after people complained and called their bluff that it didn't support needed features.
http://arstechnica.com/gadgets/2013/01/google-maps-windows-p...
Then they dropped support for ActiveSync from Gmail and Calendar so Microsoft had to scramble to add CalDAV support.
http://www.theverge.com/2013/1/21/3832838/windows-phone-card...
And then comes a second round of Spring Cleaning, which deprecates CalDAV support and moves to the Google Calendar API!
http://www.sparsebundle.net/posts/google-deprecating-caldav-...
Edit: Predictably, that post about Google asking for a takedown on the WP Youtube App is getting flagged.
http://i.imgur.com/4MBcGom.png
Just like the Windows 8.1 Blue being free post yesterday.
https://news.ycombinator.com/item?id=5707805
Google can do no wrong on HN, whereas everything Microsoft does is wrong.
See my comment in the other post.
https://news.ycombinator.com/item?id=5714520
The main issue is that partners that use revenue sharing couldn't restrict their videos from playing on WP devices that wouldn't generate ad revenue. Normally, you can block devices from having content if revenue sharing is unavailable, something Microsoft circumvented.
So, for years, Google's stated reason for lack of a Youtube client was that Windows Phone didn't have enough marketshare, and now suddenly it has so many users that it loses so many ad impressions because Microsoft's Youtube that the content creators are suffering because all the millions of freeloaders using Windows Phone?
i.e It doesn't care enough for the ad impressions on Windows Phone to itself make an app , but when MS does, the loss of the same revenue is the reason for sending the lawyers in and pulling the app?
In contrast, Yahoo Mail which is barely making any money by manages to make a nice one.
http://apps.microsoft.com/windows/en-us/app/yahoo-mail/f90f3...
And Vimeo has apps for both WP and Win8.
http://www.windowsphone.com/en-us/store/app/vimeo/ff8dadc8-8...
http://apps.microsoft.com/windows/en-us/app/vimeo/6608d199-0...
Had it been a Google startup, it may not have bothered me so much. I was using it way before Google brought it and now I am punished with a second class service for my choice of phone? That is just sad. :(
Just hope the same won't follow when Ubuntu and Firefox launch their phones.
A few sites doing that wouldn't have any effect. Google would probably just remove them. How many websites it would take for Google to actually pay attention though? 20%? 30%? 50%?
You could certainly say, "I'll keep you blocked in robots.txt (or block by IP or whatever) until you show my ads", but you are unlikely to succeed in that, and then there are still the downsides of not being listed in search results to consider.
While I don't think that every action you list is necessarily Google trying to screw over Microsoft (dropping support for common protocols hurts everyone, not just Microsoft), I also can't deny there's some obvious bad blood between them. It doesn't help that Google has a fair number of ex-microsoft employees, and they have A LOT of products in competition with each other (google vs bing, gdocs vs office, android vs wp, chrome vs IE, etc etc etc)
And the fact that HN would have a slight bias towards Google should not be a surprise, as Microsoft veers more towards the business side of software while Google veers more towards the open source, free stuff, etc etc. Which do you think people would honestly be more supportive of?
It's why I'm so upset that a large network that had the potential to include a huge amount of people and volume AND LEVERAGE XMPP just spat in our faces.
http://mashable.com/2013/05/14/bbm-ios-android/
I'm trying to stay open-minded, but so far I really dislike this product. I hope gtalk stays open.
I think the Chrome app is an excellent cross platform solution (written once, easily maintainable). As for the protocol I don't think it is practical or even possible to built this sort of all encompassing communications platform on top of XMPP (see the competition).
I do hope there will be a Hangouts API.
I'll cross my fingers for a Hangouts API that allows me to write a standalone client. However, if chatting through a semi-broken browser extension (or memory intensive gmail tab) are my only options, then I guess the service isn't for me. I think the reason I'm annoyed is that I have a lot of important contacts on gtalk, so migrating away will be a challenge.
I know change is inevitable, that the service is free, and that they want to offer a better product. Perhaps my use cases are just too expensive to support in the long run.
XMPP _federation_ is going away :(.
WhatsApp is XMPP, fundamentally, in any case.
As for a binary serialization, XMPP traffic does compress very well already (TLS/zlib/lzw), but we have started the process on standardizing the use of EXI (https://en.wikipedia.org/wiki/Efficient_XML_Interchange).
However, the XMPP community has been active in quantifying such issues and providing solutions. The beginning of a document with background information is available as http://xmpp.org/extensions/xep-0286.html. There are also various opinions on the topic to be found online, like http://www.deepdarc.com/2008/02/14/mobile-xmpp/, that, as you can see, dates back half a decade already.
Facebook also have a private extension, as I understand things.
I should actually submit that extension - I wrote it up as a XEP ages back, but various things have held it up.
1) the free protocols to do voice and video are not as good as the proprietary ones
2) it seems that every client use a different set of protocols for video and chat
I'll be very happy with Google Hangouts but I'm still waiting for the properly federated chat that appeals to the masses.
You can set up your own XMPP server or use one of tons of the public ones: http://xmpp.net/
Edit: There's also jabber.org http://www.jabber.org/ which probably will operate as long as XMPP is still relevant.
Instant Messaging is now dead for me because all the people I used to chat with are now fragmented across 4 or 5 different services. Aside from those who gave up on IM for the same reason I now have to.
You've all literally killed IM. Well done.
Sure, you usually get a common denominator of features between the various networks, but presence and chat usually is enough.
Whatever. Google Voice is a dying product, and I hate them for what they've done, but at least the underlying transport is SMS and a portable phone number -- if I want I can host it myself in Plivo, which I plan on doing soon.
About an hour ago, the personal account had a changed icon, started looking nicer, and is now called Hangouts. The Apps for business one stayed the same.
I've never been closer to being a fanboi than I was with Google, but this seals it...I'm pissed. Closing off (yet another) service in favor of proprietary protocols is not something a "Don't Be Evil" company does...in fact it's why you have the motto in the first fucking place.
You could have made the change without breaking XMPP. This is just shitty all the way around.
I just hope they'll keep XMPP running for the chat. I'll stop using it the second it'll stop working in bitlbee.
Why not? XMPP is pretty extensible, and Google's Jingle spec was open. Is there a technical reason that Hangouts had to be based on something other than Jabber?
Ahem. This[1] is close enough to a motto to make this part of your comment irrelevant.
[1]: http://en.wikipedia.org/wiki/Don%27t_be_evil
The biggies will be the ones supported by large companies (ie, Skype, iMessage, Hangouts).
So when will Amazon buy Viber or another smaller chat community?.
SMS. And as much as I hate to say it, iMessage has the best support/transparency for it so far
So does this mean the rollout is not complete, and what they rolled out as Hangouts today is not what they'll ultimately roll out? Or does it mean -- as I suspect -- that New Hangouts is XMPP under the hood, but they plan to flip the 'interoperate' switch to 'off' once they think nobody will notice?
Hangouts CAN NOT communicate with XMPP clients.
IM has never been unified. In the mid-90s you had the war between AIM and ICQ, then came along the IM clients from MSN, Yahoo and Excite. That's what led to the rise of multi-protocol IM clients like Gaim, Jabber and IMVU and out of that rose XMPP (one of 5 major "cross-compatibilty" IM standards).
Then you had a new generation of IM wars as desktop clients died out and were replaced by browser chat like GTalk and Facebook Messenger. As the desktop IM clients died, Skype pretty much absorbed their desktop users into their voice chat platform.
But now web IM clients are being wiped out by a new generation of mobile IM apps like WhatsApp, Vibber, etc.
IM has never been unified, and given it's track record, I doubt that's going to change anytime soon.
http://msdn.microsoft.com/en-us/library/live/hh826554.aspx
AIM also has limited XMPP support (although that is just from a quick Google search, can't figure out if that is still the case).
Either way more and more clients and chat protocols were beginning to converge onto a single standard, that allowed people to easily communicate across different "domains". That is now going away.
I was wondering why my friends with non-Google Jabber IDs were never showing up as online, and one day figured out federation was turned off.
This is as if a few months ago your email provider silently discarded emails to and from other domains, and just today abandoned SMTP and IMAP.
The true failure happened way back when federation was abandoned, not today.
1) Subscription requests to/from other domains were blocked.
2) Only for a short period (about a month, tops).
Can anyone clarify if this actually impacts your average standalone XMPP client, not connected with AppEngine, sending and receiving messages to Google Talk users?
If you have an App Engine instance, and it uses the App Engine XMPP Service[1] to send messages to people, then that will stop working for users who switch to Hangouts.
[1] https://developers.google.com/appengine/articles/using_xmpp
1) Competitors use Google's APIs based on open standards for their own advantage.
2) Google gets annoyed.
3) Google stops supporting open standards.
Well, that's my honeymoon with Google over.
It seems a naive mistake to have assume an enlarging Google would stay true to their roots.
It's time for those roots to move. Onwards and upwards.
It turns out Open Source's weird uncle was right again.