Hi Everyone... This is great news as Jabber is endorsed by Google....
Google Talk uses the standard XMPP protocol for authentication, presence, and messaging. http://www.google.com/talk/developer.html Download Jabber client from Google and connect to Jabber server using gmail account http://www.google.com/talk/ Client supported: http://www.google.com/talk/otherclients.html Google has come up with new XMPP-based signaling protocol for voice calls but not sure if they will make it open.... Regards Brijesh Singh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 6:19 AM To: [email protected] Subject: jdev Digest, Vol 19, Issue 26 Send jdev mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://mail.jabber.org/mailman/listinfo/jdev or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of jdev digest..." Today's Topics: 1. Re: PyMsn (Remko Troncon) 2. Re: Google and jabber (Hal Rottenberg) 3. Re: Google and jabber (Tijl Houtbeckers) 4. Re: Google and jabber (Fabio Forno) 5. Re: Google and jabber (Chris Chen) 6. Re: Google and jabber (Fabio Forno) 7. Re: Google and jabber (Ulrich Staudinger) 8. Re: Google and jabber (Dan Cunningham) 9. Re: Google and jabber (Celso Martinho) 10. RE: Google and jabber (JD Conley) 11. Re: Google and jabber (Celso Martinho) ---------------------------------------------------------------------- Message: 1 Date: Tue, 23 Aug 2005 19:23:38 +0200 From: Remko Troncon <[EMAIL PROTECTED]> Subject: [jdev] Re: PyMsn To: Jabber software development list <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On 23 Aug 2005, at 18:00, Francisco Obarrio wrote: > is there any way of avoid the step of adding one user per time to my > roster when i register ? > is it possible to change something on the config transport ? You probably want to direct your questions te the PyMSN-t mailinglist. See their webpage for the address. I'm not sure i understand what you mean by 'adding one user per time to the roster'; when you register. the transport adds all users to your roster. How this works out depends on the client you use, it might be that it asks you for confirmation on every user. If your client gives you trouble, PyMSN-t provides a web-interface for registration, which will add all roster items with the correct nickname etc. to your roster, without going through your client. cheers, Remko ------------------------------ Message: 2 Date: Tue, 23 Aug 2005 13:56:44 -0400 From: Hal Rottenberg <[EMAIL PROTECTED]> Subject: Re: [jdev] Google and jabber To: Jabber software development list <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 As seen in the article: <blockquote> telnet talk.google.com 5222 Trying 64.233.167.125... Connected to talk.l.google.com. Escape character is '^]'. < ?xml version="1.0" encoding="UTF-8" ?> <stream :stream to="talk.google.com" xmlns="j abber:client" xmlns:stream="http://etherx.jabber. org/streams"> </stream><stream :stream from="talk.google.com" id="C12F7326" xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client"> </blockquote> -- Psi webmaster (http://psi-im.org) im:[EMAIL PROTECTED] http://halr9000.com ------------------------------ Message: 3 Date: Tue, 23 Aug 2005 20:13:50 +0200 From: "Tijl Houtbeckers" <[EMAIL PROTECTED]> Subject: Re: [jdev] Google and jabber To: "Jabber software development list" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 Did anyone with a GMail account and a SASL capable client actually try and log in? (I don't have a GMail account) On Tue, 23 Aug 2005 19:56:44 +0200, Hal Rottenberg <[EMAIL PROTECTED]> wrote: > As seen in the article: > > <blockquote> > telnet talk.google.com 5222 > Trying 64.233.167.125... > Connected to talk.l.google.com. > Escape character is '^]'. > < ?xml version="1.0" encoding="UTF-8" ?> > <stream :stream > to="talk.google.com" > xmlns="j abber:client" > xmlns:stream="http://etherx.jabber. org/streams"> > </stream><stream :stream from="talk.google.com" id="C12F7326" > xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client"> > </blockquote> > ------------------------------ Message: 4 Date: Tue, 23 Aug 2005 20:36:44 +0200 From: Fabio Forno <[EMAIL PROTECTED]> Subject: Re: [jdev] Google and jabber To: Jabber software development list <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=UTF-8 Tijl Houtbeckers wrote: > Did anyone with a GMail account and a SASL capable client actually try > and log in? (I don't have a GMail account) I tried, but the server sends only one stream feature, tls. Once tls is started I should expect a feature like this one (from xmpp-core): <mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'> <mechanism>DIGEST-MD5</mechanism> <mechanism>PLAIN</mechanism> </mechanisms> Instead I get only an empty <feature/> tag and the client hangs ... -- Fabio Forno, PhD Istituto Superiore Mario Boella Jabber ID: xmpp:[EMAIL PROTECTED] ** Try Jabber http://www.jabber.org ------------------------------ Message: 5 Date: Tue, 23 Aug 2005 12:14:59 -0700 From: Chris Chen <[EMAIL PROTECTED]> Subject: Re: [jdev] Google and jabber To: Jabber software development list <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed From what I can tell, after TLS negotiation, Google supports the following mechanisms: PLAIN X-GOOGLE-TOKEN Chris On Aug 23, 2005, at 11:36 AM, Fabio Forno wrote: > Tijl Houtbeckers wrote: > >> Did anyone with a GMail account and a SASL capable client actually >> try >> and log in? (I don't have a GMail account) >> > > I tried, but the server sends only one stream feature, tls. Once > tls is > started I should expect a feature like this one (from xmpp-core): > > <mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'> > <mechanism>DIGEST-MD5</mechanism> > <mechanism>PLAIN</mechanism> > </mechanisms> > > Instead I get only an empty <feature/> tag and the client hangs ... > > -- > Fabio Forno, PhD > Istituto Superiore Mario Boella > Jabber ID: xmpp:[EMAIL PROTECTED] > ** Try Jabber http://www.jabber.org > _______________________________________________ > jdev mailing list > [email protected] > http://mail.jabber.org/mailman/listinfo/jdev > ------------------------------ Message: 6 Date: Tue, 23 Aug 2005 21:34:40 +0200 From: Fabio Forno <[EMAIL PROTECTED]> Subject: Re: [jdev] Google and jabber To: Jabber software development list <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 Chris Chen wrote: > From what I can tell, after TLS negotiation, Google supports the > following mechanisms: > > PLAIN > X-GOOGLE-TOKEN Yes now I can get the mechamisms too. I've tried using plain, my gmail account and talk.google.com as realm with no success :/ -- Fabio Forno, PhD Istituto Superiore Mario Boella Jabber ID: xmpp:[EMAIL PROTECTED] ** Try Jabber http://www.jabber.org ------------------------------ Message: 7 Date: Tue, 23 Aug 2005 21:49:33 +0200 From: Ulrich Staudinger <[EMAIL PROTECTED]> Subject: Re: [jdev] Google and jabber To: Jabber software development list <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed We'll soon know - tomorrow is approaching swiftly! Fabio Forno schrieb: >Chris Chen wrote: > > >>From what I can tell, after TLS negotiation, Google supports the >>following mechanisms: >> >>PLAIN >>X-GOOGLE-TOKEN >> >> > >Yes now I can get the mechamisms too. I've tried using plain, my gmail >account and talk.google.com as realm with no success :/ > > > ------------------------------ Message: 8 Date: Tue, 23 Aug 2005 14:20:42 -0600 From: Dan Cunningham <[EMAIL PROTECTED]> Subject: Re: [jdev] Google and jabber To: Jabber software development list <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 This is what I get (changed myName and myPass from real ones) using my gmail account and PSI <?xml version="1.0"?> <stream:stream xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client" to="gmail.com" > <stream:stream from="gmail.com" id="E454CB10" xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client"> <iq type="get" id="auth_1" to="gmail.com" > <query xmlns="jabber:iq:auth"> <username>myname</username> </query> </iq> <iq from="gmail.com" type="result" id="auth_1" > <query xmlns="jabber:iq:auth"> <username/> <resource/> <password/> </query> </iq> <iq type="set" id="auth_2" to="gmail.com" > <query xmlns="jabber:iq:auth"> <username>myname</username> <password>mypass</password> <resource>Psi</resource> </query> </iq> <iq from="gmail.com" type="error" id="auth_2" > <query xmlns="jabber:iq:auth"> <username>myname</username> <password/> <resource>Psi</resource> </query> <error type="auth" code="403" > <forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> <text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">username or password not correct</text> </error> </iq> On 8/23/05, Ulrich Staudinger <[EMAIL PROTECTED]> wrote: > We'll soon know - tomorrow is approaching swiftly! > > > > Fabio Forno schrieb: > > >Chris Chen wrote: > > > > > >>From what I can tell, after TLS negotiation, Google supports the > >>following mechanisms: > >> > >>PLAIN > >>X-GOOGLE-TOKEN > >> > >> > > > >Yes now I can get the mechamisms too. I've tried using plain, my gmail > >account and talk.google.com as realm with no success :/ > > > > > > > _______________________________________________ > jdev mailing list > [email protected] > http://mail.jabber.org/mailman/listinfo/jdev > ------------------------------ Message: 9 Date: Wed, 24 Aug 2005 00:51:49 +0100 From: Celso Martinho <[EMAIL PROTECTED]> Subject: Re: [jdev] Google and jabber To: Jabber software development list <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed It's Jabber/XMPP, I'm in with my Gmail account confirmed both on iChat, Psi and AdiumX! Slashdot is already reporting that as well and blogs are popping up with info and reports everywhere. This is excellent news for the Jabber community and the Opensource movement in general. I feel happy :) S2S seems closed at the moment and there are no visible agents configured but I'm sure a lot of details will come up on the next hours. Celso. On Aug 23, 2005, at 9:20 PM, Dan Cunningham wrote: > This is what I get (changed myName and myPass from real ones) using my > gmail account and PSI > > > <?xml version="1.0"?> > > <stream:stream xmlns:stream="http://etherx.jabber.org/streams"; > xmlns="jabber:client" to="gmail.com" > > > <stream:stream from="gmail.com" id="E454CB10" > xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client"> > > <iq type="get" id="auth_1" to="gmail.com" > > <query xmlns="jabber:iq:auth"> > <username>myname</username> > </query> > </iq> > > <iq from="gmail.com" type="result" id="auth_1" > > <query xmlns="jabber:iq:auth"> > <username/> > <resource/> > <password/> > </query> > </iq> > > <iq type="set" id="auth_2" to="gmail.com" > > <query xmlns="jabber:iq:auth"> > <username>myname</username> > <password>mypass</password> > <resource>Psi</resource> > </query> > </iq> > > <iq from="gmail.com" type="error" id="auth_2" > > <query xmlns="jabber:iq:auth"> > <username>myname</username> > <password/> > <resource>Psi</resource> > </query> > <error type="auth" code="403" > > <forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> > <text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">username or password > not correct</text> > </error> > </iq> > > > On 8/23/05, Ulrich Staudinger <[EMAIL PROTECTED]> wrote: > >> We'll soon know - tomorrow is approaching swiftly! >> >> >> >> Fabio Forno schrieb: >> >> >>> Chris Chen wrote: >>> >>> >>> >>>> From what I can tell, after TLS negotiation, Google supports the >>>> following mechanisms: >>>> >>>> PLAIN >>>> X-GOOGLE-TOKEN >>>> >>>> >>>> >>> >>> Yes now I can get the mechamisms too. I've tried using plain, my >>> gmail >>> account and talk.google.com as realm with no success :/ >>> >>> >>> >>> >> _______________________________________________ >> jdev mailing list >> [email protected] >> http://mail.jabber.org/mailman/listinfo/jdev >> >> > _______________________________________________ > jdev mailing list > [email protected] > http://mail.jabber.org/mailman/listinfo/jdev > ------------------------------ Message: 10 Date: Tue, 23 Aug 2005 17:40:50 -0700 From: "JD Conley" <[EMAIL PROTECTED]> Subject: RE: [jdev] Google and jabber To: "Jabber software development list" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" > It's Jabber/XMPP, I'm in with my Gmail account Me too... So, do you guys know which server uses hex based ID's like that and supports XMPP? -JD ------------------------------ Message: 11 Date: Wed, 24 Aug 2005 01:49:18 +0100 From: Celso Martinho <[EMAIL PROTECTED]> Subject: Re: [jdev] Google and jabber To: Jabber software development list <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed XCP from Jabber Inc uses hex but it's not the same and I don't think it's XCP or any other server implementation we know. Our best bet here at sapo.pt is that it's their own implementation, highly distributed and scalable like everything else at Google. And we would be very curious to know details about it, of course :) <stream:stream xmlns='jabber:client' xml:lang='en' xmlns:stream='http://etherx.jabber.org/streams' from='sapo.pt' id='185EE2F261' > Google Talk: <stream:stream from="gmail.com" id="E5E6C9A7" xmlns:stream="http:// etherx.jabber.org/streams" xmlns="jabber:client"> On Aug 24, 2005, at 1:40 AM, JD Conley wrote: >> It's Jabber/XMPP, I'm in with my Gmail account >> > > Me too... > > So, do you guys know which server uses hex based ID's like that and > supports XMPP? > > -JD > _______________________________________________ > jdev mailing list > [email protected] > http://mail.jabber.org/mailman/listinfo/jdev > ------------------------------ _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev End of jdev Digest, Vol 19, Issue 26 ************************************ _____ << ella for Spam Control >> has removed 3501 Spam messages and set aside 2250 Newsletters for me You can use it too - and it's FREE! www.ellaforspam.com _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
