> > Since u2.10.11.03. Because these channel names have been abused in an
> > attempt to make the abuser appear to be an official. This will not be
> > changed. No, the RFC says nothing about these characters in a channel
> > name being illegal.
>
> I thought colors were a client thing and not
On Fri, Jan 03, 2003 at 01:20:43PM -0500, Kev wrote:
>
> > When trying to join channels with ascii character 3 in the name, I now get a
> > 'cahannel does not exist' error. Since when? How come? Will this be fixed?
> > The RFC doesn't seem to say anything about any channel names being illegal.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 03 Jan 2003 4:54 pm, The Storm Surfer wrote:
> a 'cahannel does not exist' error. Since when? How come? Will this be
> fixed? The RFC doesn't seem to say anything about any channel names being
> illegal.
It's not going to be "fix
> When trying to join channels with ascii character 3 in the name, I now get a
> 'cahannel does not exist' error. Since when? How come? Will this be fixed?
> The RFC doesn't seem to say anything about any channel names being illegal.
Since u2.10.11.03. Because these channel names have been a
The Storm Surfer wrote:
>
> When trying to join channels with ascii character 3 in the name, I now get a
>'cahannel does not exist' error. Since when? How come? Will this be fixed?
ircu on undernet checks for such characters (mirc control characters)
and disallows them, because they can be
When trying to join channels with ascii character 3 in the name, I now get a 'cahannel
does not exist' error. Since when? How come? Will this be fixed?
The RFC doesn't seem to say anything about any channel names being illegal.
