It's old news for Internet standards but Google Talk has opened their server (not the service yet).
Enough to confirm it's XMPP/Jabber. I was able to use my Gmail account both with Psi, iChat and AdiumX (libgaim based so all clients based on GAIM should work).
Works with plain 5222 connections but you need TLS (Gaim clients and iChat support that)
Works with SSL 5223 with any client, including Psi.
You need to set "allow plain passwords" if your client has that option.
S2S seems closed for the moment and no DNS SRV records are available for google.com, gmail,com or talk.gmail.com yet.
No agents or components can be found while browsing (disco, agents or browse) for any of those domains.
There's some integration with the GMail webmail already, namely:
Common contact lists. You can see your IM buddies in your E-Mail contact list. No distintion is made. JIDs are E-mails period!
If you add a gmail E-mail account to your Webmail account list, the XMPP server will send you a presence subscription of type none for the new contact. I guess their client will react to that and ask a subscribe to other peer immediatly.
No new e-mail alerts or webbased presence icons are visible yet.
Some questions without answers (yet):
Which XMPP server are they using ? It's not XCP from Jabber Inc. because we run one at @sapo.pt and it's doesn't behave like one. Obviously doesn't seem like any Opensource server too. Best bet is that it's their own work, and we're very curious.
Are they opening S2S at all ? We hope we don't see Google on the IM federation business. That's so NOT Jabber, NOT good.
VoIP details ? We'll have to wait for tomorow.
What kind of integration will we see with their other services Blogs, Search, AdWords, Gmail ? Google over XMPP would be very sexy
Google is mainly a Web application. Is WebIM planed ? poll/bind will be supported ?
What will be the mid term impact of this on the Jabber community, adoption, JSF and JEP standards/adoption?
Will Google be the reason for closing the pubsub JEP and kickoff missing for it's wide adoption ?
Some links:
Pedro Melo's my first Gmail IM buddy
Slashdot News entrySmashworld
And pic:
I think this is a great day for the Jabber community and the Opensource movement in general of proportions I haven't seem in a while, I feel happy.
PS: Their server seems to be up and down closing connections. They must be readying the beast.
Google Talk is now live. I was able to connect with Adium using Jabber as the account type, and my gmail login. Some notes: this is NOT jabber, it’s XMPP: Google Talk requires TLS for connection; Server-to-server is not yet operational, don&#82...
[...] many have noted Google’s IM Service is live. I read this excellent first insights by Celso and Melo. Both have been working closely with XMPP/Jabber for the last months and make some really interest [...]
I guess we'll see S2S and some transports in the future:
From the Google Talk FAQ:
we believe strongly in user choice and open standards, and we are committed to letting users access Google Talk using the client and platform of their choice, as well as to enabling our users to talk with users from other service providers.
The developer FAQ explains it a lot better:
http://www.google.com/talk/developer.html
DNS SRV records are not configured for the service at this time
Client applications should connect to host talk.google.com on port 5222
TLS is required
The only supported authentication mechanism is SASL PLAIN
PLAIN
4. Do you plan to support other real-time communication protocols?
Google Talk supports XMPP with the beta release. We plan to support SIP in a future release. Additionally, we will evaluate other protocols as appropriate, to continue to deliver on our commitment to open communications.
5. What protocols are used for voice calls?
Google Talk supports a custom XMPP-based signaling protocol and peer-to-peer communication mechanism. We will fully document this protocol. In the near future, we plan to support SIP signaling.
6. Which voice codecs do you support?
Today, Google Talk supports the following standard voice codecs: PCMA, PCMU, G.723, iLBC. We are also evaluating the Speex codec. We also support codecs from Global IP Sound: ISAC, IPCMWB, EG711U, EG711A
Google Talk is now live. I was able to connect with Adium using Jabber as the account type, and my gmail login. Some notes: this is NOT jabber, it’s XMPP: Google Talk requires TLS for connection; Server-to-server is not yet operational, don&#82...
Wednesday, August 24. 2005 at 01:32 (Link) (Reply)
Wednesday, August 24. 2005 at 02:52 (Link) (Reply)
From the Google Talk FAQ:
we believe strongly in user choice and open standards, and we are committed to letting users access Google Talk using the client and platform of their choice, as well as to enabling our users to talk with users from other service providers.
Wednesday, August 24. 2005 at 08:57 (Reply)
http://www.google.com/talk/developer.html
DNS SRV records are not configured for the service at this time
Client applications should connect to host talk.google.com on port 5222
TLS is required
The only supported authentication mechanism is SASL PLAIN
PLAIN
4. Do you plan to support other real-time communication protocols?
Google Talk supports XMPP with the beta release. We plan to support SIP in a future release. Additionally, we will evaluate other protocols as appropriate, to continue to deliver on our commitment to open communications.
5. What protocols are used for voice calls?
Google Talk supports a custom XMPP-based signaling protocol and peer-to-peer communication mechanism. We will fully document this protocol. In the near future, we plan to support SIP signaling.
6. Which voice codecs do you support?
Today, Google Talk supports the following standard voice codecs: PCMA, PCMU, G.723, iLBC. We are also evaluating the Speex codec. We also support codecs from Global IP Sound: ISAC, IPCMWB, EG711U, EG711A
Wednesday, August 24. 2005 at 09:04 (Reply)