One, a ChanServ BAN module that allows banning of both nicknames and usermasks in the same command. If a nick is given and the nick is not online, it bans nick!*@*, and the same for /cs UNBAN,For the not lazy, /whowas <nick> then ban/akick whichever address(es).
Another is ChanServ MODE, which allows remote setting of modes to a channel. +vhoaq may not be used by this, as there are other appropriate commands which address this.Not sure what you mean here. especially by the phrase "remote setting of modes". If you are referring to something similair to operserv MODE, then it hasn't a place in ChanServ and seems a bit nazi'ish.
Next up, we have ChanServ STAFF, which returns information about online staff and their levels (similar to bs_fantasy_ext, just in private)+1
ChanServ BANS command, which allows remote viewing of a channel's BanList (cmode +b) and Akick List and denotes which is which.1>Some IRCds allow non-opped users to see the banlist already.
2> Speaking as a Channel Owner: If you are the one banned, memo me and we will talk about it. If you are not, then it's none of your business who is banned/akicked. I have the right to ban/akick whom I wish with or without reason. IRC has been run that way since the beginning.
Just my opinion.
The next, an OperServ IRCOP list which restricts /oper privileges to users on that list - if they aren't on the list and identified, OperServ takes their umode +o. OperServ IRCOP ADD/DEL/LIST <nick> - ALL opers have to be on THIS list to /Oper, unless they are on SOper, SAdmin, or SRoot list.Only link to servers who has a trustworthy admin that way you know they wont add users that would need permission to oper up. This also sounds a bit nazi'ish.
Another is the OperServ DEOPER command, used via /operserv DEOPER <nick> - which removes all opermodes from said nick.Completely nazi'ish! Again .. trust. you shouldn't have a reason to deoper another oper unless they go rogue, in which case, ban their oper mask and kill them. This works very well unless you are stupid enough to use and/or allow *@* in oper masks. If you are, then you have much bigger problems.
ns_infospy: Just like +W, it's not really so practical nor useful and can and has caused many problems especially with users/opers that dont know what's really happening.
Some people think that they can be attacked or "/whois flooded". Completely false, a user will be disconnected for filling their sendQ loong before they can flood anything with a /whois request. Not to mention that /whois output comes from the server and not the oper/user. Another myth is that users that /whois an ircop are seeking help .. again, not always true. /ns info and /whois are information gathering tools about users/opers, there is no way to get flooded, attacked nor is it an indication that users need help.
Others believe that by offering help to those that /whois'ed them they are saving bandwidth by immediately addressing the user with assistance, this is also false. Everytime a user /whois's an oper it wastes bandwidth and cpu cycles notifying the oper in question.
/whois oper
<oper> Can I help you?
<user> No.
<oper> Then why did you /whois me?
<user> Because I can.
*close PM window*
Another common use is automated reply scripts ranging from trying to be helpful to retaliation from the oper back on the user.
Bottom line is opers don't really need to know when someone /whois or /ns info's them. it's an invitation for harassment complaints and for paranoid users to think you are spying on them, and rightfully so. In addition, as an oper/admin you have more important things to do with your time other than monitor who is looking at you not to mention there are somethings that happen on IRC that as an oper/admin, you really don't need to know or see unless you're a Nazi!