Irc Commands:
NickServ - The Basics
Info
USAGE: /NickServ INFO nick-NickServ- Info for Nick1:Use this command to find out information about a registered nick. This information includes their last seen address (unless they are currently on IRC) and when they last left. It includes when they registered that nick and what time it is now (both in GMT, Greenwich Mean Time). The next lines (if present) show different settings that can be set on the nick (URL, KILL, and a special settings to prevent very high DALnet administration nicks from ever expiring).
NOTE: The "Last seen time" represents the last time the nick was identified to NickServ.
EXAMPLE: /NickServ Info Nick1
-NickServ- (Currently on IRC) For extra info: /whois Nick1
-NickServ- Last seen address : ~userid@ppp-365.some.isp.net
-NickServ- Last seen time : Mon 08/02/1999 20:20:58 GMT
-NickServ- Time registered : Sat 02/07/1998 09:40:15 GMT
-NickServ- Time now : Mon 08/02/1999 20:22:33 GMT
-NickServ- URL : http://www.some.isp.net/~nick1/
-NickServ- This user has enabled nick kill enforce.
-NickServ- This user will not receive memos
-NickServ- *** End of Info ***
Register
USAGE: /NickServ REGISTER password email@addressUse this command to reserve a nickname for your use by registering it with NickServ. Also, it adds a single mask in your nick's access mask in the form *userid@*.domain or *userid@12.34.56.*. You must include a valid email address; when you register your nick, an email is sent to you by services containing an AUTH command which you must issue to complete the registration.
EXAMPLE: /NickServ REGISTER q59H39tF2bb nick1@u.dal.net
-NickServ- The nick Nick1 has been temporarily registered to you.
-NickServ- A short message has been sent to the email address you provided
-NickServ- with simple and quick instructions on how to permanently register
-NickServ- this nick. You won't be able to modify this nick's setting or send
-NickServ- memos until you follow the instructions within the email. This nick
-NickServ- will expire in 24 hours if the email instructions are not completed.
Auth
USAGE: /NickServ AUTH nick Authorization NumberThis command is used when you have registered your nick or changed your email address for your nick.
Below is an example email from services when you register your nick. Note that there are two ways to complete the registration process. One is by issuing the AUTH command while on DALnet. The other doesn't even require that you be on DALnet at all. Just surf to the web page given and your nick will be fully registered!
From::: DALnet User Registration To::: Nick1 Subject::: Welcome to DALnet!
Nick1,
You are recieving this message as part of an automated nickname
registration system on the DALnet IRC network. If you did not request
this service, you may simply ignore this message.
---------------------------------------------------------------
Thanks for registering your nickname on DALnet. To complete
the registration process, simply type the following command next
time you visit us:
/msg NickServ AUTH Nick1 6169401955453888
OR you can visit the following URL:
http://users.dal.net/cgi-bin/verify.cgi?nick=Nick1&id=6169401955453888
That's it! After entering the above command or clicking on the
above URL, you'll be able to change your nick options, send memos
to other users, and make use of DALnet's registered user site at
http://users.dal.net which includes free email and a free web site.
Please take a moment right now to write down your nick password.
The password you chose is: q59H39tF2bb
Keeping your password secure is your responsibility.
Please take the necessary precautions to keep others from obtaining
this information.
If you ever need to change your e-mail address, please use the
'/msg NickServ set email' command. It is your
responsibility to keep a valid email address with services at all
times should you ever need to recover your password.
DALnet has made a commitment to its users not to sell or
distribute any email addresses. For a detailed letter from DALnet's
CEO on the topic, visit http://www.dal.net/emailinfo.html
Thanks again for making DALnet your choice. :)EXAMPLE: /msg NickServ AUTH Nick1 2349084362984750
EXAMPLE: /msg NickServ AUTH Nick1 2349084362984750
EXAMPLE: /msg NickServ AUTH Nick1 2349084362984750
-NickServ- Mission accomplished! The nick Nick1 is fully
-NickServ- registered. You now have access to change your nick
-NickServ- settings, send memos to other users and use DALnet's
-NickServ- registered user web site at http://users.dal.net
-NickServ-
-NickServ- Thanks for making DALnet your choice! :)
Identify
USAGE: /NickServ Identify nick passwordThis command is used when you get on IRC to identify to NickServ for your nick; in this way, NickServ knows that you are supposed to have access to that nick and everything that the nick implies (ops in places, status in channels).
If you want to identify for a nick you're not currently using (perhaps to identify for a founder's nick to change some channel settings), you can include the nick between the identify and the password.
EXAMPLE: /NickServ IDENTIFY q59H39tF2bb
EXAMPLE: /NickServ IDENTIFY Nick1 q59H39tF2bb (if you're not using Nick1)
-NickServ- Password accepted for Nick1.
An access mask lets you add multiple allowable addresses you can use to use that nick. For example, if you wanted to allow yourself access from three different ISPs, you could add a mask (or 2) for each address mask you commonly use. If you have set KILL ON for your nick, you will not be asked for your password (in 60 seconds) if your current access mask matches one found in your nick's access list.
These masks, unlike a normal mask on IRC, do not include the nick; obviously, NickServ knows which nick is under discussion. That means that the only parts of the mask that need be included are the userid and the host.domain, any part of which may contain wildcards. It takes the form *userid@*.host.domain or *userid@12.34.56.*, where the * means any character(s).
CAUTION: Putting an unsecure mask (like *@*.*) in your access list will allow anyone to use your nick.
CAUTION: ANYONE who exactly matches an address mask in your access list can use your nick. This means that anyone who is using your userid and ISP can use your nick (usually), unless you have a static (unchanging) IP address assigned to you by your ISP. If you use a BNC (a unix bounce used to hide your real address) which uses a virtual (fake) host (vhost), anyone who uses that same vhost can switch to your userid and use your nick if that vhost is in your access list.
Use this command to add a mask to your nick's access list. This is desirable when you use more than one ISP or a BNC (a way to use a unix shell process to hide your real named/IP address) so that NickServ won't keep asking you for your password (changing your nick to Guest#####) should you have set KILL ON for your nick.
EXAMPLE: /NickServ ACCESS ADD *!*userid@*.myisp.net
-NickServ- The mask
*!*userid@*.myisp.net has been added successfully.
-NickServ- You
currently have 2 access list entries.
Command used to remove access masks that are no longer needed. If you have dropped an ISP in favor of another, you would delete your old mask from the access list and add the new one.
EXAMPLE: /NickServ ACCESS DEL *!*userid@*.myisp.net
-NickServ- The mask
*!*userid@*.myisp.net has been removed from your access
list.
Use this command to view your nick's access mask list. This is useful to use occasionally to ensure that you only have those masks in it that are needed. Any access masks you don't use should be deleted.
EXAMPLE: /NickServ ACCESS LIST
-NickServ- Access list for
Nick1:
-NickServ- *!*userid@*.myisp.net
-NickServ- *userid@myisp.net
-NickServ- End of list
Sometimes on IRC, your client gets disconnected for various reasons. Sometimes, it's because the connection between you and the server goes bad (perhaps because of bad network routing and packet loss). Sometimes, it's because your client is busy doing something else when the server pings it (which it does occasionally just to make sure it's still there). There are many ways to be disconnected from IRC.
In cases like these, sometimes the server doesn't realize right away that you aren't really at your keyboard (the console) anymore, and thinks that your client is still there. When this happens, you come back on IRC to find that your nick is already taken. If you do a /whois on yourself, you'll find that it's YOU! It's a ghost!
When this happens, you need to use this command to remove the old (non-existent) session in order to use your nick.
EXAMPLE: /MemoServ GHOST Nick1
EXAMPLE: /MemoServ GHOST Nick1 q59H39tF2bb
-NickServ- Your ghost has been
successfully killed.
When you get on IRC and find that someone else is using your nick, you have two ways you can get it back: you can ghost them (not necessarily the best idea) or you can RECOVER your nick through NickServ (better idea). The first way kills them off IRC, but they can frequently get back on IRC and back into your nick before you can switch to it (because of lag delays or whatever).
The better way is to use the RECOVER command to kill them out of your nick and places an "enforcer" into the nick as a place holder. This enforcer is a way to keep them from just jumping right back into your nick before you can.
EXAMPLE: /NickServ RECOVER Nick1
EXAMPLE: /NickServ RECOVER Nick1 q59H39tF2bb
-NickServ- The nick Nick1 has
been recovered.
If you get on IRC and find that your nick is in use, you can RECOVER your nick through NickServ. NickServ which puts a place holder into your nick, called an enforcer. This also happens if you have set KILL ON for your nick and someone, even you, used your nick but didn't identify in time and so had their nick changed to Guest#####.
In order to reclaim your nick, you issue the RELEASE command to get the enforcer out of your nick. Then you can switch into your nick without problems using the /nick Nick1 command
EXAMPLE: /NickServ RELEASE Nick1
EXAMPLE: /NickServ RELEASE Nick1 q59H39tF2bb
-NickServ- This nick Nick1
has been released.