…trying not to become a man of success, but rather a man of value. (Albert E.)
A couple of days ago, my Pidgin wouldn’t connect to ICQ any longer.
It seems that the “lovely” ICQ team pushes people to upgrade their ICQ messenger, or else.. to switch to ICQ.
pidgin.im seems to be down, and there’s no solution anywhere, except for a patch 1. But most of us don’t do ICQ builds every time we pee, so that’s practically of no help. But there’s hope!
Carsten Knobloch to the rescue! He published a compiled liboscar.dll that has the patch. So what you need to do is:
That should do it for Windows. The same post has a solution for Ubuntu as well.
UPDATE: Although pidgin.im is down, it seems that they released 2.4.3 today which fixes the ICQ problem as well. Download it here.
Changelog
* libpurple
o Yahoo! Japan now uses UTF-8, matching the behavior of official clients and restoring compatibility with the web messenger (Yusuke Odate)
o Setting your buddy icon once again works for Yahoo! accounts.
o Fixes in the Yahoo! protocol to prevent a double free, crashes on aliases, and alias functionality
o Fix crashes in the bonjour protocol
o Always use UTF-8 for Yahoo! (#5973)
o Fix a crash when the given jabber id is invalid.
o Make the IRC “unknown message” debugging messages UTF-8 safe.
o Fix connecting to ICQ (#6220)
o Fix a memleak when handling jabber xforms.* Pidgin
o Include the send button plugin in the win32 build
o Various memory leak fixes
Merely a living soul;
mostly one that survives.
Often seeing the best in people;
surely one that dies trying.
value, cherish, criticize, plan, enjoy, think
Alejandro Valenzuela
July 3rd, 2008 at 1:20 am
Sigh, Free (as in Freedom) software developers are not supposed to push people into upgrading more than when it’s really really needed (security problems, etc.). I’m still waiting for the debian pidgin packages to be updated.. I might consider trying another ICQ clone in the meantime.. lazyness..
Andrei Neculau
July 3rd, 2008 at 8:37 am
@Alejandro Valenzuela: The AOL guys are quite far from FREE
But still it’s only the second time this happens.. first time in 2006 if I remember correctly. But I wonder if 2.4.3 was pushed quickly because of this.. it doesn’t feel like a normal update.
Elix
July 3rd, 2008 at 9:58 am
Maybe I’m just stupid, since this is the first time I’ve manually compiled and installed something from source (Ubuntu’s package manager is too kind to me), but I compiled 2.4.3 and it’s still failing to connect on the same error. I also don’t speak German and I’m not sure how to use the source packages on the above link.
Elix
July 3rd, 2008 at 10:05 am
And now ICQ likes me, so upgrading to 2.4.3 does actually seem to work. (I had 2.4.1 before.)
Alejandro Valenzuela
July 11th, 2008 at 3:36 am
@Andrei Neculau, yes, the AOL guys are far from free, but pidgin and libpurple are GPL’ed.
Pidgin is in no way made by AOL people (in fact it was called gaim until some people from AOL didn’t like it).
Luckily the debian packages have been updated now.. at least in debian-testing..
Andrei Neculau
July 11th, 2008 at 8:58 am
@Alejandro Valenzuela: You got it all wrong then!
Pidgin didn’t push for any upgrade. Every protocol “driver” needs to send version of the protocol and of the client when connecting. For instance.. when you log on to Microsoft servers with Windows Messenger there’s one version, with Live Messenger another version.. with the old MSN another version, etc, etc
ICQ servers were probably receiving version 6.0 (Pidgin was impersonating ICQ 6.0), but they found some security issues and demanded people to upgrade to the newer 6.1
Thus, accordingly… Pidgin needed to impersonate ICQ 6.1.. and from 2.4.3 it does.
Alejandro Valenzuela
July 19th, 2008 at 10:06 am
Ah, I see
And I suspect they did it mostly for people to change into 6.1