TOPIC:

you, you're totally right there

at least saved me the work of repeating the exactly same words

Guys, I didn't wanted to react on this topic, but now I guess I should:

Few Points:

1: IF The_Dude was trolling he got you guys now EXACTLY where he wanted: reacting pissed off on his messages. To be honest I don't think that he was trolling, so please, don't feel so "attacked".
2: These discussions can also be done on IRC which is MUCH more efficient (since people can react directly) and not for everyone to see, so please continue there if you still have something to say.

I am tempted to just delete all messages in this topic although I realise it's already to late for that. I think we are all grown ups here right? So please: Just cut the crap (from both sides), no matter who is right in this case alright?

Thanks!

no firewall on my side -- the "autologin" does not work.

i tried to manipulate .cfg -- did not help.
something is wrong here, maybe, just maybe, a password is encripted inaccurately, or is not sent at all (i didn't dig into network traffic).

also i noticed quite few very nasty warning during compilations, including not initialized values and malforpmed printf's format.

stop swearing all!

the reason was the client did not URLencode username and password.

if you have spaces or % or = or & or ? in your username or password, please URLencode them manually before input them to the client.

for alphanumeric username-password pairs autologin is indeed working, and this caused the flame.

I ran into the same problem. It is fixed in the n-ice client for ages(at least since version 1.3.3).
I'm pretty sure I warned ST2 about this issue when I fixed it. But it seems to have gone ignored.

well, I don't recall being warned about it therefore not ignored, but yes, it's an issue.
I'll fix it when have time to put my hands on it (found the solution , similar as used in n-ice client).
Maybe a week or so to change it and be verified -> compiled -> published.