<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"
xmlns:dc="http://purl.org/dc/elements/1.1/"
>
    <title>deep darc » Google Talk</title>
    <link rel="alternate" type="text/html" href="http://www.deepdarc.com/category/google-talk/" />
    <id>category:google-talk</id>
    <subtitle>deep and darc stuff</subtitle>
    <updated>2006-11-01T21:45:09Z</updated>
    <rights>Copyright 2005</rights>
    <generator version="0.2">darcness</generator>

        
        <entry>
            <title type="html"><![CDATA[Honeymoon is over]]></title>
            <author>
                <name>darco</name>
            </author>
            <link rel="alternate" type="text/html" href="http://www.deepdarc.com/2006/10/27/honeymoon-is-over/" />
            <id>http://www.deepdarc.com/2006/10/27/honeymoon-is-over/</id>
                            <updated>2006-10-28T01:15:56Z</updated>
                                        <published>2006-10-28T01:15:56Z</published>
                                                <summary type="html"><![CDATA[<p>I don't want to seem unappreciative, so I'll start out with some good points. <a href="http://www.google.com/talk/">Google Talk</a> has energized <a href="http://www.jabber.org/">Jabber</a>/<a href="http://www.xmpp.org/">XMPP</a> to a level of activity that is unprecedented. Think about all of the things that have happened since Google Talk went beta: how much of it is a direct or indirect result of Google choosing to use XMPP as the protocol for their IM service? I don't want to minimize this point. Google Talk has been one of the best things to happen to the Jabber community in recent memory. And kudos to them.</p>

<p>Ever since Google Talk <a href="http://googletalk.blogspot.com/2006/01/xmpp-federation.html">flipped the switch</a> to enable server-to-server communications, Google Talk has become <a href="http://www.deepdarc.com/2006/05/19/full-time-jabber/#use-jabber">my default recommendation</a> for anyone looking to get a ‘jabber account’. Back then, <a href="http://www.jabber.org/">jabber.org</a> was still having stability problems (as it was still running <a href="http://jabberd.jabberstudio.org/1.4/">jabberd 1.4</a>), and <a href="http://jabber.deepdarc.com/">my own server</a> was also less than reliable. Google Talk also came with several useful features, such as the <a href="http://www.google.com/talk/about.html#withgmail">chat client built right into gmail</a>.</p>

<p>However, I have recently realized that Google Talk is not the ideal, stable jabber server that I thought it would be. Read on to find out why.</p>

<p><strong>UPDATE:</strong> (2006-11-01) <a href="http://googletalk.blogspot.com/2006/11/offline-messages.html">Google Talk now supports offline message delivery</a>!</p>

<div><a href="http://www.deepdarc.com/2006/10/27/honeymoon-is-over/">Read the rest of this entry &raquo;</a></div>
]]></summary>
        </entry>
        
        <entry>
            <title type="html"><![CDATA[Google Talk Supports vCard Avatars]]></title>
            <author>
                <name>darco</name>
            </author>
            <link rel="alternate" type="text/html" href="http://www.deepdarc.com/2006/03/31/google-talk-vcard-avatars/" />
            <id>http://www.deepdarc.com/2006/03/31/google-talk-vcard-avatars/</id>
                            <updated>2006-03-31T17:42:10Z</updated>
                                        <published>2006-03-31T17:42:10Z</published>
                                                <summary type="html"><![CDATA[<p>I just noticed yesterday that Google Talk now seems to support <a href="http://www.jabber.org/jeps/jep-0153.html">vCard avatars</a>! Apparently, they support pretty much nothing else about <a href="http://www.jabber.org/jeps/jep-0054.html">vcard-temp</a>... but hey, at least I no longer have to keep explaining to my friends why their avatars don't work with their gmail accounts. <img src="http://www.deepdarc.com//images/smilies/1.png" alt=":)" style="border: 0; margin-bottom: -4px;" /></p>

<p>Just a reminder to everyone: I'll be <a href="http://www.deepdarc.com/2006/02/27/goodbye-legacy-im/">dropping my accounts</a> on AIM, MSN, ICQ, and YIM on May 19<sup>th</sup> of this year, and switching entirely to Jabber. So grab yourself a gmail account if you don't already have a jabber account!</p>
]]></summary>
        </entry>
        
        <entry>
            <title type="html"><![CDATA[Google Talk Federates!]]></title>
            <author>
                <name>darco</name>
            </author>
            <link rel="alternate" type="text/html" href="http://www.deepdarc.com/2006/01/17/google-talk-federates/" />
            <id>http://www.deepdarc.com/2006/01/17/google-talk-federates/</id>
                            <updated>2006-01-17T17:45:54Z</updated>
                                        <published>2006-01-17T17:45:54Z</published>
                                                <summary type="html"><![CDATA[<p><a href="http://ralphm.net/blog/2006/01/17/gtalk_s2s">It would appear</a> that <a href="http://talk.google.com/">Google Talk</a> has has not only <a href="http://www.simplicidade.org/notes/archives/2006/01/telnet_federati.html">begun testing Server-to-Server communication</a> with the <code><a href="xmpp:google.com">google.com</a></code> domain, but also <a href="http://www.deepdarc.com/2006/01/17/google-talk-federates/#comment-266">enabled S2S communication</a> for <code><a href="xmpp:gmail.com">gmail.com</a></code>! This should be the major turning point for <a href="http://www.jabber.org">Jabber</a> adoption. It's time to take over the world. <img src="http://www.deepdarc.com//images/smilies/7.png" alt=":D" style="border: 0; margin-bottom: -4px;" /></p>

<p><strong>UPDATE</strong>: <a href="http://googletalk.blogspot.com/2006/01/xmpp-federation.html">Official Announcement</a> | <a href="http://groups.google.com/group/google-talk-open">Official Discussion Forum</a></p>

<div><a href="http://www.deepdarc.com/2006/01/17/google-talk-federates/">Read the rest of this entry &raquo;</a></div>
]]></summary>
        </entry>
        
</feed>
