ok, Conference Room IRCd's report /names as Nick!User@Host so that people dont /who the server to fill their IAL list.. mIRC handles this fine when populating the nicklist but an actual /names #chan only returns one or two nicks SOMETIMES!

mIRC Output:
#hamilton5 @Talon
#hamilton5 End of /NAMES list.

Debug Output:
<- :glass.webchat.org 353 Talon = #hamilton5 :@Talon!Talon@=igvbyuerfm.raex.com @Tr[a]visK!Travis_jk@=kUp-48-8-673-77.hsd1.tx.comcast.net @digits!digits1_9@=4ithgx-55-603-335-416.buff.east.verizon.net @Hamilton5!KiLLeR@=nz43-594-757-6.client.mchsi.com
<- :glass.webchat.org 366 Talon #hamilton5 :End of /NAMES list.

Confirmed.

I blame Cobra^

Conference Room is terrible these days, i don't think i can name one advantage of any of the "added features" except for /kick now being able to use *!*@* format. I wouldn't be surprised if they start calling it something other than IRC software soon, because it barely is.

Mark used to say it was 100% RFC compatible a year ago, then the last time I asked, Mark said it wasn't and never was...

mIRC depends on the IRC server to be consistent with its replies, so if for some reason the IRC server provides incomplete information there's very little that the IRC client can do. I would suggest that you contact the IRC server coder and point out the issue to them.

I'm really confused by this bug report. Did you do the /NAMES when you were IN the channel? If you're not in the channel, some things are hidden (e.g. users that are +i)

I tested this for almost 20 minutes, and I haven't seen any problems with the functionality at all. As far as I can tell, CR is perfectly consistent.

A brief sidenote to the person that mentioned RFC compatibility. We try not to break things that make it impossible for clients to connect to us, but nowdays, you won't find many servers that stick to the RFC. Our server-server stuff is not RFC-compatible and doesn't need to be. But that you can connect with mIRC and a half dozen other clients means we are compatible.

nikb

P.S.: I laugh at thee, for having your forums mark me as a "newbie" :P

Default positioning for anyone that has (as of when I looked at your post) only one posting. It means that you're a newbie related to the number of postings that have been made, not that you're a newbie to IRC, mIRC, scripting, or anything else that you might want to fill in there.

Taken from the forum FAQ.

0 to be ranked stranger
1 to be ranked newbie
50 to be ranked journeyman
100 to be ranked member
200 to be ranked enthusiast
400 to be ranked addict
700 to be ranked old hand
1200 to be ranked veteran
1600 to be ranked Pooh-Bah
2500 to be ranked Carpal Tunnel

-Andy

No, this is when /names is used while currently in the channel.

For instance, i do /names #help.mirc while in the channel, and mirc shows:



however, when i check what the server actually sent, using /debug, i get this:



So something isn't working right.

It was a joke Thanks for the reply.

-n

I went over the code again, and I don't see any issues with CR. This is somewhat perplexing. I'll go over the code again though,

-n

The problem is as Talon said, CR sends the names list in Nick!User@Host format, whereas usually its done in just nickname format.

It does so after sending "UHNAMES" in protoctl and getting a "UHNAMES" back from mIRC, which indicates support for n!u@h mask.

So, while 6.17 and later will get <level>n!u@h, 6.16 and earlier versions will get simply <level>nick.

Similar with NAMESX, which allows the server to send all levels (e.g. "@+nikb!nikb@staff.webchat.org" instead of simply "@nikb!nikb@staff.webchat.org"

Could I ask you to test this using arena.webchat.org, which runs a slightly newer build than the rest, and reports UHNAMES and NAMESX in its 005, because, I still don't see anything wrong with the CR side of this but obviously there's an issue somewhere -- whether it's in the output of CR, or in mIRC's parsing -- which must be addressed.

-n

Yep, it seems it is indeed a mirc issue.

After testing with nikb we found that (as stated above) CR checks wether mirc supports the n!u@h format, then sends all info correctly:



mIRC has no problems when loading the nick list for the channel, only when displaying it otherwise.

Thanks for checking it out, this has been fixed for the next bugfix release.

Thank you.

-n

SURE why not, blame Cobra^ ....

/me grumbles

lol

Cobra^