Are you really complaining that someone is stopping people from distributing insecure code? Not merely "insecure" in the sense that someone with 3 days and a lot of knowledge could break something, but rather "insecure" in the sense that a single crafted string that's really very easy to figure out could be delivered to thousands of people at once via IRC and do anything from open them up to trojan infections to start deleting everything on their hard drive.
All of the security exploits we're talking about are vulnerable in the same way to the same strings, they're all vulnerable from text passed into wherever the script is taking text from (which is very often channels) - this stuff is a script kiddie's wet dream.
The idea that you're going to bitch because someone is trying to stop people spreading code that has these gaping holes in it is ridiculous.
It's not even like there's something really complicated going on here, all you need to do is remember that /timer, /scid, and /scon (when used with the command parameter) are evaluated twice. Even if people can't wrap their heads around how to avoid the issues that causes they can at least accept that those commands are playing with fire and not supply code which makes use of them.
