The spelling correction was simply an fyi. It was not intended to 'flame' your ability to spell, or use grammar. I was just letting you know how it was spelled.
As for the restriction to certain commands, there are already /run and /dll restriction built into mirc. Such restriction still haven't stopped trojans and virsuses, how would a socket restriction do so? As I already mentioned, any form of worm or virus installed on a clients computer comes as a package, not a single mrc or ini (or a group of them for that matter). Its almost always an exe that installs a customized mIRC version, configuration, and harmful files. So any and all restriction put onto a task or group of tasks would already be null and void.
Additionally such a restriction wouldn't go far. Why would people download a mirc that comes with all these new handy protections when there is already (several) versions without such protections? The idea of getting version 6.13, 6.3, or even 7.0 just so they can bypass it would be idiotic.
With the url warning box, users who still, at that point, can't see reason enough to not want to continue on to a website with 7 different extensions almost deserves what happens. mIRC gives plenty of warning to the user about opening a url over the internet adnd how it may be harmful. At some point common sense has to enter, and not programmed protections.
