CrazyEgg wrote:
1.some ctcp control on connect like version(if has or not).Flood bots have not version reply.better a 30 seconds delay on connect and more secure network)
You are wrong, flood bots - drones CAN have version and some of them have, they can have any version they want to tho. So, CTCP VERSION on connect is useless. You can't even protect a channel name with ctcp on join, do not talk about controling a whole network.
CrazyEgg wrote:
2.control over nick/ident for random characters with heuristics detection algorithm or with someone else logical algorithm
3.remove posibility to use characters like { } [ ] \ / _ to nick or ident.(more work on X settings to read that)
Well, / is not allowed to be used in nickname, anyway, I will recommend you to read RFC 1459 -- the IRC protocol which IRCu is based on. So, feel free to ban those chars in your channels if you think that will protect you from drones or you just don't want people with those chars in your channel.
CrazyEgg wrote:
4.drone scan bot "e" can easyly make with delay test every connect ip for proxy(sock4,5 connection) or proxy via http connection with testing over web and g-line if positive(tools exist on gnuworld).
E is just the mod.dronescan -- feel free to check the GNUWorld source for what it does, it just sends warnings to a defined channel. Here's an example:
[W] #test is being join flooded.
[W] Join flood over in #test. Total joins: 20. Total size: 500
etc. Btw, Undernet is using pxys as a proxy scanner, feel free to check
http://pxys.sf.net/ about it.
I really don't think that any of these ideas will be useful.
Best regards,
Mit.