Colloquy 2.3 mishandles &channel messages with ngIRCd 20.1
Hi again, I know I have the SSL thread open, and I'll get to that in a bit, but this issue is even weirder (and unfortunately harder to work around). After our upgrade to ngIRCd 20.1, users using Colloquy 2.3 basically cannot use server-local &channels. The client renders any public messages sent to those channels as private messages from the sender. In other words, messages that should show up in the &channel pane end up in a private query pane instead. We haven't received any similar reports from other clients, and even Colloquy 2.4 is reported to work correctly, so this seems like a client-specific bug. But this all worked fine in ngIRCd 19.2, so I'm wondering if anyone has any ideas about what might have changed server-side that could trigger this? Thanks in advance, -- Brett Smith
Hi Brett! On Mon, Jan 07, 2013 at 12:17:23PM -0500, Brett Smith wrote:
After our upgrade to ngIRCd 20.1, users using Colloquy 2.3 basically cannot use server-local &channels. The client renders any public messages sent to those channels as private messages from the sender. In other words, messages that should show up in the &channel pane end up in a private query pane instead.
We haven't received any similar reports from other clients, and even Colloquy 2.4 is reported to work correctly, so this seems like a client-specific bug. But this all worked fine in ngIRCd 19.2, so I'm wondering if anyone has any ideas about what might have changed server-side that could trigger this?
So this is quite interesting, and as you already guessed, it's indeed a client bug. And sadly one we can't work around: Colloquy <2.4 seems to have a broken ISUPPORT(005) numeric parser: the only(!) difference that matters concerning this bug is the different value of the "PREFIX" variable in this numeric: v19.x: :irc.test.net 005 nick PREFIX=(ov)@+ v20.x: :irc.test.net 005 nick PREFIX=(qaohv)~&@%+ As soon as PREFIX lists the channel mode character "&", Colloquoy fails in becoming the target of "PRIVMSG &channel :text" commands right. Colloquy 2.4[.1] have been fixed obviously, probably this is related to the following bug report: <http://colloquy.info/project/ticket/2291> -- but I didn't look closer, so this is a wild guess only ... In the end, I don't see much we can do about this: the ISUPPORT(005) numeric that ngIRCd 20.x sends is correct, and the old Colloquoy fails. Hm. Regards Alex
On 01/07/2013 02:33 PM, Alexander Barton wrote:
Colloquy 2.4[.1] have been fixed obviously, probably this is related to the following bug report: <http://colloquy.info/project/ticket/2291> -- but I didn't look closer, so this is a wild guess only ...
In the end, I don't see much we can do about this: the ISUPPORT(005) numeric that ngIRCd 20.x sends is correct, and the old Colloquoy fails. Hm.
Alexander, Thanks for getting back to me. Knowing that this was related to ISUPPORT was helpful; with that information, I was able to track down Colloquy's bug fix at <http://colloquy.info/project/changeset/5351/trunk/Chat%20Core/MVIRCChatConnection.m>. The main thing that tells me is that the Colloquy developers knew that they were fixing this bug in 2.4, which is reassuring. :) Best regards, -- Brett Smith
Teilnehmer (2)
-
Alexander Barton -
Brett Smith