<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>El Tramo | Google Talk</title>
  <subtitle>Remko Tronçon's Homepage</subtitle>
  <link href="http://el-tramo.be/blog/tag/google-talk/feed/" rel="self" type="application/rss+xml"/>
  <link href="http://el-tramo.be/"/>
  <updated>2011-12-30T17:00:29+01:00</updated>
  <id>http://el-tramo.be/</id>
  <author>
    <name>Remko Tronçon</name>
    <uri>http://el-tramo.be/about/</uri>
  </author>
  
  <entry>
    <title>Receiving Google Talk files with libjingle</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/psi-googleft"/>
    <updated>2007-02-04T00:00:00+01:00</updated>
    <id>http://el-tramo.be/blog/psi-googleft</id>
    <content type="html">As Google released a new version of &lt;a href=&quot;http://code.google.com/apis/talk/libjingle&quot;&gt;libjingle&lt;/a&gt; last friday, I decided to experiment with their file transfer implementation in Psi this weekend. I added some code that allows someone to accept files sent by Google Talk, and tested it with a few Google Talk contacts, with a perfect success rate (so far). For the brave who wish to experiment with this, see the instructions below. Note that this code is unofficial, untested, only uses a very rudimentary UI (there is no integration with the existing file transfers), still suffers from at least two bugs (on Mac OS X: one that segfaults when receiving images, and one where CPU skyrockets to 100% after a while, which we had with older libjingles as well), and has no support from the Psi developers whatsoever. Comments should therefore go directly to me.

&lt;!--more--&gt;
To compile Google File Transfer support in Psi, get the latest development version from &lt;a href=&quot;http://el-tramo.be/blog/psi-svn&quot;&gt;Subversion&lt;/a&gt;. First, use a custom configure script to configure Psi:
&lt;blockquote&gt;&lt;code&gt;./configure-jingle --enable-google-ft&lt;/code&gt;&lt;/blockquote&gt;
(note that you may need to provide a path to expat). &lt;strong&gt;DO NOT&lt;/strong&gt; enable other Jingle features, as both conflict at the moment.

Next, download and build the new version of libjingle by going into the &lt;code&gt;third-party/libjingle.new&lt;/code&gt; subdir, and executing the following commands:
&lt;blockquote&gt;&lt;code&gt;make -f Makefile.libjingle
qmake
make&lt;/code&gt;&lt;/blockquote&gt;
Finally, go back to the root dir, and build Psi. After the build has finished, your version of Psi should be able to receive files from Google Talk, putting them in &lt;code&gt;~/googletalk_files&lt;/code&gt; (or &lt;code&gt;~/Desktop/googletalk_files&lt;/code&gt; if you are on Mac OS X).
</content>
  </entry>
  
  <entry>
    <title>vCard-based Extended Presence Plugin</title>
    <author>
      <name>Remko Tronçon</name>
      <uri>http://el-tramo.be/about/</uri>
    </author>
    <link href="http://el-tramo.be/blog/vcardextpres"/>
    <updated>2006-10-24T00:00:00+02:00</updated>
    <id>http://el-tramo.be/blog/vcardextpres</id>
    <content type="html">After gathering dust for a few months in some deep and dark corner of my hard disk, my vCard-based Extended Presence plugin for Openfire is now publicly available &lt;a href=&quot;http://el-tramo.be/files/openfire/vcardextpres.jar&quot;&gt;here&lt;/a&gt;.

&lt;!--more--&gt;What this plugin does is add avatar (&lt;a href=&quot;http://www.xmpp.org/extensions/xep-0153.html&quot;&gt;XEP-0153&lt;/a&gt;) and nickname (&lt;a href=&quot;http://www.xmpp.org/extensions/xep-0172.html&quot;&gt;XEP-0172&lt;/a&gt;) information from your vCard to all your outgoing presence packets. This allows clients that do not support setting of vCard-based avatars (e.g. Psi) to still broadcast this information to contacts, such that clients supporting this avatar protocol (basically almost all clients, including the upcoming Psi 0.11) can still see your avatar. This server-side approach is basically what Google Talk does as well. For nickname support, this adds nickname information to presence subscription requests, such that clients supporting the protocol can present the request in a nicer way.

To use this plugin, simply put it in the &lt;tt&gt;plugins/&lt;/tt&gt; dir of your Openfire installation. It should then be listed in the Plugins pane of the admin console. You can then change the settings of the plugin (enable/disable avatars/nicknames) from the first panel in the admin console.
</content>
  </entry>
  
</feed>

