| USING NICKSERV
NickServ allows you to "register" a nickname and prevent others
from using it. If the nick is not used for 30 days, the registration
will expire.
COMMANDS
| /msg NickServ |
REGISTER {password}
{email} |
This enables you to register your
nickname with a password and email
so only you can use it. Please try to use obscure passwords that
cannot be easily guessed. Passwords *ARE* case sensitive. Once you
have registered a nickname, you can use the SET
and ACCESS commands to configure it.
| /msg NickServ |
DROP {password} |
DROP allows you to cancel the registration
of your nickname, thus allowing others to re-register it. If you
have not IDENTIFY'd when you use the
DROP command, you will need to supply
your password; otherwise you do not
need to.
| /msg NickServ |
IDENTIFY {password} |
Most commands require that you identify
yourself, in order to use them. Also, nicknames which have kill
protection will be killed if the user has not identified within
one minute. If SET AUTOMASK is ON, and you IDENTIFY
from a host which is not on your ACCESS
list, the new hostmask will automatically be added to it.
| /msg NickServ |
ACCESS {ADD
| DEL | LIST}
[mask] |
The ACCESS command allows you to modify
the list of recognized hostmasks for
your nickname. If you use a hostmask that is not on your ACCESS
list, you must IDENTIFY with NickServ.
eg.
/msg NickServ ACCESS ADD
*hnet@*hashnet.org
Gives users matching *hnet@*hashnet.org permission to use your
nickname.
/msg NickServ ACCESS DEL
*hnet@*hashnet.org
Opposite of previous command.
/msg NickServ ACCESS LIST
Displays list of authorized hostmasks for your nickname.
| /msg NickServ |
SET {option}
{parameters} |
Configures various nickname options, which are:
| KILL |
Turn kill protection on or off |
| DISPLAY |
Sets how your nickname is displayed |
| AUTOMASK |
Auto add new hostmasks on IDENTIFY |
| PASSWORD |
Reset your nickname password |
| OPER |
Turn nickname expiration on or off |
| SECURE |
Turn nickname security on or off |
| UNSECURE |
Set nickname security very low |
| PRIVATE |
Hide nickname information from LISTS |
| MEMOS |
Allow memos sent to your nick |
| NOTIFY |
Turn notification of new memos on/off |
| LANGUAGE |
Sets the language services messages you in |
| EMAIL |
Associate an email address with your nick |
| URL |
Associate a url with your nick |
| ICQ |
Associate a icq no with your nick |
| HIDE |
Hide information in your INFO reply |
| /msg NickServ |
RECOVER {nickname}
{password} |
If someone has stolen your nickname, you can use RECOVER
to get it back. RECOVER performs a
nick collide on {nickname} and enforces
the nickname until you use the RELEASE
command on it, or just wait until the release timeout. If you match
a hostmask on {nickname}'s ACCESS
list, and {nickname} has NOT SET SECURE
ON, you do not need to supply a password.
However, if {nickname} has SET SECURE
ON, you will always need to supply the correct password.
| /msg NickServ |
RELEASE {nickname}
{password} |
If NickServ is enforcing your nickname, as it would after a RECOVER
or if you didn't IDENTIFY in time,
you can use RELEASE to regain control
of your nickname. If you match a hostmask on {nickname}'s
ACCESS list, and {nickname}'s
SET SECURE is OFF, you do not need
to supply a password. However, if {nickname}'s
SET SECURE is ON, you will always need
to supply the correct password.
| /msg NickServ |
SENDPASS {nickname} |
Send the password of the given nickname
to the e-mail address set in the nickname
record. This command is really useful to deal with lost passwords.
May be limited to IRC operators on certain networks.
This command is unavailable when encryption is enabled.
| /msg NickServ |
GHOST {nickname}
{password} |
If you suddenly get disconnected from your isp or the irc server,
sometimes a ghosted client will be left behind. This command can
be used to kill the ghosted client so you can get your nickname
back. If {nickname} has SET SECURE
OFF, and you match a hostmask on {nickname}'s
ACCESS LIST, then you do not need to
supply a password.
| /msg NickServ |
INFO {nickname} |
Displays information for {nickname}
such as time registered, SET options, whether they are online, etc.
| /msg NickServ |
GROUP {nickname}
{password} |
This command will link your current nickname to {nickname},
assuming you have supplied the correct password
for {nickname}. Once you have linked
nicknames, your ACCESS list will be
deleted, and you will share {nickname}'s
access list. Your memos will also be added to {nickname}'s
memos. If {nickname} was previously
unlinked, it will become the master nickname for your link.
When any nickname in your link gives a command to services, it
will be processed as if it came from the master nickname, with the
exception of DROP, UNLINK, SET PASSWORD, SET EMAIL, and SET URL.
The advantage of linked nicknames is whenever you IDENTIFY
for one nick, you will be identified for every nick in the link.
Also, memos sent to any nickname will all be stored in the master
nickname's record, for any nickname in the link to read. Furthermore,
if any nickname in the link is on a channel's access list, all nicknames
will receive the same access. eg.
/msg NickServ GROUP CoolGuy
CoolGuysPassword
Links your nickname to "CoolGuy".
This command lists all nicks in your group.
| /msg NickServ |
INFO {nickname}
[ALL] |
This command displays information about the given nickname,
such as the nicks`s owner, last seen address, and time, and nick
options. If you are identified for the nick you`re getting information
for and ALL is specified, you will
be shown all the information; regardless of whether it`s hidden
or not.
eg. /msg nickserv INFO nickname
[ALL]
This reverses the effect of the IDENTIFY
command, i.e. make you not recognized as the real owner of the nick
anymore. Note, however, that you won`t be asked to reidentify yourself.
| /msg NickServ |
STATUS {nickname} |
e.g. /msg nickserv STATUS nickname
This returns whether the user using the given nickname
is recognized as the owner of the nickname. The response has this
format:
nickname status-code
where nickname is the nickname
sent with the command, and status-code is one of the following:
0 - no such user online or nickname not registered
1 - user not recognized as nicknames`s owner
2 - user recognized as owner via acces list only
3 - user recognized as owner via password identification
Up to sixteen nicknames may be sent with each command; the rest
will be ignored. No error message is gernerated if no nickname is
given.
|