Opened at 2006-02-14T10:34:21Z
Closed at 2006-03-16T19:44:51Z
#101 closed defect (worksforme)
ICQ protocol change
| Reported by: | Owned by: | Jelmer Vernooij | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | OSCAR | Version: | 1.0.1 |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Public server |
| OS version/distro: |
Description
12th Feb 2006 + ICQ protocol fix. In the past few days, AOL changed the ICQ protocol a bit, that way disabling a lot of clone clients. This fix re-enables ysmICQ. Have fun!
Are bitlbee aware of protocol change?
From ysm changelog (http://cvs.sourceforge.net/viewcvs.py/ysmv7/ysmv7/ChangeLog?rev=HEAD&content-type=text/vnd.viewcvs-markup): 12th Feb 2006 + ICQ protocol fix. In the past few days, AOL changed the ICQ protocol a bit, that way disabling a lot of clone clients. This fix re-enables ysmICQ. Have fun!
Attachments (0)
Change History (6)
comment:1 Changed at 2006-02-14T11:57:41Z by
comment:2 Changed at 2006-02-14T12:25:42Z by
13:20:17 Err| Wilmer: we have yet to see *any* evidence that the "oscar
protocol change" affects gaim
Same for BitlBee. Since Gaim is used by a *lot* of people, they should've had enough reports about it by now, if they were affected. So I guess it's the same thing for BitlBee. I'll leave this thing open for now, maybe Jelmer can confirm this with some quick analysis of the patch from ysmICQ.
comment:3 Changed at 2006-02-14T12:44:39Z by
May be better to contact ysm developer because with patching this there are a bit of other changes. I look into patch and can't guess where what is.
Anyway i dropped using bitlbee - can't solve troubles with reception of russian messages in erc.
comment:4 Changed at 2006-02-24T14:42:28Z by
Ivan, look here, bitlbee works fine with russian messages.
comment:5 Changed at 2006-02-27T08:05:02Z by
The link doesn't work, but I *think* Ivan has more trouble with getting the Russian characters work with his Emacs-ERC client.
comment:6 Changed at 2006-03-16T19:44:51Z by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
I'm still not sure about this. Nobody reported problems about it yes, and there's nothing about it in the topic of #Gaim (while usually they have it filled up with all current problems). So maybe libfaim doesn't have this problem.
Until someone reports BitlBee actually *has* this problem, I don't know what to do...