next up previous contents index
Next: Network Related Commands Up: Let's Go! Previous: Channel and User

Client to Client Protocol

 
Table: Client to Client commands 

/CTCP <nickname> <command> [<arguments>]   CTCP 
allows you to perform certain client specific actions on the network.

/CTCP Nap VERSION
*** CTCP VERSION reply from Nap: ircII 2.2 *IX :ircII 2.2, SL0 The one
   you thought you'd never see.

This can be used to get information about how long a person has been idle:

/CTCP Nap FINGER
*** CTCP FINGER reply from Nap: PIOCH Nicolas - Nap on IRC, X90,
   (pioch@poly.polytechnique.fr) Idle 0 seconds

There are many others CTCP commands, and new ones are introduced all the time. There is a mechanism for you to find out what you can use: CTCP CLIENTINFO. To find out about your own client services, execute a CLIENTINFO on yourself.

/CTCP Nap CLIENTINFO
*** CTCP CLIENTINFO reply from Nap: SED VERSION CLIENTINFO USERINFO ERRMSG
   FINGER TIME ACTION DCC UTC PING :Use CLIENTINFO <COMMAND> to get more
   specific information

If you're interested in this powerful CTCP mechanism, have a look in the various ircII help files. `` /HELP CTCP'' might tell you more... However the client-to-client protocol has a very powerful feature: allowing two people to exchange files.

To send small text files, electronic mail is probably the best solutiongif. However, ircII provides you a way to establish Direct Client Connections (`` DCC'') to perform functions like sending or receiving files.

If NickA wants to send a file to NickB, then NickA should type
/DCC SEND NickB filename

On NickB's screen will appear
*** DCC SEND (filename) request received from NickA
If he wants to get the file, he just needs to type `` /DCC GET NickA filename''

A few seconds later,
*** DCC GET connection with NickA established
*** DCC GET filename connection to NickA completed
will inform both users that data transfer has been successfully completed.

Here's a quick overview of the subject:

/DCC <function> [<arguments>]   DCC
Handles direct connections to remote clients. The behavior of DCC is determined by the specified <function>.

/DCC SEND <nickname> <filename>   DCC SEND  
Initiates a file transfer by direct client connection.

/DCC GET <nickname> <filename>   DCC GET 
Accepts a file transfer by direct client connection. The sender must first have offered the file with DCC SEND.

/DCC CLOSE <type> <nickname> [<arguments>]   DCC CLOSE  
Ends an unwanted DCC connection or offer. The <type>, <nickname> and <arguments> must be the same as those shown by `` /DCC LIST''. If the arguments are not supplied, the oldest connection of the specified type is closed.

/DCC LIST   DCC LIST 
Shows current DCC connections with their types, status and nicknames involved.

More details can be found in ircII online help: try `` /HELP DCC''... for more information.

However, if someone asks you to send him a file, don't do it unless you exactly know what you are doing. For instance, never send the password file of your system to anybody. This could grant crackers illegal access to your machines, and put you and your system administrator in much trouble.

DCC also allows two clients to establish a direct client connection for chat. This is a secure form of communication, since messages will not be sent through the IRC network.

/DCC CHAT   DCC CHAT 
initiates a direct client connection chat to the given nick, who must respond with DCC CHAT. Once established, messages are sent over it with `` /MSG =NickName ...''.



next up previous contents index
Next: Network Related Commands Up: Let's Go! Previous: Channel and User


Nikos Drakos
Thu Jan 12 11:58:54 GMT 1995