# $EPIC: dcc,v 1.3 2001/05/08 23:23:29 jnelson Exp $
Synopsis:
   dcc [<command> [<arguments>]]

Description:
   DCC stands for Direct Client-to-Client connection.  The DCC 
   command manages all off these connections.  There are two primary uses for 
   DCC; chatting with other users without having to use the irc network; and
   file transfers.  These are examples; they are not the limit of DCC's
   capabilities.

   DCC connections are offered with CTCP DCC requests.  This means that you
   need to have a way to send a message to the person you want to offer
   the DCC to, typically you have to be on the same network.

   DCC offers that others make to you are considered CTCP messages as far as 
   IGNORE and flood control and the like go.

   DCC requires that the INITIATOR be able to accept inbound connections to
   their host.  Firewalls often preclude this possibility and so if you are
   behind a firewall you will not be able to initiate DCC connections.

   If both you and the person you want to talk to are behind a firewall
   which disallows inbound connections then you will not be able to use DCC 
   at all.  This is not a restriction in EPIC or in the DCC specification; 
   it is simply how the internet works.

Aliases:
   Using DCC with no arguments is the same as DCC LIST.

See Also:
   ctcp(1); on(5) dcc_connect, dcc_lost, dcc_request
