Franks Homepage

About a year ago I wrote about QQ with Kopete. It didn't work at that time and it does not work now. As I switched to OpenSolaris and KDE is not really usable here, I switched to Gnome, too. And so I switched to Pidgin, too.

I miss some Kopete features, but other things work better in Pidgin. Sadly I QQ is not one of them. So QQ is neither working in Kopete nor in Pidgin. Is there any working open implementation of a chat client for QQ out there?

I understand that even Chinese people are using MSN/WLM for foreign contacts, but is open source unimportant in China? All of them Windows User?

Today I tried to make the QQ protocol in Kopete under KDE 4.2 work. As I saw it, it has been ported from evaq some time ago. evaq stopped development in 2006! Since then Tencent stopped supporting different protocol versions. So the Tencent networks complains of a too old client version when Kopete tries to connect. A bug of this is already filed in November, but it's not even confirmed, yet. There is even a bug filed in June what IMHO tells a different part of the same story. This bug isn't confirmed, either.

Today I pulled the svn version of evaq and tried to port the QQ 2006 code to connect to the network. I had some success as the error message for a too old client disappeared. But I couldn't get a real connection to QQ. I guess there is some work to do on this plugin. But I'm not experienced in KDE programming.

Pidgin somehow had some luck to find a maintainer who cares and its QQ implementation is still working. Unfortunately it isn't just copy & paste from Pidgin to Kopete.

Where are all those Chinese people around there? Nobody using KDE? Nobody caring about QQ and Kopete?

Wenn jemand eine deutsche Übersetzung braucht, einfach Bescheid sagen.

I read a guide how to syncronize a Nokia 6630 over bluetooth with opensync and syncml. I tried to do the first pair "filenokia" at first. Othe than that guide states you have to change a bit more while doing

$ msynctool --configure filenokia 2

all the bold things I had to change

<bluetooth_address>XX:XX:XX:XX:XX:XX</bluetooth_address> 
<bluetooth_channel>YY</bluetooth_channel> 
<identifier>PC Suite</identifier> 
<version>1</version> 
<wbxml>1</wbxml> 
<username></username> 
<password></password> 
<type>2</type> 
<usestringtable>1</usestringtable> 
<onlyreplace>0</onlyreplace> 
<recvLimit>10000</recvLimit> 
<maxObjSize>0</maxObjSize> 
<contact_db>Contacts</contact_db> 
<calendar_db>Calendar</calendar_db> 
<note_db>Notepad</note_db> 
</config>

After that the sync with filenokia works better than expected. Now for the harder part - sync with kdepim.

Its like the described setup for evolution, but instead of adding the evo2-sync plugin we do

$ msynctool --addgroup kdepimnokia  $ msynctool --addmember kdepimnokia kdepim-sync  $ msynctool --addmember kdepimnokia syncml-obex-client

The kdepim-sync doesn't need any configuration. So we can skip that part. The final test

$ msynctool --sync kdepimnokia

works until it wants to write back to the phone. Unluckily there are some error messages, which I couldn't solve yet. But at least its a good start...