Mass Whois
mIRC Code
+ 0 likes
Please Register to submit score.
| Average Score | 5.5 |
| Scores Submitted | 2 |
| Date Added | Feb 17, 2007 |
| Last Updated | Feb 17, 2007 |
| Tags | whois |
|
Introduction
However, some information may not be given if your not a IRCOP. i.e IP's and such. Props to defaulrt for helpin with this snippet.
mIRC Snippet:
Mass Whois
Posted on Feb 18, 2007 4:13 am
Posted on Feb 18, 2007 4:13 am
Just some ideas to make this better
- If you\'re not an IRCOP you probably get a flood disconnection too, this needs a queue.
- Some networks support doing whois nick1,nick2,...,nickN, which helps in avoiding flood disconnection. A testrun can determine this.
- A script should not output data requested by other scripts or from command line. So the script has to store the fact it did a whois for a certain nick, and only process the response after checking it has requested it.
- There are alot more raws that can be returned, for which you don\'t have events, they will flood the status window, since not halted.
- Make it multiserver. Put the network name in variables, custom window names, etc.
- If you\'re not an IRCOP you probably get a flood disconnection too, this needs a queue.
- Some networks support doing whois nick1,nick2,...,nickN, which helps in avoiding flood disconnection. A testrun can determine this.
- A script should not output data requested by other scripts or from command line. So the script has to store the fact it did a whois for a certain nick, and only process the response after checking it has requested it.
- There are alot more raws that can be returned, for which you don\'t have events, they will flood the status window, since not halted.
- Make it multiserver. Put the network name in variables, custom window names, etc.
mIRC Snippet:
Mass Whois
Posted on Feb 18, 2007 10:12 pm
Posted on Feb 18, 2007 10:12 pm
Thanks for the info, Qc. I have yet to learn all the raw returns. Ill update this as soon as i can. I\'ll also adjust it so that it won\'t flood disconnect oneself.
mIRC Snippet:
Mass Whois
Posted on Feb 19, 2007 3:52 am
Posted on Feb 19, 2007 3:52 am
Go check on sites, they got all the raw numerics, and most of em are ezplained aswell. Try googling.
mIRC Snippet:
Mass Whois
Posted on Feb 23, 2007 6:42 pm
Posted on Feb 23, 2007 6:42 pm
The quickest and most reliable way to find all the numerics you need is to first turn on debug with /debug -p @debug, and then do a /whois on yourself with IRCop priveliges when you have an SWHOIS set. You can set an SWHOIS for yourself in your operblock; there may also be a way to temporarily set one using the OperServ RAW command (don\'t mess with that if you don\'t know what you\'re doing though, of course).
Also on large channels, it is likely to RecvQ you off. While a SendQ could be prevented by combining it into a /whois nick1,nick2,..,nickN command, this won\'t do anything for your RecvQ, since the server still has to send you the same amount of information. In order to prevent a RecvQ flood on larger channels, you should use timers... PM me if you want specific info on how.
Also on large channels, it is likely to RecvQ you off. While a SendQ could be prevented by combining it into a /whois nick1,nick2,..,nickN command, this won\'t do anything for your RecvQ, since the server still has to send you the same amount of information. In order to prevent a RecvQ flood on larger channels, you should use timers... PM me if you want specific info on how.
mIRC Snippet:
Mass Whois
Posted on Feb 27, 2007 12:40 pm
Posted on Feb 27, 2007 12:40 pm
Why timers?
Just let the last response of the previous /whois command trigger the next. Its then impossible the server sendqueue overflows.
Regarding the server receivequeue, if the sendqueue never overflows, then the receivequeue doesnt either, and /whois nick1,nick2 etc doesnt suffer this problem at all, since the server sends a RAW 416 too many lines in your output, which just stops the responses after that amount, so a part of the passed nicks need to be re-whoissed.
Just let the last response of the previous /whois command trigger the next. Its then impossible the server sendqueue overflows.
Regarding the server receivequeue, if the sendqueue never overflows, then the receivequeue doesnt either, and /whois nick1,nick2 etc doesnt suffer this problem at all, since the server sends a RAW 416 too many lines in your output, which just stops the responses after that amount, so a part of the passed nicks need to be re-whoissed.
