*arrg*
This comes up over, and over, oh, and OVER again, there was a
long-ass rant the last time, and I finally broke down and wrote
the poor mirc users a script that would show them very clearly
the channel name with the characters used, anyone care to dig
it out of the mailfolders and repost?
-poptix
On Sun, Jul 01, 2001 at 12:02:29PM -0700, Diane Bruce wrote:
> G.Miliotis (Corfiot) says:
> > join #<ctrl+k><channel>
> >
> > you can seem to appear as an op in channels using this method when someone
> > does a /whois on you.
> > This goes for inverse and bold. Admittedly a client issue but may cause
> > problems with impersonation of channel ops and a multitude of scripts.
>
> Yep. I have seen this for months on EFNet as well. Its also how they
> join #2,000 ...
>
> >
> > Maybe the low end of the ascii codes should be stripped from channel names?
> > This would of course not affect foreign language channel names, at least in
> > my opinion nor break any clients.
>
> Well, channels are supposed to be iso-8859. Masking the 8 bit code
> to iso-8859 limits would help, but then thats a scan through of every byte
> of the channel name. Not a good idea. It surely seems a better idea to
> have the client coders add some means of being able to see that these
> are high bit chars instead of mucking ircd. Moreover, even if you did
> strip, you'd have to change all servers at once, or you would have people
> unable to join some channels listed that are legitimate.
>
>
> - Dianora
>
> --
> Diane Bruce, http://www.db.net/~db [EMAIL PROTECTED]
> --- I got bored with the last witty aphorism.
