Chuck

cool

"so baiscly u dont need to write a conn ... just get the ticket" That depends what you are doing. Standard mirc connection won't parse listview correctly under CLIENTMODE cd1. But you don't need to write a connection if you are not using cd1 mode. btw, don't post uticket info. If above is the correct one then change your password now.

About ircop account flag, it has not been implemented yet, but soon in an upcoming update server will switch to that instead of ^. What I've done to keep it compatible with the updates in my client is to check the length of the flags string, if it is 4 then it ignores the account flag, if it is 5 then last char is used for the account type. I'm tokenizing the irc messages by space, so this method works best for me. btw, good work

language is now en, there will be another property for country that will be in iso format too.

I'll check it out later, maybe it is sending nameslist in ircwx format with join only.

Once, preferably after connection is made.

before joining send /raw CLIENTMODE cd1 that will turn off the standard irc backward compatibility mode for the client connection, which will send you the info you need. Flags: 1. Away/unaway U/A 2. Male/Female/Unsepciefied M/F/U 3. Photo/Non P/N 4. +voice/-voice V/N 5. User/Guide/Sysop/Admin U/G/S/A (not implemented yet)

Well that is normal for any software, it is part of the development cycle... bugs are discovered and patched. mirc had a buffer-overflow issue too.

msn ocx had security issues too and much worse, for example: it was possible to crash the whole browser and sometimes that crashed windows too, buffer-overflow issues, cloning, unkickables, etc... So far we had no critical security issue like buffer-overflow. And any security issue that was rated as high was patched within 24hrs.

Basically it is Microsoft's version of flash. It is supposed to be released as RTM in early 2008. And we have one webchat ready in silverlight too for IRCwx server

I think those tools are made by Koach, some must having used on msn chat. Looks like they are being used on Koach's server. I can see some names that stay on Koach's server.

1. you need to send it in hex, not bytes. If you are using mirc then current version has md5$ function. 2. don't post your session info in public.

Client is based on html, javascript, css, flash, xml, and asynchronous calls. Programmers are not bothered to give it a specific name, but ajax comes close. If anyone wants to give this kind of programming a specific name, be my guest. ************************************* I agree that AJAX and XForms will be used in conjunction. However, this blog explains better what I meant: Here is an article that goes into more detail: http://www.oreillynet.com/xml/blog/2006/03..._revisited.html ************************************* Actually, it isn't secure compared to ajax or something similar. 1. It may work for well known companies like Yahoo, MSN, and Adobe, but signed code can be from wrong publishers and still it will have trust issues since once activex control is accepted it gains direct access to windows api. This is not an issue with javascript in webbrowsers since it is built to work without signing and thus puts security limitations on commands that can be sent through javascript. Here is an example of activex issue that I'm talking about: 2. Another problem that comes from direct access to windows api by activex controls is that if there is a security exploit like buffer-overflow then an attacker can use it to take over the computer of a user. This is mitigated with the use of javascript in popular webbrowsers and components build on popular activex based runtime like flashplayer because they are used by millions of users, therefore, these kind of exploits will be discovered and patched very quickly compared to custom developed activex control that would be used by comparatively much less users. I hope that makes it more clearer.

First, that was a server side issue and not related to ajax. Second, guests were banned because server had to take the load of 36,131 page views per hour and irc server had to take 1,900+ concurrent connections, so guest flooders were a nuisance at that time. Web server, database server, and irc server were running on the same machine so for beta load test the results were pretty good. Like you said we'll see the stability and reliability of the system as the development progresses and more load tests are done

No offence, but that was hilarious . Ocx has full access to windows API, once a user accepts to run it. AJAX client is no more than javascript & xml/xhtml code running in a browser. Best answer was given by Director of Engineering of the Mozilla Foundation. here is another quote: Another thing ajax is not really a new technology, it is a name given to the new style of use of old technologies. Javascript, xml, x/html, and http asynchronous calls didn't came into existence with ajax, people just combined them for better webapps and called it ajax. Btw, W3C is officially standardizing AJAX style of programming in the form of XForms ( http://en.wikipedia.org/wiki/XForms ). But at the moment no browser natively supports XForm specification. Firefox has an extension, so perhaps firefox will be the first one to properly support it. Maybe XForms will replace Activex browser controls.