ChanServ Information

1.Registering a channel

 Syntax: /chanserv register #channel password description

 Informasi: Perintah REGISTER memungkinkan pengguna untuk mendaftar / nya channel nya (jika belum terdaftar) dengan cepat dan tanpa rasa sakit dengan mengetikkan satu baris. Dalam rangka untuk mendaftarkan saluran, pengguna harus menentukan saluran, password bahwa ia, dan deskripsi channel secara singkat.

 Dalam rangka untuk mengetahui apakah saluran terdaftar atau tidak, jenis / chanserv Info channel #, lebih pada nanti. Juga, jangan lupa untuk menggunakan tanda # saat mendaftarkan saluran.

Example: /chanserv register #jakarta indoirc My home online.
 

Ini akan mendaftarkan channel # jakarta dengan indoirc sandi (password yang kompleks yang cukup bagi seseorang untuk hanya menebak keluar dari biru) dan deskripsi "secara online di rumah saya."

2 · Dropping a channel

Syntax: /chanserv drop #channel [dropcode]


Informasi: Perintah ini akan memungkinkan Anda untuk menjatuhkan saluran Anda seorang pendiri. Pertama-tama Anda harus menggunakan perintah sendiri dan kemudian Anda akan menerima kode drop yang Anda ketik dengan perintah.

Catatan: Anda harus mengidentifikasi ke saluran sebelum dapat menjatuhkannya.

Example: /chanserv drop #jakarta
 

Ini adalah perintah pertama, setelah itu saya akan melihat sesuatu seperti ini di jendela status saya:

-ChanServ- Dropping a channel is permanent and cannot be undone! 
 

-ChanServ- To confirm, type: /chanserv DROP #jakarta 13151683216 

 

Setelah itu, saya akan ketik perintah DROP / chanserv # jakarta 13151683216 untuk menyelesaikan apakah aku yakin.

3 · Identifying as a channel's founder

Syntax: /chanserv identify #channel password
 
Information: Perintah identify adalah untuk mengidentifikasi pengguna sebagai founder dari channel tersebut dan memberikan akses pengguna ke pendiri berbasis perintah. Anda juga dapat menggunakan / identify # channel password dan / jasa mengidentifikasi # channel password (ini mungkin tidak bekerja pada beberapa klien).

4 · Retrieving a password

 Syntax: /chanserv sendpass #channel email

 Information: Perintah sendpass mengijinkan founder untuk memiliki password channel-nya dikirim ke alamat email yang terkait dengan saluran dalam database jasa. Menggunakan fungsi itu, pendiri mungkin mengirimkan password kepadanya memetikan password yang hilang / lupa. The foundernick untuk saluran yang harus diidentifikasi sebelum perintah yang dapat digunakan.

5 · Adding/removing/listing SOps

Syntax: /chanserv sop #channel add/del/list/wipe [nick]

 

Information: Perintah ini mengijinkan Founder untuk menambah atau menghapus Sops dalam akses list channel. Perintah Daftar, bagaimanapun, dapat diakses oleh 'AOps dan up.

 

6 · Adding/removing/listing AOps

Syntax: /chanserv aop #channel add/del/list/wipe [nick]
 
Information: Perintah ini mengijinkan SOps atau Founder untuk memasukkan atau menghapus Ops dari channel tersebut. The Perintah LIST dapat diakses oleh AOps dan sampai.
Note: Daftar AOp dibatasi hingga 300 entri. Sekalah hanya dapat digunakan oleh pendiri
Update: Pendiri tidak bisa lagi ditambahkan ke AOP / SOP / AKICK daftar
 

7 · Adding/removing/listing AKicks
Syntax: /chanserv akick #channel add/del/list/wipe [nick/host]
 
Information: Akicks adalah Auto Kicks dan dapat dimasukkan oleh SOp atau Founder, namun hanya pendiri dapat menghapus AKICK. Akicks dapat ditambahkan dengan julukan atau nama host. Juga, Anda dapat menentukan pola list (* kata *). Sekalah hanya dapat digunakan oleh pendiri.

Update: Pendiri tidak bisa lagi ditambahkan ke AOP / SOP / AKICK daftar.

8 · Oping / Deoping people
Syntax: /chanserv op/deop #channel nickname
 
Information: Perintah ini cukup sederhana, memungkinkan Anda untuk op atau DeOp nickname didalam channel tanpa harus menggunakan status Op atau bahkan berada di saluran. Anda harus menjadi AOp atau lebih tinggi untuk menggunakan perintah ini.
Note: Anda tidak dapat melakukan deop terhadap seseorang yang memiliki akses ChanServ lebih tinggi daripada Anda
 

9 · Mass kicking a channel
Syntax: /chanserv mkick #channel
 
Information: The masskick (Mass Kick) Perintah ini digunakan dalam kasus desync (informasi lebih lanjut dalam dokumen Netsplits) dalam hal saluran harus ditutup dan dibuka kembali. Perintah ini mengungsikan saluran sepenuhnya dengan menendang semua orang keluar, melarang * * @! * (Orang), pengaturan modus + i (mengundang saja) dan + l 1. Ketika MKICKing channel, Anda tidak dapat melakukan unban atau INVITE diri Anda kembali ke saluran. Hal ini seharusnya hanya digunakan dalam situasi pengambilalihan.
Note: Masskicks terbatas pada satu jam, dan hanya tersedia bagi SOP dan Pendiri. Perintah tidak boleh digunakan jika seseorang lebih tinggi daripada Anda berada dalam saluran. SOps tidak bisa masskick ketika pendiri hadir.
 

10 · Mass Deoping a channel
Syntax: /chanserv mdeop #channel
 
Information: Perintah MDEOP akan men-deop setiap orang dalam saluran yang memiliki akses yang sama atau kurang di ChanServ daripada orang yang menggunakan perintah. (misalnya AOps hanya bisa men-deop ops reguler dan Ops lainnya, SOps hanya bisa men-deop SOps lainnya, AOps dan ops biasa.)
 

11 · Setting options in channels
Perintah SET memiliki argumen yang berbeda, termasuk FOUNDER, PASSWORD, DESC, MLOCK, melihat daftar aop, KEEPTOPIC, URL, IDENT, MEMBATASI dan VERBOSE. Semua perintah ini akan memodifikasi dan mengubah bentuk aktifitas ChanServ didalam channel dan anda harus mengambil beberapa waktu untuk membiasakan diri dengan mereka karena mereka akan membantu Anda dalam menjaga keamanan channel anda.
Note: Untuk menggunakan perintah ChanServ SET dan argumen, pastikan Anda diidentifikasi sebagai founder channel (lebih lanjut di bawah).

11.1 Changing channel founders
Syntax: /chanserv set #channel founder
 
Information: The FOUNDER argument of the set command will allow the user that uses this command to change the channel founder to himself.
Note: The nickname that the user is using must be registered or the command will not work

11.2 Changing channel passwords
Syntax: /chanserv set #channel passwd oldpassword newpassword
Information: This argument will change the password of the channel from an old password to a new password. It is a good idea to rotate your password once every few months to improve security (more on that in the Security section).
Note: You must identify to the channel before being able to use this command.
Example:/chanserv set #jakarta passwd indoirc indoirc2

This command will set the channel password from indoirc to  indoirc2

11.3 Changing channel description
Syntax: /chanserv set #channel desc newdescription
Information: The DESC argument lets a user change the description of his or her channel which can be viewed through the /chanserv info command (more on that later).
Example: /chansev set #mystro desc Mystro's home on the web!

This command will change #mystro's channel description to 'Mystro's home on the web!'

11.4 Changing the channel modes
Syntax: /chanserv set #channel mlock modes
Information: The MLOCK command is one of the most important commands to maintain channel security. Below is a list of all the possible modes and what they do:
+R - Only registered nicks allowed. Very useful if you wish to stop clone attacks, since most clone attacks use unregistered nicks.
+n - No external messages. This option prevents people who are not in channel from sending messages to that channel.
+t - Only ops set topic. This command will make sure non-ops cannot change the topic of the channel. There are also a few ChanServ settings that can help with more specific topic settings (only SOps/AOps can change topic) , more on that below.
+s and +p - Both commands set the channel to be invisible in /list commands, but +s also sets it invisible in whois, both settigs are a good way to keep unwanted users out of channel.
+i - This option makes the channel closed to anyone unless an op invites them or they have ChanServ invite them using the /chanserv invite command.nnel has at a time, which is a good technique for clone protection. (More on that in the Security section).
+m - This option prevents anyone who is not voiced or OPed from talking in the channel.
+c - This option will disable any control codes (color, bold, underline, reverse) from being sent to the channel and will those messages. Also useful against clone attacks.

Note: Some of the options require another argument (ie. +l needs a number, +k needs a password) so the arguments need to be specified in the order of the options. (ie. +kl password number)
Example: /chanserv set #mystro mlock +ntR-s

This command would set #mystro to +ntR-s which means only ops can change topic, no external messages, registered nicks only and secret can't be set.

11.5 Setting OPGUARD on and off 
Syntax: /chanserv set #channel opguard on/off
Information: When this argument is set on only AOps, SOps and the Founder will be allowed to be an op in the channel, everyone else will automatically be deopped.

11.6 Setting KEEPTOPIC on and off
Syntax: /chanserv set #channel keeptopic on/off
Information: If a channel becomes empty (last person leaves), ChanServ will save the topic if this option is set on so that next time someone comes in the topic will be recreated with the nick who set it.

11.7 Making a URL show in the info
Syntax: /chanserv set #channel url [URLhere]
Information: This command lets you set the URL for your channel which can be viewed through the /chanserv info command. To remove a URL, type the command without a URL at the end.

11.8 Ops have to identify before getting opped
Syntax: /chanserv set #channel ident on/off
Information: The ident argument regulates whether people can get opped in the channel automatically without having to identify (access list) or must identify.

11.9 Restricting a channel to AOps and higher
Syntax: /chanserv set #channel restrict on/off
Information: The RESTRICT argument, when set on, will not allow anyone who is not on the channel access list to join the channel and will automatically kick and ban them.

11.10 Turning VERBOSE on and off
Syntax: /chanserv set #channel verbose on/off
Information: The VERBOSE argument, when set on, will notify channel ops of any changes made to the channel access list (ie. aop added/removed, sop added/removed, akick added/removed).
An example of output would be:
-ChanServ:@#mystro- [VERBOSE] Mystro!mystro@sun.2kservices.com => aop #mystro add |Mystro|
 

11.11 Setting who can change the topic
Syntax: /chanserv set #channel topiclock founder/sop/off
Information: The TOPICLOCK command, when turned on, will allow you to set who should be able to change the topic: You (the founder), a SOp, or anyone else (off).

11.12 Allowing users who join to stay opped
Syntax: /chanserv set #channel leaveops on/off
Information: This command, when turned on, will not deop the first user to join the channel regardless of whether he is an op or not, if set off (as it is by default), it will deop anyone who is not AOp or higher. It is recommended you leave this setting untouched for security.

11.13 Founder does not need to identify
Syntax: /chanserv set #channel unsecure
Information: This command, when turned on, will allow anyone on the founder's nick access list to make founder type changes to the channel. This may be a large security compromise if the founder does not have a very secure nickserv access list (please see the NickServ document for more information). It is suggested to leave this argument untouched.

11.14 Making the channel private
Syntax: /chanserv set #channel private on/off
Information: This setting, when turned on, will prevent the /chanserv invite command from being used. Only AOps and above will be able to see the channel topic when issuing /chanserv info #channelname. It will also allow only people who know about the channel to access it.

11.15 Setting who may send channel-wide memos
Syntax: /chanserv set #channel memo none/aop/sop/founder
Information: This command allows the founder to manage who may send channel memos. When memo is set to none, no one can memo; when memo is set to AOp, all people on chanserv's access list may memo, when memo is set to SOp only founder and sops may memo and when the option is set to founder only the channel founder may send channel wide memos.

11.16 Setting the successor of the channel
Syntax: /chanserv set #channel successor nickname / -
Information: This command allows the founder to set the successor for the channel in case the nickname of the founder expires. When and if the nickname expires the channel will be turned over to the successor with all rights and privileges of the founder. If you wish to disable the successor feature in your channel, use a hyphen ("-") instead of a nickname. If the founder's nickname expires, and that channel has a successor, the following will occur: A memo is sent to the channel's succesor with an AUTH code. The successor must use the AUTH code to authorize himself in the channel within ten (10) days. If the successor does so, a random password is generated that can be used to identify and become the founder. If the successors nick expires, or the successor doesnt take any action within ten (10) days, the channel expires as normal. A user can prevent himself from being added as a successor to a channel if he has enabled the NOOP option on his nickname

11.16.1 ·Removing yourself as Successor 
If you want to remove yourself as successor of a channel you can use the following command to do that
Syntax:/chanserv successor #channel DEL
Note: You must be using the Nickname that is listed as successor and you must be identified to it.
Example: /chanserv successor #jakarta DEL
 

11.16.2 ·Resending the Authorization Request
Syntax:/chanserv sendauth #channel S
Information: When a founders nick expires, the successor will be sent an AUTH code by MemoServ to gain access to the channel. If the first memo fails, the successor can re-request the AUTH code to be sent to them again through memoserv using the command

11.17 Adding a channel manager
Syntax: /chanserv manager #channel add nick
Syntax: /chanserv manager #channel del nick
Founders can now add up to 5 managers to their channel. Managers have *almost* full control over the channel with the exception of changing the channel's foundership

Channel managers can: - Manage the SOP list (add/remove SOPs) - Change WEBPASSWD - Wipe AOP/SOP lists - Change channel description - Set/unset OPGUARD - Set/unset MLOCK - Set/unset IDENT - Set/unset KEEPTOPIC - Set/unset RESTRICT - Set/unset URL - Set/unset VERBOSE - Set/unset TOPICLOCK (unless it's locked to the founder) - Set/unset LEAVEOPS - Set/unset PRIVATE - Set/unset MEMO level (unless it's locked to the founder) - See successor's nick with ChanServ INFO Channel managers can *NOT*: - Change channel password - Change founder - Set/unset successor - Set/unset mailblock - Add/remove other managers - Set/unset UNSECURE (currently broken and doesn't do anything) - Use sendpass

11.18 Setting the web password for the channel
Syntax: /chanserv set #channel webpasswd password
Note: The password should be different from the password of the channel so that it may be given out to people in order to modify the website.

11.19 Setting the mailblock option for the channel
Syntax:/chanserv set #channel mailblock on/off
Information: This command allows the founder of a channel to turn on/off mailblock on his channel, by that enabling/disabling the option for the channel password to be sent to the email on file in case of a lost password.
Note: By enabling this command, the founder no longer has the option to retrieve his password incase it is lost/forgotten. The mailblock option should NOT be turned on unless the founder is absolutely sure that he is not going to forget/lose the password.

12 · Inviting yourself into the channel
Syntax: /chanserv invite #channel
Information: This command will invite you into a +R/+O/+i/+l/+k/+b channel or a channel which you have been banned from by someone. You must be an AOp or higher to use that command.

13 · Viewing the access of a person
Syntax: /chanserv acc/access #channel [nick]
Information: This command lets an AOp or higher see what access he/someone else has to the channel. The access is displayed numerically, below are the definitions:
-2 = Channel is frozen or closed
-1 = AutoKICKed from the channel
0 = basic
10 = AutoOp
20 = SuperOp
30 = User has MANAGER access
40 = Has founder access via a NickServ access list mask
50 = Has founder access via identification to NickServ
60 = Has founder access via identification to ChanServ

If the USER is not online, the access will be 0.

Note: You must be an AOp or higher to use that command.
Example: /chanserv acc #mystro mystro
The following reply would come from ChanServ:
-ChanServ- Mystro ACC #mystro 50 (Founder)
 

14 · Why a person opped
Syntax: /chanserv why #channel nick
Information: The WHY command does the same thing as the ACC/ACCESS command, however it returns the status of the user in AOp/SOp/Founder form with no access level. It will also tell you when someone is using a different nickname what nickname he has access to that let him become opped. Also it tell you the status of the channel.
Note: You must be an AOp or higher to use that command
Example: /chanserv why #docsteam Zappu
Below is what you would receive from ChanServ
-ChanServ- Zappu has SOP access to #docsteam. Reason: Identification to the nickname Zappu. Channel Frozen: NO
 

15 · Unbanning yourself and others
Syntax: /chanserv unban #channel [nick/*/nick!user@host]
Information The UNBAN command will unban all masks that match your nick!user@host if you do not specify a nickname. AOps may also unban a specific user or a host. SOps can unban everything by specifying the * sign instead of a nickname.

16 · Counting AOps/SOps and AKicks 
Syntax: /chanserv count #channel
Information: This command counts all the AKicks, AOps and SOps in a channel and gives you the number in a reply.
EXample: /chanserv count #mystro
This will return the following:
-ChanServ- Channel: #mystro - AOP: 27 SOP: 3 AKICK: 9

17 · listing Aops,Sops,Managers and Founder of the channel.

Syntax: /chanserv listops #channel
Information: This command lists all the AOPs, SOPs, managers and founder of the channel. Limited to AutoOps or above.
EXample: /chanserv listops #docsteam
This will return the following:
-ChanServ- Founder:
-ChanServ- Fredfred (fredfred@staff.dalnet)
-ChanServ- Manager[s}:
-ChanServ- Sop(s):
-ChanServ- eDdYk0nG (eddykong@118.128.268
-ChanServ- Zappu (zappu@123.345.789)
-ChanServ- Aop(s):
-ChanServ- Uzay (uzay@123.123.123)

18 · Finding information on a channel

Syntax: /chanserv info #channel>
Information: The INFO command allows one to see specific information about channels (chanserv settings, topic, registry date, last op date, etc.)
Example: /chanserv info #mystro
This command will give out the following information:
-ChanServ- Info for #mystro:
-ChanServ- Founder : |Mystro| (mystro@66.38.188.104)
-ChanServ- Mode Lock : +nt-ilk
-ChanServ- Description: My little home on the net.
-ChanServ- Options : Verbose
-ChanServ- Memo Level : AOP
-ChanServ- Registered : Thu 09/30/1999 03:07:00 GMT
-ChanServ- Last opping: Sat 04/21/2001 13:54:14 GMT
-ChanServ- *** End of Info ***

This shows that the founder is |Mystro| with the host mystro@66.38.188.104, the channel modes are +nt-ilk, the description is 'my little home on the net.' etc.

19 · Channel Security

Now that you have gotten yourself familiarized with the ChanServ commands, it's time to move on to a very important topic: Channel Security. Each day, many people join channels such as #operhelp in order to receive help with channel takeovers, forgotten passwords, etc... Here are some tactics to help you fight all of the security problems.
1) Make your password use uppercase and lowercase letters, as well as numbers. This makes passwords much harder to guess.
2) NEVER EVER give out your password to anyone who you wouldn't trust with your life. DALnet does not help users who shared their password and later found it misused.
3) Add SOps very carefully. Also, add AOps very carefully. Don't add anyone who you don't know very well to the OP list.
4) Once the channel is registered , Chanserv set +nt-k as MLOCK ,So if you want to set a password for your Channel , you have to remove the -k from the MLOCK and keep the +nt for channel protection , Syntex of removal the MLOCK is : /chanserv set #channelname mlock +nt
5) Don't create an auto-identify script. If you do, make sure you don't give out the script with the auto identify or you may be in serious trouble.
6) Rotate your password at least once every couple of months.

20 · Conclusion

Now that you are familiar with the ChanServ commands you're ready for the privileges and responsibilities of being a founder. You may also want to check out the NickServ documents for some information on the NickServ commands and settings.
For more information on AKicks, AOps and SOps, please take a look at the Chanserv Access document located

21 · Credits

Thanks goes to Dalila, the Documentation Team leader and LadyDana for suggesting this document. Thanks also goes to Morfeus and quen for proof-reading the document.

HELP

 NickServ allows you to "register" a nickname and
 prevent others from using it. The following
 commands allow for registration and maintenance of
 nicknames; to use them, type /msg NickServ command.
 For more information on a specific command, type
 /msg NickServ HELP command.
 
     REGISTER   Register a nickname
     GROUP      Join a group
     IDENTIFY   Identify yourself with your password
     ACCESS     Modify the list of authorized addresses
     SET        Set options, including kill protection
     DROP       Cancel the registration of a nickname
     RECOVER    Kill another user who has taken your nick
     RELEASE    Regain custody of your nick after RECOVER
     SENDPASS   Forgot your password? Try this
 
 Other commands: GHOST, ALIST, GLIST, INFO, LIST, LOGOUT, 
                 STATUS
 
 NOTICE: This service is intended to provide a way for
 IRC users to ensure their identity is not compromised.
 It is NOT intended to facilitate "stealing" of
 nicknames or other malicious actions.  Abuse of NickServ
 will result in, at minimum, loss of the abused
 nickname(s).
  

• REGISTER
  

   Syntax: /msg NickServ  REGISTER password [email]
   
   Registers your nickname in the NickServ database.  Once
   your nick is registered, you can use the SET and ACCESS
   commands to configure your nick's settings as you like
   them.  Make sure you remember the password you use when
   registering - you'll need it to make changes to your nick
   later.  (Note that case matters!  EPONA, Epona, and 
   epona are all different passwords!)
   
   Guidelines on choosing passwords:
   
   Passwords should not be easily guessable.  For example,
   using your real name as a password is a bad idea.  Using
   your nickname as a password is a much worse idea ;) and,
   in fact, NickServ will not allow it.  Also, short
   passwords are vulnerable to trial-and-error searches, so
   you should choose a password at least 5 characters long.
   Finally, the space character cannot be used in passwords.
   
   The parameter email is optional and will set the email
   for your nick immediately. However, it may be required
   on certain networks.
   Your privacy is respected; this e-mail won't be given to
   any third-party person.
   
   This command also creates a new group for your nickname,
   that will allow you to register other nicks later sharing
   the same configuration, the same set of memos and the 
   same channel privileges. For more information on this
   feature, type /msg NickServ HELP GROUP.
   
  

• GROUP
  

   Syntax: /msg NickServ  GROUP target password
   
   This command makes your nickname join the target nickname's 
   group. password is the password of the target nickname.
   
   Joining a group will allow you to share your configuration,
   memos, and channel priviledges with all the nicknames in the
   group, and much more!
    
   A group exists as long as it is useful. This means that even
   if a nick of the group is dropped, you won't lose the
   shared things described above, as long as there is at
   least one nick remaining in the group.
   
   You can use this command even if you have not registered
   your nick yet. If your nick is already registered, you'll
   need to identify yourself before using this command. Type 
   /msg NickServ HELP IDENTIFY for more information. This
   last may be not possible on your IRC network.
   
   It is recommended to use this command with a non-registered
   nick because it will be registered automatically when 
   using this command. You may use it with a registered nick (to 
   change your group) only if your network administrators allowed 
   it.
   
   You can only be in one group at a time. Group merging is
   not possible.
   
   Note: all the nicknames of a group have the same password.
  
  

• IDENTIFY
  

   Syntax: /msg NickServ  IDENTIFY password
   
   Tells NickServ that you are really the owner of this
   nick.  Many commands require you to authenticate yourself
   with this command before you use them.  The password
   should be the same one you sent with the REGISTER
   command.
   
  

• LOGOUT
  

   Syntax: /msg NickServ  LOGOUT
   
   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.
  
  

• DROP
  

   Syntax: /msg NickServ  DROP [nickname]
   
   Drops your nickname from the NickServ database.  A nick
   that has been dropped is free for anyone to re-register.
   
   You may drop a nick within your group by passing it
   as the nick parameter.
   
   In order to use this command, you must first identify
   with your password (/msg NickServ HELP IDENTIFY for more
   information).
  
  

• ACCESS
  

   Syntax: /msg NickServ  ACCESS ADD mask
           ACCESS DEL mask
           ACCESS LIST
   
   Modifies or displays the access list for your nick.  This
   is the list of addresses which will be automatically
   recognized by NickServ as allowed to use the nick.  If
   you want to use the nick from a different address, you
   need to send an IDENTIFY command to make NickServ
   recognize you.
   
   Examples:
   
       ACCESS ADD anyone@*.bepeg.com
           Allows access to user anyone from any machine in
           the bepeg.com domain.
   
       ACCESS DEL anyone@*.bepeg.com
           Reverses the previous command.
   
       ACCESS LIST
           Displays the current access list.
  
  

• SET
  

   Syntax: /msg NickServ  SET option parameters
   
   Sets various nickname options.  option can be one of:
   
       DISPLAY    Set the display of your group in Services
       PASSWORD   Set your nickname password
       LANGUAGE   Set the language Services will use when
                      sending messages to you
       URL        Associate a URL with your nickname
       EMAIL      Associate an E-mail address with your nickname
       ICQ        Associate an ICQ number with your nickname
       GREET      Associate a greet message with your nickname
       KILL       Turn protection on or off
       SECURE     Turn nickname security on or off
       PRIVATE    Prevent your nickname from appearing in a
                      /msg NickServ LIST
       HIDE       Hide certain pieces of nickname information
       MSG        Change the communication method of Services
   
   In order to use this command, you must first identify
   with your password (/msg NickServ HELP IDENTIFY for more
   information).
   
   Type /msg NickServ HELP SET option for more information
   on a specific option.
  
  

• SET DISPLAY
  

   Syntax: /msg NickServ  SET DISPLAY new-display
   
   Changes the display used to refer to your nickname group in 
   Services. The new display MUST be a nick of your group.
  
  

• SET PASSWORD
  

   Syntax: /msg NickServ  SET PASSWORD new-password
   
   Changes the password used to identify you as the nick's
   owner.
  
  

• SET LANGUAGE
  

   Syntax: /msg NickServ  SET LANGUAGE number
   
   Changes the language Services uses when sending messages to
   you (for example, when responding to a command you send).
   number should be chosen from the following list of
   supported languages:
   
  
  

• SET URL
  

   Syntax: /msg NickServ  SET URL url
   
   Associates the given URL with your nickname.  This URL
   will be displayed whenever someone requests information
   on your nick with the INFO command.
  
  

• SET EMAIL
  

   Syntax: /msg NickServ  SET EMAIL address
   
   Associates the given E-mail address with your nickname.
   This address will be displayed whenever someone requests
   information on the channel with the INFO command.
   
  

• SET ICQ
  

   Syntax: /msg NickServ  SET ICQ number
   
   Associates the given ICQ number with your nickname.  This 
   number will be displayed whenever someone requests 
   information on your nick with the INFO command.
   
  

• SET GREET
  

   Syntax: /msg NickServ  SET GREET message
   
   Makes the given message the greet of your nickname, that
   will be displayed when joining a channel that has GREET
   option enabled, provided that you have the necessary 
   access on it.
  
  

• SET KILL
  

   Syntax: /msg NickServ  SET KILL {ON | QUICK | IMMED | OFF}
   
   Turns the automatic protection option for your nick
   on or off.  With protection on, if another user
   tries to take your nick, they will be given one minute to
   change to another nick, after which NickServ will forcibly change
   their nick.
   
   If you select QUICK, the user will be given only 20 seconds
   to change nicks instead of the usual 60.  If you select
   IMMED, user's nick will be changed immediately without being
   warned first or given a chance to change their nick; please
   do not use this option unless necessary.  Also, your
   network's administrators may have disabled this option.
  
  

• SET SECURE
  

   Syntax: /msg NickServ  SET SECURE {ON | OFF}
   
   Turns NickServ's security features on or off for your
   nick.  With SECURE set, you must enter your password
   before you will be recognized as the owner of the nick,
   regardless of whether your address is on the access
   list.  However, if you are on the access list, NickServ
   will not auto-kill you regardless of the setting of the
   KILL option.
  
  

• SET PRIVATE
  

   Syntax: /msg NickServ  SET PRIVATE {ON | OFF}
   
   Turns NickServ's privacy option on or off for your nick.
   With PRIVATE set, your nickname will not appear in
   nickname lists generated with NickServ's LIST command.
   (However, anyone who knows your nickname can still get
   information on it using the INFO command.)
  
  

• SET HIDE
  

   Syntax: /msg NickServ  SET HIDE {EMAIL | USERMASK | QUIT} {ON | OFF}
   
   Allows you to prevent certain pieces of information from
   being displayed when someone does a NickServ INFO on your
   nick.  You can hide your E-mail address (EMAIL), last seen
   user@host mask (USERMASK), and last quit message (QUIT).
   The second parameter specifies whether the information should
   be displayed (OFF) or hidden (ON).
   
  

• SET MSG
  

   Syntax: /msg NickServ  SET MSG {ON | OFF}
   
   Allows you to choose the way Services are communicating with 
   you. With MSG set, Services will use messages, else they'll 
   use notices.
  
  

• RECOVER
  

   Syntax: /msg NickServ  RECOVER nickname [password]
   
   Allows you to recover your nickname if someone else has
   taken it; this does the same thing that NickServ does
   automatically if someone tries to use a kill-protected
   nick.
   
   When you give this command, NickServ will bring a fake
   user online with the same nickname as the user you're
   trying to recover your nick from.  This causes the IRC
   servers to disconnect the other user.  This fake user will
   will remain online for one minute to ensure that the other
   user does not immediately reconnect; after that minute, you
   can reclaim your nick.  Alternatively, use the RELEASE
   command (/msg NickServ HELP RELEASE) to get the nick
   back sooner.
   
   In order to use the RECOVER command for a nick, your
   current address as shown in /WHOIS must be on that nick's
   access list, you must be identified and in the group of
   that nick, or you must supply the correct password for
   the nickname.
  
  

• RELEASE
  

   Syntax: /msg NickServ  RELEASE nickname [password]
   
   Instructs NickServ to remove any hold on your nickname
   caused by automatic kill protection or use of the RECOVER
   command.  By default, such holds last for one minute;
   this command gets rid of them sooner.
   
   In order to use the RELEASE command for a nick, your
   current address as shown in /WHOIS must be on that nick's
   access list, you must be identified and in the group of
   that nick, or you must supply the correct password for
   the nickname.
  
  

• GHOST
  

   Syntax: /msg NickServ  GHOST nickname [password]
   
   Terminates a "ghost" IRC session using your nick.  A
   "ghost" session is one which is not actually connected,
   but which the IRC server believes is still online for one
   reason or another.  Typically, this happens if your
   computer crashes or your Internet or modem connection
   goes down while you're on IRC.
   
   In order to use the GHOST command for a nick, your
   current address as shown in /WHOIS must be on that nick's
   access list, you must be identified and in the group of
   that nick, or you must supply the correct password for
   the nickname.
  
  

• INFO
  

   Syntax: /msg NickServ  INFO nickname [ALL]
   
   Displays information about the given nickname, such as
   the nick'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.
  
  

• LIST
  

   Syntax: /msg NickServ  LIST pattern
   
   Lists all registered nicknames which match the given
   pattern, in nick!user@host format.  Nicks with the
   PRIVATE option set will not be displayed.
   
   Examples:
   
       LIST *!joeuser@foo.com
           Lists all nicks owned by joeuser@foo.com.
   
       LIST *Bot*!*@*
           Lists all registered nicks with Bot in their
           names (case insensitive).
   
       LIST *!*@*.bar.org
           Lists all nicks owned by users in the bar.org
           domain.
  
  

• ALIST
  

   Syntax: /msg NickServ  ALIST [level]
   
   Lists all channels you have access on. Optionally, you can specify
   a level in XOP or ACCESS format. The resulting list will only 
   include channels where you have the given level of access.
  
   Examples:
       ALIST Founder
        Lists all channels where you have Founder
     access.
  
    ALIST AOP
        Lists all channels where you have AOP access 
     or greater.
  
    ALIST 10
        Lists all channels where you have level 10 
     access or greater.
   
   Channels that have the NOEXPIRE option set will be prefixed by 
   an exclamation mark.
   
  

• GLIST
  

   Syntax: /msg NickServ  GLIST
   
   Lists all nicks in your group.
  
  

• STATUS
  

   Syntax: /msg NickServ  STATUS nickname...
   
   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 nickname's owner
       2 - user recognized as owner via access 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 generated if no
   nickname is given.
   
  

• SENDPASS
  

   Syntax: /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.
  
  

• SERVADMIN HELP
  

   
   The following commands are available to Services admins:
   
       GETPASS    Retrieve the password for a nickname
                      (only if encryption is disabled)
       FORBID     Prevent a nickname from being used
   
   Services admins can also drop any nickname without needing
   to identify for the nick, and may view the access list for
   any nickname (/msg NickServ ACCESS LIST nick).
  
  

• SERVADMIN LOGOUT
  

   Syntax: /msg NickServ  LOGOUT [nickname [REVALIDATE]]
   
   Without a parameter, 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.
   
   With a parameter, does the same for the given nick. If you 
   specify REVALIDATE as well, Services will ask the given nick
   to re-identify. This use limited to Services admins.
  
  

• SERVADMIN DROP
  

   Syntax: /msg NickServ  DROP [nickname]
   
   Without a parameter, drops your nickname from the
   NickServ database.
   
   With a parameter, drops the named nick from the database.
   You may drop any nick within your group without any 
   special privileges. Dropping any nick is limited to 
   Services admins.
  
  

• SERVADMIN SET
  

   
   Services admins can also set the option NOEXPIRE, with
   which nicknames can be prevented from expiring.
   Additionally, Services admins can set options for any
   nickname without entering a password, using the format
   SET nickname option parameters.
  
  

• SERVADMIN SET NOEXPIRE
  

   Syntax: /msg NickServ  SET [nickname] NOEXPIRE {ON | OFF}
   
   Sets whether the given nickname will expire.  Setting this
   to ON prevents the nickname from expiring.  If no
   nickname is given, sets the no-expire flag for your nick.
   
   Limited to Services admins.
  
  

• SERVADMIN LIST
  

   Syntax: /msg NickServ  LIST pattern [FORBIDDEN] [NOEXPIRE]
   
   Lists all registered nicknames which match the given
   pattern, in nick!user@host format.  Nicks with the PRIVATE
   option set will only be displayed to Services admins.  Nicks
   with the NOEXPIRE option set will have a ! prepended to the
   nickname for Services admins.
   
   If the FORBIDDEN or NOEXPIRE options are given, only nicks
   which, respectively, are FORBIDden or have the NOEXPIRE flag
   set will be displayed.  If both options are given, both
   types of nicks will be displayed.  These options are limited
   to Services admins.
   
   Examples:
   
       LIST *!indoirc@yahoo.com
           Lists all registered nicks owned by indoirc@yahoo.com.
   
       LIST *Bot*!*@*
           Lists all registered nicks with Bot in their
           names (case insensitive).
   
       LIST * NOEXPIRE
           Lists all registered nicks which have been set to
           not expire.
  
  

• SERVADMIN ALIST
  

   Syntax: /msg NickServ  ALIST [nickname] [level]
   
   With no parameters, lists channels you have access on. With
   one parameter, lists channels that nickname has access 
   on. With two parameters lists channels that nickname has 
   level access or greater on.
  
   This use limited to Services admins.
  
  

• SERVADMIN GLIST
  

   Syntax: /msg NickServ  GLIST [nickname]
   
   Without a parameter, lists all nicknames that are in
   your group.
   
   With a parameter, lists all nicknames that are in the
   group of the given nick.
   This use limited to Services admins.
  
  

• SERVADMIN GETPASS
  

   Syntax: /msg NickServ  GETPASS nickname
   
   Returns the password for the given nickname.  Note that
   whenever this command is used, a message including the
   person who issued the command and the nickname it was used
   on will be logged and sent out as a WALLOPS/GLOBOPS.
   
   Limited to Services admins.
   
   This command is unavailable when encryption is enabled.
  
  

• SERVADMIN FORBID
  

   Syntax: /msg NickServ  FORBID nickname [reason]
   
   Disallows a nickname from being registered or used by
   anyone.  May be cancelled by dropping the nick.
   
   On certain networks, reason is required.
   
   Limited to Services admins

• HELP
  

   BotServ allows you to have a bot on your own channel.
   It has been created for users that can't host or
   configure a bot, or for use on networks that don't
   allow users' bot. Available commands are listed 
   below; to use them, type /msg BotServ command.  For 
   more information on a specific command, type /msg 
   BotServ HELP command.
   
   BOTLIST            Lists available bots
   ASSIGN             Assigns a bot to a channel
   SET                Configures bot options
   KICK               Configures kickers
   BADWORDS           Maintains bad words list
   
   Other commands: ACT INFO SAY UNASSIGN
   
   Bot will join a channel whenever there is at least
   <num> user(s) on it.
   
  

• BOTLIST
  

   Syntax: /msg BotServ  BOTLIST
   
   Lists all available bots on this network.
   
  

• ASSIGN
  

   Syntax: /msg BotServ  ASSIGN chan nick
   
   Assigns a bot pointed out by nick to the channel chan. You
   can then configure the bot for the channel so it fits
   your needs.  
   
  

• UNASSIGN
  

   Syntax: /msg BotServ  UNASSIGN chan
   
   Unassigns a bot from a channel. When you use this command,
   the bot won't join the channel anymore. However, bot
   configuration for the channel is kept, so you will always
   be able to reassign a bot later without have to reconfigure
   it entirely.
   
  

• INFO
  

   Syntax: /msg BotServ  INFO {chan | nick}
   
   Allows you to see BotServ information about a channel or a bot.
   If the parameter is a channel, then you'll get information
   such as enabled kickers. If the parameter is a nick,
   you'll get information about a bot, such as creation
   time or number of channels it is on.
   
  

• SET
  

   Syntax: /msg BotServ  SET channel option parameters
   
   Configures bot options.  option can be one of:
   
       DONTKICKOPS      To protect ops against bot kicks
       DONTKICKVOICES   To protect voices against bot kicks
       GREET            Enable greet messages
       FANTASY          Enable fantaisist commands
       SYMBIOSIS        Allow the bot to act as a real bot
   
   Type /msg BotServ HELP SET option for more information
   on a specific option.
   
   Note: access to this command is controlled by the
   level SET.
   
  

• SET DONTKICKOPS
  

   Syntax: /msg BotServ  SET channel DONTKICKOPS {ON|OFF}
   
   Enables or disables ops protection mode on a channel.
   When it is enabled, ops won't be kicked by the bot
   even if they don't match the NOKICK level.
   
  

• SET DONTKICKVOICES
  

   Syntax: /msg BotServ  SET channel DONTKICKVOICES {ON|OFF}
   
   Enables or disables voices protection mode on a channel.
   When it is enabled, voices won't be kicked by the bot
   even if they don't match the NOKICK level.
   
  

• SET FANTASY
  

   Syntax: /msg BotServ  SET channel FANTASY {ON|OFF}
   
   Enables or disables fantasy mode on a channel.
   When it is enabled, users will be able to use
   commands !op, !deop, !voice, !devoice,
   !kick, !kb, !unban, !seen on a channel (find how 
   to use them; try with or without nick for each, 
   and with a reason for some?).
   
   Note that users wanting to use fantaisist
   commands MUST have enough level for both
   the FANTASIA and another level depending
   of the command if required (for example, to use 
   !op, user must have enough access for the OPDEOP
   level).
  
  

• SET GREET
  

   Syntax: /msg BotServ  SET channel GREET {ON|OFF}
   
   Enables or disables greet mode on a channel.
   When it is enabled, the bot will display greet
   messages of users joining the channel, provided
   they have enough access to the channel.
  
  

• SET SYMBIOSIS
  

   Syntax: /msg BotServ  SET channel SYMBIOSIS {ON|OFF}
   
   Enables or disables symbiosis mode on a channel.
   When it is enabled, the bot will do everything
   normally done by BotServ on channels, such as MODEs,
   KICKs, and even the entry message.
  
  

• KICK
  

   Syntax: /msg BotServ  KICK channel option parameters
   
   Configures bot kickers.  option can be one of:
   
       BOLDS         Sets if the bot kicks bolds
       BADWORDS      Sets if the bot kicks bad words
       CAPS          Sets if the bot kicks caps
       COLORS        Sets if the bot kicks colors
       FLOOD         Sets if the bot kicks flooding users
       REPEAT        Sets if the bot kicks users who repeat
                          themselves
       REVERSES      Sets if the bot kicks reverses
       UNDERLINES    Sets if the bot kicks underlines
   
   Type /msg BotServ HELP KICK option for more information
   on a specific option.
   
   Note: access to this command is controlled by the
   level SET.
  
  

• KICK BOLDS
  

   Syntax: /msg BotServ  KICK channel BOLDS {ON|OFF} [ttb]
  
   Sets the bolds kicker on or off. When enabled, this
   option tells the bot to kick users who use bolds.
  
   ttb is the number of times an user can be kicked
   before it get banned. Don't give ttb to disable
   the ban system once activated.
  
  

• KICK COLORS
  

   Syntax: /msg BotServ  KICK channel COLORS {ON|OFF} [ttb]
  
   Sets the colors kicker on or off. When enabled, this
   option tells the bot to kick users who use colors.
  
   ttb is the number of times an user can be kicked
   before it get banned. Don't give ttb to disable
   the ban system once activated.
  
  

• KICK REVERSES
  

   Syntax: /msg BotServ  KICK channel REVERSES {ON|OFF} [ttb]
  
   Sets the reverses kicker on or off. When enabled, this
   option tells the bot to kick users who use reverses.
  
   ttb is the number of times an user can be kicked
   before it get banned. Don't give ttb to disable
   the ban system once activated.
  
  

• KICK UNDERLINES
  

   Syntax: /msg BotServ  KICK channel UNDERLINES {ON|OFF} [ttb]
  
   Sets the underlines kicker on or off. When enabled, this
   option tells the bot to kick users who use underlines.
  
   ttb is the number of times an user can be kicked
   before it get banned. Don't give ttb to disable
   the ban system once activated.
  
  

• KICK CAPS
  

   Syntax: /msg BotServ  KICK channel CAPS {ON|OFF} [ttb [min [percent]]]
  
   Sets the caps kicker on or off. When enabled, this
   option tells the bot to kick users who are talking in
   CAPS.
  
   The bot kicks only if there are at least min caps
   and they constitute at least percent%% of the total 
   text line (if not given, it defaults to 10 characters
   and 25%%).
  
   ttb is the number of times an user can be kicked
   before it get banned. Don't give ttb to disable
   the ban system once activated.
  
  

• KICK FLOOD
  

   Syntax: /msg BotServ  KICK channel FLOOD {ON|OFF} [ttb [ln [secs]]]
  
   Sets the flood kicker on or off. When enabled, this
   option tells the bot to kick users who are flooding
   the channel using at least ln lines in secs seconds
   (if not given, it defaults to 6 lines in 10 seconds).
   
   ttb is the number of times an user can be kicked
   before it get banned. Don't give ttb to disable
   the ban system once activated.
  
  

• KICK REPEAT
  

   Syntax: /msg BotServ  KICK #channel REPEAT {ON|OFF} [ttb [num]]
  
   Sets the repeat kicker on or off. When enabled, this
   option tells the bot to kick users who are repeating
   themselves num times (if num is not given, it
   defaults to 3).
  
   ttb is the number of times an user can be kicked
   before it get banned. Don't give ttb to disable
   the ban system once activated.
  
  

• KICK BADWORDS
  

   Syntax: /msg BotServ  KICK #channel BADWORDS {ON|OFF} [ttb]
  
   Sets the bad words kicker on or off. When enabled, this
   option tells the bot to kick users who say certain words
   on the channels.
  
   You can define bad words for your channel using the
   BADWORDS command. Type /msg BotServ HELP BADWORDS for
   more information.
  
   ttb is the number of times an user can be kicked
   before it get banned. Don't give ttb to disable
   the ban system once activated.
   
  

• BADWORDS
  

   Syntax: /msg BotServ  BADWORDS channel ADD word [SINGLE | START | END]
           BADWORDS channel DEL {word | entry-num | list}
           BADWORDS channel LIST [mask | list]
           BADWORDS channel CLEAR
   
   Maintains the bad words list for a channel. The bad
   words list determines which words are to be kicked
   when the bad words kicker is enabled. For more information,
   type /msg BotServ HELP KICK BADWORDS.
   
   The BADWORDS ADD command adds the given word to the
   badword list. If SINGLE is specified, a kick will be
   done only if an user says the entire word. If START is 
   specified, a kick will be done if an user says a word
   that starts with word. If END is specified, a kick
   will be done if an user says a word that ends with
   word. If you don't specify anything, a kick will
   be issued every time word is said by an user.
   
   The BADWORDS DEL command removes the given word from the
   bad words list.  If a list of entry numbers is given, those
   entries are deleted.  (See the example for LIST below.)
   
   The BADWORDS LIST command displays the bad words list.  If
   a wildcard mask is given, only those entries matching the
   mask are displayed.  If a list of entry numbers is given,
   only those entries are shown; for example:
  
      BADWORDS #channel LIST 2-5,7-9
         Lists bad words entries numbered 2 through 5 and
         7 through 9.
         
   The BADWORDS CLEAR command clears all entries of the
   bad words list.
  
  

• SAY
  

   Syntax: /msg BotServ  SAY channel text
   
   Makes the bot say the given text on the given channel.
  
  

• ACT
  

   Syntax: /msg BotServ  ACT channel text
   
   Makes the bot do the equivalent of a "/me" command
   on the given channel using the given text.
  
  

• SERVADMIN HELP
  

   
   The following command is available to Services admins:
   
       BOT              Maintains network bot list
  
  

• SERVADMIN BOT
  

   Syntax: /msg BotServ  BOT ADD nick user host real
           BOT CHANGE oldnick newnick [user [host [real]]]
           BOT DEL nick
           BOT LIST
   
   Allows Services admins to create, modify, and delete
   bots that users will be able to use on their own
   channels.
   
   BOT ADD adds a bot with the given nickname, username,
   hostname and realname. Since no integrity checks are done 
   for these settings, be really careful.
   BOT CHANGE allows to change nickname, username, hostname
   or realname of a bot without actually delete it (and all
   the data associated with it).
   BOT DEL removes the given bot from the bot list.  
   BOT LIST is an alias of BOTLIST and just lists all
   bots available on the network.
   
   Note: if you create a bot that has a nick that is 
   registered, it will be dropped. Also, if an user is
   currently using the nick, it will be killed.
  
  

• SERVADMIN SET
  

   
   These options are reserved to Services admins:
   
       NOBOT            Prevent a bot from being assigned to 
                           a channel
       PRIVATE          Prevent a bot from being assigned by
                           non IRC operators
  
  

• SERVADMIN SET NOBOT
  

   Syntax: /msg BotServ  SET channel NOBOT {ON|OFF}
   
   This option makes a channel be unassignable. If a bot 
   is already assigned to the channel, it is unassigned
   automatically when you enable the option.
   
   Limited to Services admins.
  
  

• SERVADMIN SET PRIVATE
  

   Syntax: /msg BotServ  SET bot-nick PRIVATE {ON|OFF}
   
   This option prevents a bot from being assigned to a
   channel by users that aren't IRC operators.
   
   Limited to Services admins.

Bagi teman² yang sudah sering maen IRC kemungkinan besar sudah tau apa itu psyBNC di mana psyBNC itu adalah salah satu software yang dapat anda gunakan untuk bisa memakai Ip shell yang anda punya untuk keperluan IRC dan juga dapat membuat nick anda online 24 jam walaupun anda telah offline.
Postingan saya ini akan mengutarakan cara Instalasi psyBNC.

 PERTAMA-TAMA APA SAJA UNTUK DI SIAPKAN

1.  Siapakan dulu shell atau ssh anda, shell resmi ataupun yang elegan. Tapi gabi saya lebih nyaman pakai shell yang resmi.
2.  Siapakan program putty untuk menjalankan perintah shell, apabila agan belom mempunyai program putty, agan bisa download di mari
3.  Sekarang kita langsung ada mendownload file psyBNC dengan commands;

• wget http://www.buildersavvy.com/wp-content/psybnc.tar.gz

 Lalu mengektrak file.setelah diekstrak kita masuk ke direktori psyBNC-nya, ketik dengan perintah.?

•  tar -zxvf  psybnc.tar.gz
•  cd psybnc
• make
• make install

 Edit psybnc.conf dengan command pico psybnc ( Yang harus di edit nick owner dan port psyBNC ) apabila sudah di edit save atau CTRL + x
 Saat nya kita menge RUN psybnc

•  ./psybnc

 Sekarang kita conectkan psyBNC yang udah jadi, dengan IP= shell ada tadi ( Misal kan IP shell nya 202.122.85.23 ) dan Port 2012 yang tadi kita buat.
 -> /s ip port
 Lalu add server buat masuk ke server yang kita mau, Misalnya nama server nya irc.indoirc.org
ketik nya di private PsyBNc
- addserver irc.indoirc.org:6667
Jadi deh psybnc kita, Ups Bagi-bagi yaa psybnc nya.
Sekian dahulu cara buat psyBNC dari saya.
Kalau udah jadi jangan lupa ya add nick saya, ident: r pass: ganteng

Mampir ya ke server saya yaitu: 

irc.indoirc.org

port 6667

FREE psyBNC and ZNC

to  #ZNC