2 questions about

[Nwod]

Hi all!

There is 2 troubles with PtokaX 0.3.3.21 for Windows XP/2K/NT i've got.

First one: hub does not allow user to log in when there is * in his nick, even when "check nick names" in PtokaX's settings is disabled. Hub just sends " Your nick contains illegal characters! Please correct it and get back again" and disconnects user. But previous versions of PtokaX allowed using *. Why does not 0.3.3.21?

And second one: hub disconnects client StrongDC++ RC10 every time i force it to refresh user-list by command in drop down menu. All other clients (DC++, oDC++, DCDM++) refresh user list without any problems. I watched commands in PtokaX's users/chat, but it is the same $GetNickList at any case. Is this bug in StrongDC?s protocol realization, and if so what exactly incorrect?

P.S. Sorry for my bad English.

[bastya_elvtars]

Originally posted by Nwod
First one: hub does not allow user to log in when there is * in his nick, even when "check nick names" in PtokaX's settings is disabled. Hub just sends " Your nick contains illegal characters! Please correct it and get back again" and disconnects user. But previous versions of PtokaX allowed using *. Why does not 0.3.3.21?

You can not download the filelist of a user whose name contains such characters, this cannot even be switched off. Try to create a file in Windows with * or : in the file name. And, if you can not download filelist, then why should the user be in the hub at all?

Originally posted by Nwod
And second one: hub disconnects client StrongDC++ RC10 every time i force it to refresh user-list by command in drop down menu. All other clients (DC++, oDC++, DCDM++) refresh user list without any problems. I watched commands in PtokaX's users/chat, but it is the same $GetNickList at any case. Is this bug in StrongDC?s protocol realization, and if so what exactly incorrect?

Play with Deflood/GetNickList settings, StrongDC seems to have some weird GetNickList bug that is considered as flood in PtokaX, I have also experienced this.

[PPK]

Originally posted by Nwod
And second one: hub disconnects client StrongDC++ RC10 every time i force it to refresh user-list by command in drop down menu.

1 ) Here is no reason to waste badwith with refreshing userlist.
2 ) StrongDC++ have Quicklist support and this support not allow userlist refresh.

[Nwod]

bastya_elvtars I've just checked - when i download list from * user all of * change to _ and there is no problem.

And Deflood/GetNickList is disabled at my hub.


PPK Did i understand you right: if a client supports Quicklist it should not allow user to refresh userlist? So StrongDC's author should disable this feature at all? But what to do if a hub does not have Quicklist support?

[bastya_elvtars]

Originally posted by Nwod
bastya_elvtars I've just checked - when i download list from * user all of * change to _ and there is no problem.

Still it can cause problems... PPK had a good reason to disable it,

[PPK]

Originally posted by Nwod
when i download list from * user all of * change to _ and there is no problem.

Yes your client change it, but here is very much other clients...

Originally posted by Nwod
if a client supports Quicklist it should not allow user to refresh userlist?

Yes, $GetNickList is allowed only once on login.

Originally posted by Nwod
So StrongDC's author should disable this feature at all? But what to do if a hub does not have Quicklist support?

Is easy to check if hub support QuickList or not and allow or disallow refresh )

[Nwod]

Yes, $GetNickList is allowed only once on login.

StrongDC's author fixed this, thanks!