Ragnarok Zero Online

Aku Cuma Seorang Blogger Yang Cinta Seo

2010-01-04T03:29:00.000+07:00

postingan ini hanya ngeping ke postingan yang lain yaitu Aku Cuma Seorang Blogger Yang Cinta Seo - Aku Cuma Seorang Blogger Yang Cinta Seo - Aku Cuma Seorang Blogger Yang Cinta Seo.

Dukung Ridwan Yazid Jadi Bupati Bengkalis 2010-2015

2010-01-02T00:09:00.000+07:00

Dukung Ridwan Yazid Jadi Bupati Bengkalis 2010-2015 sebagai bentuk dukungan juga untuk blogger anti login dari ragnarok zero yang sudah lama vakum kini coba ngeblog lagi, selain itu juga saya dukung untuk kontes Festival Museum Nusantara dan Peluang Usaha Ahasu Gnaulep.

Ngomong-ngomong soal kontes, saya jadi tertarik nih ikutan kontes, pengin nyoba juga... hehehe... oya, mengenai artikel Dukung Ridwan Yazid Jadi Bupati Bengkalis 2010-2015 saya kopas dari blog anti login ya. nih...

Mari kita Dukung Ridwan Yazid Jadi Bupati Bengkalis 2010-2015 karena beliau adalah orang asli mandau atau duri, jadi Dukung Ridwan Yazid Jadi Bupati Bengkalis 2010-2015 adalah support dari saya untuk calon bupati bengkalis.

Dukung Ridwan Yazid Jadi Bupati Bengkalis 2010-2015.

1. Profile & Background

Ridwan yazid adalah putra asli kelahiran mandau, kita semua tahu bahwa mandau adalah wilayah terbesar dalam kemajuan bengkalis. Nah kapan lagi putra asli mandau memimpin?, sekarang saatnya. Bapak Ridwan Yazid adalah seorang bapak atau ayah yang tidak pernah menyerah dalam menafkahi keluarganya, sifat pantang putus asa, jujur, setia dan adil membuat keluarga merasa sangat nyaman dan bangga memiliki ayah seperti bapak Ridwan Yazid.

Sedikit cerita, sekitar beberapa tahun yang lalu...seorang Ridwan Yazid bukanlah siapa-siapa, hidup dengan seorang istri dan 2 orang anak (saat ini memiliki 6 orang anak). Bekerja dari subuh, jam 5 pagi - 8 malam hanya sebagai pekerja keras di sebuah PT. Anda tahu, tidak sedikit orang yang menghina bahkan mencacinya. Tapi kesabaran yang dimilikinya tidak cukup untuk membuatnya gentar!...

Saya masih ingat ketika dia dan salah satu anaknya (saya) berkunjung ke rumah temannya. Saya melihat ada sebuah game, ketika itu adalah nitendo yang sedang dimainkan oleh anak temannya. Saya mencoba game tersebut, dengan mata berkaca-kaca dan sedikit senyum ketika ia mendengar perkataan saya "pa belikann itu". Saya tidak tahu apa yang ia rasakan saat itu (maklum saya masih kecil hahaha), tidak tahu bagaimana keadaan keluarga. Tapi seperti yang saya katakan sebelumnya, "Ia adalah Ayah Yang sangat kami banggakan!", mainan game tersebut sudah terletak rapi beberapa hari setelah saya meminta. Dengan wajah berseri-seri saya langsung mencoba game tersebut setelah pulang sekolah.

Tahun Berganti tahun, hidup berpindah dari sebuah kota ke kota lainnya demi menafkahi keluarga (saat itu bapak ridwan yazid sudah menjadi pegawai negeri biasa). Tidak pernah putus asa dan terus berusaha, keyakinan yang dimilikinya membuat saya salut! (dunia itu berputar, kelak kita akan berada di atas, ALLAH itu maha Adil!, hal ini yang menjadi motto hidup saya sampai saat ini), akhirnya berkat kegigihannya tersebut ia akhirnya menjadi Pemimpin Mandau atau duri. Satu-satunya pemimpin yang mampu membawa angin segar bagi kemajuan wilayah mandau,,,

2. Kinerja

Ketika memimpin Mandau, anda semua melihat dan merasakan kemajuan yang sangat pesat. Salah satunya adalah pembangunan jalan atau perbaikan jalan. Hampir seluruh jalan di duri diperbaiki atau dibuat baru (di aspal). Awal saya datang ke duri, jalanan disana hanya dibalut tanah kuning :D.

Tegas, adil, jujur, apa adanya dan tidak neko-neko adalah sifat yang sangat membuat saya kagum ketika ia memimpin mandau. Tidak ada kasus korupsi alias bersih, ramah kepada seluruh masyarakat dan tampil apa adanya (walau saat itu sudah menjadi camat mandau tapi ia selalu bersifat seperti biasa). Walaupun banyak para penjilat yang mendatanginya (padahal dulu menghina), tapi ia tetap menerimanya dengan lapang hati.

Selalu memerhatikan atau turun langsung ke lapangan. Ketika memimpin, bapak ridwan yazid selalu turun ke lapangan apabila ada suatu planning atau projek ataupun permasalahan, ia juga mempertimbangkan masukan-masukan dari masyarakat lainnya. Tidak sedikit pemimpin yang hanya diam di kantor (alasan sibuk) lalu menyuruh bawahannya untuk memantau, hasilnya tentu saja tidak memuaskan padahal mereka sudah dibayar besar untuk melakukan hal tersebut. Nah hal ini sangat berbeda dengan bapak Ridwan Yazid.

3. Fisi

Apabila anda memepertanyakan apa fisi dari bapak Ridwan yazid?, saya hanya bisa mengatakan "Membawa Bengkalis ke arah yang lebih baik, dari segala bidang"!. Saya tidak bisa berkata banyak, karena saya tahu bagaimana bapak ridwan yazid dalam memimpin (talk less do more).

Anda butuh janji atau bukti?, jika anda percaya janji-janji,,,maka saya sangat menyayangkan hal tersebut. Jika butuh bukti, maka "Ayo Dukung H. A. Ridwan Yazid, S.Sos Jadi "BUPATI BENGKALIS" 2010-2015".

Jadi calon bupati bengkali yang musti anda dukung adalah ridwan yazid, oleh karena itu Dukung Ridwan Yazid Jadi Bupati Bengkalis 2010-2015.

Sumber Daya Professional dan Tanggung Jawab Bagi Pemerintahan Indonesia

2009-12-05T15:16:00.000+07:00

Ragnarok Zero juga ikut meramaikan kontes seo Sumber Daya Professional dan Tanggung Jawab Bagi Pemerintahan Indonesia bersama blogger anti login dan tips seo blog / pinky.
Keyword Sumber Daya Professional dan Tanggung Jawab Bagi Pemerintahan Indonesia menjadi andalan utama untuk memenangkan kontes seo berhadiah domain .com setahun ini. jadi mari kita dukung kontes ini. :)

Writing automatonshttp://www.irchelp.org/irchelp/ircprimer.html#Start

2008-03-21T07:52:00.001+07:00

2.10 Writing automatons
An automaton, (also called robot or service), is a program that is connected to the IRC network to provide services. Many people try to set that up with a few ircII commands like:

on ^msg "% help" notice $0 This is LameBot 1.0

However, you should know that setting up an automaton using ircII ON facilities is quick and dirty, and should be reserved for robots that rely on ircII specific features such as DCC (file servers for instance). Writing a program in C, perl or any decent programming language should take longer in the beginning, but your efforts will be rewarded. You can download skeletons of such programs on some ftp sites that keep IRC related stuff (check in the Frequently Asked Questions part).

Although most robots-writers believe they have created a "smart thing", 99% of the robots online happen to be a nuisance to the IRC community, because a few simple rules were not respected by their owners. The main idea is that robots should neither be seen nor heard:

1. automatons should be clearly identified as such, having "bot","serv" or "srv" in their nickname.

2. they should use NOTICES to communicate with the rest of the world, and not reply to NOTICES they get.

3. they should be able to always be killed (craziness is a frequent disease among robots).

4. they should be able to be killed remotely by their owner via IRC.

5. they should not give access to their owner's real files, (bandits have already been able to crack people's accounts through their robots).

6. they should not send messages to channels (unless the channel is dedicated to that robot).

7. they should not flood channels with MODE changes. Basically, if you have such a command as:

on -JOIN "Lamer #BotTub" mode #BotTub +o Lamer

then you are wrong. Because this is what you will get:

*** Lamer (clueless@where.the.hell) has joined channel #bottub
*** Mode change "+o Lamer" on channel #bottub by LameBot
*** Mode change "+o Lamer" on channel #bottub by StupidSrv
*** Mode change "+ooo Lamer Lamer Lamer" on channel #bottub by FloodServ
*** Mode change "+o Lamer" on channel #bottub by Dumbbot

And this will get boring very soon, so don't be surprised if such robots get banned from most channels. A good kludge is to wait until someone asks explicitly the robot to be opped on a channel. This could be:

on -MSG "Lamer op me on #BotTub" mode #BotTub +o Lamer

If you don't respect rules 2 and 6 above, this may happen too:

*** TalkBot (clueless@where.the.hell) has joined channel #bottub
Hi TalkBot!
Hello LameBot! How are you?
*** Mode change "+o TalkBot" on channel #bottub by LameBot
Fine thanx.
Thank you for the op, LameBot.
No problem, TalkBot.
*** Signoff: Talkbot (ircserver.irc.edu where.the.hell)
*** TalkBot (clueless@where.the.hell) has joined channel #bottub
*** Mode change "+o TalkBot" on channel #bottub by where.the.hell
*** Mode change "+o LameBot" on channel #bottub by TalkBot
*** Mode change "+o TalkBot" on channel #bottub by LameBot
Thank you for the op, LameBot.
No problem, TalkBot.
...

See? Remember the golden rule:

A smart bot won't act unless explicitly asked by someone to.

2.9 Sample .ircrc

2008-03-21T07:51:00.002+07:00

2.9 Sample .ircrc
As a sample, here's part of my .ircrc file. Since ircII2.2, this file can be found in the "script" directory, and loaded with "/load ircprimer"

# Sample .ircrc script, from the IRCprimer v1.1
# -------------------------------------------------------------------
# IRCII sample configuration file (~/.ircrc) (Nicolas Pioch)
# -------------------------------------------------------------------
# The aim of this file is to shorten all useful commands to 1 letter.

set NOVICE off
set INPUT_ALIASES off
set AUTO_WHOWAS on
set SHOW_CHANNEL_NAMES on
set SHOW_AWAY_ONCE on

# Speeds up ircII display 2 times
set SCROLL_LINES 2

# Put Hack notices down under
on ^SERVER_NOTICE "\*\*\* Notice -- Hack: *" set status_user Hack: $4-

# Modified killpath script from YeggMan
ALIAS kpath ECHO ### Last received KILL for $nkp.path
@ nkp.path = []
ALIAS nkp.msg ECHO ### $Z -- KILL by $1 for $0 $2-
ALIAS nkp.idx @ FUNCTION_RETURN = RINDEX(! $0) + 1
ALIAS nkp.srv @ FUNCTION_RETURN = INDEX(. $MID($nkp.idx($0) 512 $0))
ON ^SERVER_NOTICE "\*\*\* Notice -- Received KILL*" {
# if (index(. $mid(${rindex(! $11) +1} 512 $11))
IF ( nkp.srv($11) > -1 )
{ nkp.msg $7 $9 }
{ nkp.msg $7 $9 $12- }
@ nkp.path = [$7-]
}

# Function to strip the less significant part of an internet hostname
# $userdomain(username@host.subdomain.dom) returns username@subdomain.dom
# This eliminates the hostname which may change frequently
alias userdomain {
@ function_return = LEFT($INDEX(@ $0) $0)##[@]##MID(${1+INDEX(. $0)} 99 $0)
}

# Who is that ?
on ^msg * echo *$0!$userdomain($userhost())* $1-

# /w [] get info on someone
# /q [] query someone
# /m send a message
# /n send a notice
# /r reply to last message I got
# /a followup on my last message

alias w whois
alias q query
alias m msg
alias n notice
alias r msg $,
alias a msg $.

# /j join a channel
# /l list people in a channel
# /ll list in the current channel
# /i [] invite someone
# /hop leave the current channel

alias j join
alias l who
alias ll who *
alias i invite
alias hop part $C

# /o [ ] give channel op status
# /d [ ] remove channel op status
# /k kick someone
# /mo [+|-] change current channel mode

alias o mode $C +ooo
alias d mode $C -ooo
alias k kick $C
alias mo mode $C

# the "wrong person" alias! /oops to resend message to
alias oops {
@ _whoops = [$B]
msg $. Whooops ! Please ignore, that wasn't meant for you.
msg $0 $_whoops
}

alias unset set -$*
alias unalias alias -$*
alias NickServ msg NickServ@Service.de
alias NoteServ msg NoteServ@Service.de

# -------------------------------------------------------------------

2.8 Further into ircII Wizardry

2008-03-21T07:51:00.001+07:00

2.8 Further into ircII Wizardry
Note: This part should be reserved for experienced IRC'ers.

Because ircII is not a simple client program, but an Operating System, its programming language is just as simple as you could expect (it's horrendous), but if you want to get into it, here's a little note for you.

There are a few Unix environment variables you can set in your shell configuration file, but you need to find out your shell name before that. "echo $SHELL" should give you a hint.

Table 12: Setting environment variables
----------------------------------------
Shell type Shell name Command
~~~~~~~~~~ ~~~~~~~~~~ ~~~~~~~
Bourne shells sh $ VARNAME="value" ; export VARNAME
ksh $ export VARNAME="value"
bash $ export VARNAME="value"
C-shells csh % setenv VARNAME "value"
tcsh > setenv VARNAME "value"

Table 13: Environment variables
--------------------------------
Name Effects
~~~~ ~~~~~~~
HOME where your home directory is
IRCNAME any lunacy you want instead of your real name
(text that appears between parentheses in a WHOIS)
IRCNICK your default IRC nickname
IRCPATH a directory path to LOAD scripts
IRCRC a file to use instead of your $HOME/.ircrc
IRCSERVER a default server list for ircII
TERM your terminal type

The command character, (usually "/irchelp/"), is only necessary when you type commands interactively. When you program things it is no longer needed although it used to be.

Table 14: Advanced commands
---------------------------
Keyword Action
~~~~~~~ ~~~~~~
# same as COMMENT except for the lenght
@ performs variable expressions
ALIAS creates command aliases
ASSIGN creates user variables (expandable with $)
BIND binds a keystroke sequence to a function

CD changes ircII working directory
COMMENT does nothing, but very useful. Strange, uh?
ECHO displays all of its arguments
EXEC allows you to start subprocesses
FLUSH flushes all pending output from the server

IF standard boolean expression checker
LOAD loads an ircII command script file
ON sets up actions to occur when certain events happen
REDIRECT forwards the output from a command
SAVE saves all ircII settings into a file

SAY same as sending text to a channel
SEND same as sending text to a channel
SET sets a variable to a given value
SLEEP suspends ircII for a few seconds
TYPE simulates keystrokes

WAIT waits for all server output to finish
WHILE another control command to make loops
WINDOW lets you manipulate multiple "windows" in ircII
XECHO like ECHO, but takes flag arguments

If you want to type to the channel from within an ALIAS or on BINDing, you have to use SAY or SEND.

The ";" has a special meaning in ALIASes, BINDings and ONs: it's treated as command separator, that means you can execute multiple commands in a row separated by semicolons. The semicolons are not considered separators when you use them interactively, (to be able to type ";-)"), and within an ircII script file. You can escape the meaning of ";" in an ALIAS with "\;".

When you use ircII on a (semi)regular basis, you will discover that every time you start the program you will issue the same initialization sequence. If that is the case, I have good news for you: you don't have to do that anymore! ircII will, at startup, load a file called ".ircrc", (full path: $HOME/.ircrc). It will treat each line in that file as if you typed it manually.

For example, if the content of your .ircrc file is:

JOIN #Twilight_Zone

then each time you will start IRC, you will join this channel.

Advanced commands may come in handy if you need them. Feel free to browse in ircII online help to find out more about them. A few of them are probably worth learning.

2.7 Quick Reference Panel

2008-03-21T07:50:00.002+07:00

2.7 Quick Reference Panel

Keyword Action
------- ------
! recalls previous commands for re-editing
ADMIN displays information about a server
AWAY leaves a message saying you're not paying attention
CLEAR puts some white space on your screen
CTCP performs certain client specific actions

DATE shows server current date and time
DCC handles direct connections to remote clients
DESCRIBE sends anything about you to a person or channel
HELP prints help on the given command
HISTORY displays the command history

IGNORE removes output from specific people off your screen
INFO shows useless information about IRC
INVITE sends an invitation to another user
JOIN sets your current channel
KICK gets rid of someone on a channel

LASTLOG lists the most recent messages
LEAVE leaves a channel
LINKS shows servers on the IRC network
LIST lists channels, number of users, topic
LUSERS gives a brief listing of users, servers and operators

ME sends anything about you to a channel or QUERY
MODE changes channel mode
MOTD displays the server message-of-the-day
MSG sends a private message
NAMES shows the nicknames of users on each channel

NICK changes your nickname
NOTICE sends a private message
NOTIFY warns you of people logging in or out IRC
QUERY starts a private conversation
QUIT exits your IRC session

SERVER switches your primary server
STATS shows some irc server usage statistics
TIME shows server current date and time
TOPIC changes the topic of the channel

TRACE shows the server connections of the given machine
USERS prints users logged on the server machine
VERSION shows client and server version number
WHO gives a listing of users
WHOIS displays information about someone

WHOWAS displays information about someone who just left

2.6 Network Related Commands

2008-03-21T07:50:00.001+07:00

2.6 Network Related Commands
If you encounter any problem, contact your local IRC-Administrator or an IRC-Operator. An IRC-Admin is a person who has access to all files concerning 'ircd' (the server program). An IRC-Operator or "IRC-op" is a person who has privileges given to him by an IRC-Admin and tries to maintain a fast reliable IRC network. Information on how you can find out who s/he is, can be found below.

Each time you are prompted for a server name, remember you can supply the nickname of someone being connected on that server instead. This may be useful at times.

Table 11: Network related commands
-----------------------------------
Keyword Action
~~~~~~~ ~~~~~~
ADMIN displays information about a server
LINKS shows the servers on the IRC network
SERVER switches your primary server
MOTD displays the server message-of-the-day
USERS prints users logged on the server machine
DATE shows server current date and time
TIME shows server current date and time
LUSERS gives a brief listing of users, servers and operators
TRACE shows the server connections of the given server
STATS shows some irc server usage statistics
INFO shows useless information about IRC
VERSION shows client and server version number

/ADMIN []

Displays the administrative details about the given server. If no server is supplied, the server you are connected to is used.

/ADMIN
### Administrative info about poly.polytechnique.fr
### Ecole Polytechnique, Palaiseau, FRANCE
### IRC-Administrator Nicolas Pioch (Nap@IRC)
###

/LINKS [[] ]

Shows a list of servers currently connected to the IRC network. If is given, /LINKS asks the given for a list of servers matching the given expression, (this list can get very long!).

/LINKS *po*
*** nova.unix.portal.com 7 Cupertino California, USA
*** poe.acc.Virginia.EDU 6 University of Virginia 2.7.1f
*** polaris.utu.fi 9 University of Turku, Finland
*** polaris.ctr.columbia.edu 6 Columbia University, New York City
*** csd.postech.ac.kr 4 POSTECH Computer Science Dept.
*** cdc853.cdc.polimi.it 2 Polytechnic of Milan, Italy
*** poly.polytechnique.fr 0 Ecole Polytechnique, Paris, FRANCE

/SERVER [| []]

Switches your primary server to the supplied at the specified . If no port number is given, the default port number is used (normally 6667).

/SERVER poly.polytechnique.fr 6667
*** Connecting to port 6667 of server poly.polytechnique.fr
*** Welcome to the Internet Relay Network, Nap
*** Your host is poly.polytechnique.fr, running version 2.7.2g.ID
*** This server was created Sat Jan 16 1993 at 12:16:10 MET

Occasionally, you can switch servers faster than the IRC network can send out the information that you have left your previous server. So don't be surprised if you are told your nickname is already in use... Just wait a moment and set it with /NICK again.

/MOTD []

Gives the Message-Of-The-Day for the named server. If no server is given, your server is used.

/MOTD
MOTD - poly.polytechnique.fr message of the day -
MOTD - _____________________________________
MOTD - /\ \
MOTD - \_| Bienvenue sur le serveur |
MOTD - | Internet Relay Chat |
MOTD - | de l'Ecole Polytechnique, FRANCE |
MOTD - | _________________________________|__
MOTD - \_/___________________________________/
MOTD -
MOTD - | | | En cas de probleme,
MOTD - )_) )_) )_) tapez / admin
MOTD - )___))___))___)\
MOTD - )____)____)_____)\\ Nicolas PIOCH
MOTD - _____|____|____|____\\\__ Nap sur IRC
MOTD - --\ Welcome to IRC ! /---------
MOTD - ^^^^^^^^^^^^^^^^^^^^^ ^^^ ^^^
* End of /MOTD command

/USERS []

Shows the users logged into the machine where the server is running, (it's up to the server administrator to implement this feature or not. It may not work on some machines).

/USERS
*** UserID Terminal Host
*** pioch ttyp9 rotule.polytechn
*** pioch ttypc rotule.polytechn
*** pioch ttyq0 rotule.polytechn
*** pioch ttyq1 rotule.polytechn

/DATE []
/TIME []

Shows the current time of day and date. If a server is specified, the time of day and date are reported from that server. DATE and TIME are identical.

/DATE
*** poly.polytechnique.fr Saturday June 20 1992 -- 02: 35 +01:00

/LUSERS

Gives a brief listing of the number of servers, operators and users matching the given , as seen from the specified .

/LUSERS
*** There are 1008 users and 291 invisible on 135 servers
*** 72 users have connection to the twilight zone
*** There are 458 channels
*** I have 16 clients and 4 servers
*** 22 maximum connections, 19 clients

/TRACE []

Shows the server connections of the given .

/TRACE
*** Serv Class[9] ==> 134S 1331C eff.org[192.88.144.3]
*** Serv Class[8] ==> 1S 6C Julia.Enst.FR
*** Serv Class[8] ==> 1S 6C Eurecom8.Cica.FR[192.70.34.208]
*** Serv Class[1] ==> 2S 0C athina.cc.uch.gr[147.52.80.102]
*** Serv Class[8] ==> 1S 5C dafne.mines.u-nancy.fr[192.70.66.2]
*** Serv Class[8] ==> 1S 0C cnam.cnam.fr
*** Class 0 Entries linked: 16
*** Class 9 Entries linked: 1
*** Class 8 Entries linked: 4
*** Class 1 Entries linked: 1

/STATS c|i|k|l|m|u|y []

Shows some irc server usage statistics.

/STATS u
*** Server Up 12 days, 12:28:44

/INFO []

Shows information about the IRC creators, debuggers, slaves and a lot of other people who no longer have much to do with IRC.

/VERSION

Shows the ircII version number and the version number of the server.

/VERSION
*** Client: ircII 2.2
*** Server poly.polytechnique.fr: ircd 2.7.2g.Nap+6(privacy).

2.5 Client to Client Protocol

2008-03-21T07:49:00.002+07:00

2.5 Client to Client Protocol
/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

Table 10: Client to Client Commands
------------------------------------
Keyword Action
~~~~~~~ ~~~~~~
CTCP performs certain client specific actions
DCC handles direct connections to remote clients
DCC SEND initiates a file transfer
DCC GET accepts a file transfer
DCC CLOSE ends a DCC connection or offer
DCC LIST shows current DCC connections
DCC CHAT initiates a secure chat between two clients

There are many other 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 to get more specific information

If you are 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 solution, (don't rely on the user@host given by the WHOIS command to send mail. However, ircII provides you a way to establish Direct Client Connections ("DCC") to perform functions like sending and 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, (NickB), 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 []

Handles direct connections to remote clients. The behaviour of DCC is determined by the specified .

/DCC SEND

Initiates a file transfer by direct client connection.

/DCC GET

Accepts a file transfer by direct client connection. The sender must first have offered the file with DCC SEND.

/DCC CLOSE []

Ends an unwanted DCC connection or offer. The , and 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

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.

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 a lot of trouble.

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

/DCC CHAT

Initiates a direct client connection chat to the given nick, who must repond with DCC CHAT. Once established, messages are sent over with "/MSG =Nickname ...".

2.4 Channel and User Modes

2008-03-21T07:49:00.001+07:00

2.4 Channel and User Modes
Channels can have additional constraints, which can be set by the MODE command, (most of the information in this section can also be obtained by issuing "/HELP MODE"). To understand this, recall that the first person to JOIN a channel effectively creates it and is initially "in charge" of the channel, ("Channel Operator" or "chanop"). S/he can subsequently add those constraints, make other people chanops at leisure.

Table 7: Mode commands
-----------------------
Keyword Action
~~~~~~~ ~~~~~~
MODE changes channel or user mode

Public is the default mode for a channel. When someone is on a public channel, he can be seen by all other users, (if his own user mode permits this). Anyone can notice users on a public channel and join such a conversation.

Private means that, although anyone can see members of such a channel, you can't tell what channel they are on unless you are already on that channel with them. They just appear as "Prv: *" in LIST or NAMES. Since the number of potential channels is in the billions, this is quite some security - all you give away is the acknowledgement that you're IRCing.

If you are on a secret channel, someone who is not on the same channel can't even see that you are there. Your name does not show up in a LIST of active users. The only indication of your presence is that, when entering IRC, all new users are told that there are "NNNNN users on XXX servers". If someone checks on all users and finds less than NNNNN of them, he knows that other people are hiding on secret channels. But a secret channel user still cannot be found except by brute-force checking through all channels, a hopeless proposition in the face of the huge number of possible channel names. Security through obscurity finally means something.

/MODE | [[+|-] []]

Allows channel operators to change channel mode, or any user to change their personal mode, (don't use this co mmand too often, it floods the net with worthless information).

/MODE #Twilight_Zone +m
*** Mode change "+m" on channel #Twilight_Zone by Nap

/MODE Nap -i
*** Mode change "-i" for user Nap by poly.polytechnique.fr

And this is how to give 'chanop' status to someone on the channel

/MODE #Twilight_Zone +o sojge
*** Mode change "+o sojge" on channel #Twilight_Zone by Nap

A + or - sign determines whether the mode should be added or deleted. Try typing "/HELP MODE" to get further information. Channels can be moderated (only chanops can talk), secret, private, with a limited number of users, anonymous, invite-only, topic-limited, with a list of banned users.

The MODE command also allows you to modify your personal parameters, your "user mode". You can check your usermode with the command "/MODE " or sometimes "/UMODE". Note that user mode +i may be the default on some servers, in order to protect privacy of users. This should not be seen as a problem, since any user can change his/her personal mode whatever defaults a server may set.

Table 8: Channel modes
-----------------------
ModeChar Effects on channels
~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
b ban somebody, in "nick!user@host" form
i channel is invite-only
l channel is limited, users allowed max
m channel is moderated, (only chanops can talk)
n external /MSGs to channel are not allowed
o makes a channel operator
p channel is private
s channel is secret
t topic limited, only chanops may change it

Table 9: User modes
--------------------
ModeChar Effects on nicknames
~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
i makes yourself invisible to anybody that does
not know the exact spelling of your nickname
o IRC-operator status, can only be set
by IRC-ops with OPER
s receive server notices
w receive wallops (abused and deprecated)

2.3 Channels and Public Conversations

2008-03-21T07:48:00.000+07:00

2.3 Channels and Public Conversations
On IRC, there are a lot of places where you can "hang out"; those places are called 'channels', (most of the information in this section can also be obtained by issuing "/HELP CHANNEL"). You can compare conversations on a channel to a conversation among a group of people: you see/hear everything that is said, and you can reply to anything that's said. What you type is received by everyone who's willing to listen - and everyone who is late will not hear what was said before, unless repeated by one of the ones who were there. (Who said "real life" ?)

All channels on IRC have names: a "#" sign followed by some kind of text-string, like "#C++" or "#Asians" or "#EU-Opers". Usually, the name of the channel will indicate the type of conversation that's going on in there. Don't count on it, though.

Table 6: Channel commands
--------------------------
Keyword Action
~~~~~~~ ~~~~~~
LIST lists channels, number of users, topic
NAMES shows the nicknames of the users on each channel
JOIN sets your current channel, (same as CHANNEL)
WHO gives a listing of users
INVITE sends an invitation to another user
LEAVE leaves a channel, (same as PART)
KICK gets rid of someone on a channel
TOPIC changes the topic of the channel
ME sends anything about you to a channel or QUERY
DESCRIBE sends anything about you to a person or channel

Every channel has certain characteristics, called channel modes. These will also be explained below. Remember the NAMES and LIST commands; they will show you the names of the existing channels.

/LIST [[] ]

Lists all current "channels", number of users, and topic. The displayed list may be quite long, so you can limit it using flags. "/LIST -MIN n" for instance removes channels with less than 'n' users of the output.

/LIST -MIN 5
*** #aussies 5
*** #amiga 5 Daily Amiga Silence...join&enjoy
*** #hottub 21 Imagine sky, high above...
*** #tuebingen 11 Happy Borthday CHUCK!!!
*** #Christian 6 Jesus!
*** #Twilight_ 15 The Oper Bar & Grill
*** #initgame 5 More players needed!!!!!!!!!!!!
*** #Taiwan 8 Welcome good friends.
*** #espanol 6 EMERGENCIA SE Necesitan Mujeres!
*** #sherwood 7
*** #francais 6 on apprend le japonais (japanese welcome)

/NAMES [[] ]

Shows the nicknames of all users on each "channel", (these may be very long. Remember to filter them with "-MIN n" or "-MAX n").

/NAMES -MIN 5
Pub: #twilight> Mycroft @sojge scorpio @Troy @Avalon @Nap phone
Merlinus Lumberjak @tzoper
Pub: #espanol Cacique Bonjovi leopardo Carina Miguel Cisco r2
Pub: #amiga @gio @Radix @xterm @mama @AmiBot
Pub: #aussies @Bleve @GrayElf @Insomniac @Morkeleb @titus
Pub: #hottub baby @Aldur KnightOrc @Toasty Gwydion @Belkira
@Aiken Edge @Spockobot @Nada @ZBot @Aurik @anna @RedBaron
@Katzen @esashi IceWolf @Eniigma @Digger @TheHeck

To join in the conversation on a certain channel you may use the JOIN command.

/JOIN []

Sets your current channel to the supplied channel.

/JOIN #Twilight_Zone
*** Nap has joined channel #Twilight_Zone
*** Topic: The Gernsback Continuum
*** Users on #Twilight_Zone: Nap msa tober phone @julia @SirLance
igh @Daemon @Avalon @Waftam @Trillian @tzoper

The CHANNEL command has the same effects. Note that if no parameters are given, your current channel is displayed.

Upon entering a channel, you are given useful details about it: list of users talking in that channel, topic... Joining a channel does not cause you to leave your previous channel unless NOVICE is set to ON. See "/HELP SET NOVICE".

Once in a channel, you may wish to get a detailed list of the people IRCing inside. That's where the WHO command comes in handy:

/WHO[|]

Gives a listing of users. "/WHO *" for the list of users in your current channel.

/WHO #Twilight_Zone
Channel Nickname S User@Host (Name)
#Twilight_ Nap H* pioch@poly.polytechnique.fr
(Quidquid latine dictum sit, altum viditur)
#Twilight_ msa H msa@tel1.tel.vtt.fi (Markku Savela)
#Twilight_ tober H ircuser@kragar.eff.org (tober)
#Twilight_ phone H mrgreen@munagin.ee.mu.OZ.AU (Third
row seats to the Cure? WHO ME? nah.. *grin*)
#Twilight_ julia G*@ julie@turing.acs.Virginia.EDU
( Future graduate of ACME Looniversity)
#Twilight_ SirLance G*@ lancelot@tdsb-s.mais.hydro.qc.ca
(Sir Lancelot)
#Twilight_ igh G igh@micom1.servers.unsw.EDU.AU (igh)
#Twilight_ Daemon G*@ frechett@spot.Colorado.EDU
(-=Runaway Daemon=-)
#Twilight_ Avalon H*@ avalon@coombs.anu.edu.au (Avalon...)
#Twilight_ Waftam G*@ danielce@munagin.ee.mu.OZ.AU (Daniel
Carosone)
#Twilight_ Trillian G*@ hrose@rocza.eff.org ( I turn to
stone when you are gone )
#Twilight_ tzoper H*@ tzoper@azure.acsu.buffalo.edu (/msg
tzoper help)

The first field is the current channel, then nickname, status, real name (in internet user@host form), and a small witty comment you can set yourself with the environment variable IRCNAME, (this will be detailed in section 2.8). Status indicates if a user is "H"ere or "G"one, (see AWAY), if IRCop ("*"), and/or a channel operator ("@").

It is also possible, when you are already on a channel, to ask someone to join your channel. The command is called INVITE.

/INVITE []

Invites another user to a channel. If no channel is specified, your current channel is used.

/INVITE Nap
*** Inviting Nap to channel #Twilight_Zone

If you receive an INVITE message, you can type "/JOIN -INVITE" to join the channel to which you were last invited, or simply "/JOIN ".

To leave a channel, just issue a LEAVE command, (PART has the same effects):

/LEAVE

Leave a channel.

/LEAVE #Twilight_Zone
*** Nap has left #Twilight_Zone

Well, you guessed it, if there is a way to invite someone on a channel, there's also the possibility to KICK someone out of it, for example if this person is behaving like a jerk, annoying people or flooding the channel with unwanted information:

/KICK []

Kicks named user off a given channel. Only 'channel operators' are privileged to use this command.

/KICK #Twilight_Zone Target
*** Target has been kicked off channel #Twilight_Zone by Nap

Channels have topics, that indicate the current topic of conversation. You can change this topic on a channel with the TOPIC command.

/TOPIC [[] ]

Changes the topic for the channel.

/TOPIC The silent channel.
*** Nap has changed the topic on channel #EU-Opers to The silent
channel.

At times, you may want to send a description of what you are doing or how you are feeling or just anything concerning you to the current channel or query. It is absolutely good style not to forget the period at the end of the sentence!

/ME

Tells the current channel or query about what you are doing. You can also use your own nickname as command, i.e. you can type the line with a leading slash.

/ME opens up the fridge.
* Nap opens up the fridge.

/Nap reaches out for the orange juice.
* Nap reaches out for the orange juice.

The same goal can be achieved towards a specific nickname using:
/DESCRIBE |

Sends anything concerning you to the or you pass as first argument.

(Note: The look of the result depends on each client version, and might not be exactly the same as in the examples shown here.)

These commands make use of CTCP, a client-to-client protocol crafted to perform specific actions, but not understood by all clients, (more about CTCP in section 2.5). If you get an error message, your description may not have arrived properly.

2.2 Communication and Private Conversation

2008-03-21T07:47:00.001+07:00

2.2 Communication and Private Conversation

Table 5: Private conversation commands
--------------------------------------
Keyword Action
~~~~~~~ ~~~~~~
MSG sends a private message
QUERY starts a private conversation
NOTICE sends a private message
NOTIFY warns you of people logging in or out IRC
IGNORE removes output from specific people off your screen

You can use the MSG command, (usually "M" is an alias for it), to send someone a message that only that person can read.

/MSG |

Send a private message to specified nickname.

/MSG Nap This message is for Nap only.
-> *Nap* This message is for Nap only.

On my screen will appear:

*YourNick* This message is for Nap only.

If you want to send a private message to more than one person, you can specify a list of nicknames separated by commas, (no spaces).

/MSG Nap,Sorg This message for both Nap and Sorg.
-> *Nap* This message for both Nap and Sorg.
-> *Sorg* This message for both Nap and Sorg.

Two special case nicknames are defined. If the nickname is "," (a comma), the message is sent to the last person who sent you a MSG. If the nickname is "." (a period), the message is sent to the last person to whom you sent a message.

You can have a private conversation by only using /MSG. However, typing "/MSG " or "/MSG . " gets cumbersome. That's where the /QUERY command comes in handy.

/QUERY [|]

Starts a private conversation with .

All text you type that would normally be sent to your channel now goes to the supplied nickname in the form of MSGs. To cancel a private conversation, use QUERY with no arguments.

/QUERY Nap
*** Starting conversation with Nap

Blahblahblah
-> *Nap* Blahblahblah

/QUERY
*** Ending conversation with Nap

There is also another command to send messages, called NOTICE. Unlike MSGs, NOTICEs are surrounded by '-' when printed, and no automated responses, (such as generated by IGNORE or an automaton), will be sent in reply. Services, (robots), on IRC often use this form of interaction.

/NOTICE |

Sends a private message to the specified .

/NOTICE Nap Better use /MSG instead of /NOTICE.
-> -Nap- Better use /MSG instead of /NOTICE.

On my screen will appear:

-YourNick- Better use /MSG instead of /NOTICE.

As you begin to make new friends over IRC, you'll want to mark certain nicknames such that you will be warned when they signon or off.

/NOTIFY [[-]]

Adds or removes to the list of people you'll be warned when they enter or quit IRC (in ircII versions prior to 2.2, too many people in the NOTIFY list cause excessive slowness).

/NOTIFY Nap Nappy
*** Signon by Nap detected

/NOTIFY
*** Currently present: Nap
*** Currently absent: Nappy

Eventually, you may wish some day not to see messages from a specific user on your screen. This may happen when someone is dumping large amounts of garbage, or if someone is harassing you. The proper response to such a behavior is to IGNORE that person. IGNORE is a very powerful command, and can be used in many ways. However the basic usage of this tool is the following.

/IGNORE [| [[-]]]

Suppresses output from the given people from your screen. IGNORE can be set by nickname or by specifying a userid@hostname format. Wildcards may be used in all formats. Output that can be ignored includes MSGs, NOTICEs, PUBLIC messages, INVITEs, ALL or NONE. Preceding a type with a "-" indicates removal of ignoring of that type of message.

/IGNORE *@cheshire.oxy.edu ALL
*** Ignoring ALL messages from *@CHESHIRE.OXY.EDU

/IGNORE
*** Ignorance list:
*** *@CHESHIRE.OXY.EDU ALL

/IGNORE *@cheshire.oxy.edu NONE
*** *@cheshire.oxy.edu removed from ignorance list

2. Let's Go!

2008-03-21T07:46:00.002+07:00

2. Let's Go!
2.1 General Commands

Table 4: General commands
--------------------------
Keyword Action
~~~~~~~ ~~~~~~
NICK changes your nickname
QUIT exits your IRC session, (same as BYE, SIGNOFF and EXIT)
HELP prints help on the given command
WHOIS displays information about someone
WHOWAS displays information about someone who just left
AWAY leaves a message saying you're not paying attention

/NICK []

Changes your nickname to whatever you like.

Everyone who wants to talk to you sees this name - also, at the moment, nicknames are limited to 9 characters max. Your nickname will be the same as your login name by default. You can also set an environment variable, IRCNICK, the value of which will be used instead. Nickname clashes are not allowed; this is enforced by the servers. If your intended nickname clashes with someone else's as you enter IRC, you will not be able to enter until you change it to something else.

/NICK Nappy
*** Nap is now known as Nappy

/QUIT []

Exits your IRC session. You can also use BYE, SIGNOFF and EXIT. If a reason is supplied, it is displayed to other people on your channels.

/QUIT Lunch Time!

/HELP []

Shows help on the given command. Note: This is not installed for all clients, which can be kind of annoying.

/HELP HELP
Usage: HELP [command]
Shows help on the given command. The help documentation is set
up in a hierarchical fashion. That means that certain help
topics have sub-topics under them.
[boring stuff deleted]

/WHOIS []

Shows information about someone.

/WHOIS Nap
*** Nap is pioch@poly.polytechnique.fr (Klein bottle for sale...
inquire within.)
*** on channels: @#Twilight_Zone @#EU-Opers
*** on via server poly.polytechnique.fr (Ecole Polytechnique,
Paris, FRANCE ! )
*** Nap has a connection to the twilight zone (is an IRC operator)
*** Nap has been idle 0 seconds

/WHOIS Nappy
*** Nappy: No such nickname

Sometimes WHOIS won't help you much, because the person you want to know more about just left IRC or changed nick. However, you can use WHOWAS to get this information for a while:

/WHOWAS [] []

Shows information about who used the given nickname last, even if no one is currently using it.

/WHOWAS Nappy
*** Nappy was pioch@poly.polytechnique.fr (Artistic ventures
highlighted. Rob a museum.) on channel *private*
*** on irc via server poly.polytechnique.fr (Signoff: Mon Jun 22
20:15:23)

Very often, an unsuccessful call to WHOIS will lead you to try WHOWAS. That's why ircII allows you to "/SET AUTO_WHOWAS ON"; that way, a "*** : No such nickname" message will auto-magically generate a "/WHOWAS ". Try typing "/HELP SET AUTO_WHOWAS" for more information on this topic.

/AWAY []

Leave a message explaining that you are not currently paying attention to IRC. Whenever someone sends you a MSG or does a WHOIS on you, they automatically see whatever message you set. Using AWAY with no parameters marks you as no longer being away.

/AWAY Gone to get a cup of coffee.
*** You have been marked as being away

/AWAY
*** You are no longer marked as being away

1.5 Screen and Keyboard activity

2008-03-21T07:46:00.001+07:00

1.5 Screen and Keyboard activity
IRC is a full-screen utility. It takes over the screen, with the bulk of activity happening in the top (N-2) lines, a status line, (vaguely emacs-like), on the next to last line, and your input being entered on the last line. When typing commands at ircII, you have a minimalist line-editing facility in an emacs style.

Table 1: Editing keys
----------------------
Key Effects
~~~ ~~~~~~~
^P recalls previous command line
^N recalls next command line
^F moves forward one character
^B moves backward one character
^A moves the cursor to the beginning of the line
^E moves the cursor to the end of the line
^D deletes the character under the cursor
^K kills from the cursor to the end
^Y reinserts the last stretch of killed text
^U clears the whole line
^L redraws the screen

Table 2: Editing commands
--------------------------
Keyword Action
~~~~~~~ ~~~~~~
! recalls previous commands for re-editing
HISTORY displays the command history
LASTLOG lists the most recent messages
CLEAR puts some white space on your screen

The ! command is used to recall previous commands in your command history for re-execution. The ! command is unique in that when it is used, it leaves the matching history entry in the input line for re-editing. You can specify a history entry either by its number in the history list, or by a match with a given wildcard expression. For instance, "/!10" will put entry 10 in the history list into the input line. "/!/MSG" will search the history for a line beginning with a /MSG, (a "*" is implied at the end).

/! [|]

Recalls previous commands for re-editing.

/HISTORY []

Displays the command history on the screen. You can specify the number of history entries you wish to view as well.

Almost everything happens in the upper bulk of the screen. This includes both messages from other users, as well as the output of the control commands. Normal messages from other users appear with the originating nickname in . Private messages arrive with the originating nickname in *asterisks*. Messages you send to everyone appear with a preceding "> " whereas messages you send privately to another user appear with "-> *nickname*". Other output (invitations from other users to join channels, and so forth), appears interspersed with other activity on the screen.

Table 3: Simple screen activity
--------------------------------

What is displayed What you typed Sender Recipients
~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~ ~~~~~~ ~~~~~~~~~~
> Morning people Morning, people You Channel
hello some1else Channel
-> *some1else* hi! /msg some1else hi! You some1else (only)
*some1else* wassup? some1else You (only)

Last ircII outputs can be recalled with:
/LASTLOG [| []]

Displays the contents of the lastlog. This is a list of the most recent messages that have appeared on the screen, useful if you inadvertantly miss messages. If no arguments are given, the entire lastlog is displayed. If the first argument is a number, it determines how many log entries to show. Otherwise it is searched for in every lastlog entry. The second argument determines how many lines back to start display from.

/LASTLOG
> Public message I send to all in the channel
Public message from some1else
*some1else* Private message sent to me by some1else
-> *some1else* Private message I send to some1else

Finally, if your screen gets garbage from a 'talk', 'write', 'wall' or any other form of primitive communication (smirk), hit ^L to redraw it, or CLEAR it.

/CLEAR

Clears the screen.

1.4 First Steps

2008-03-21T07:45:00.002+07:00

1.4 First Steps
Note: ircII, the client most people are using, has most of this information online. If you are stuck, type "/HELP" and hit . To escape from HELP mode, keep pressing until your edit line, (the line at the bottom of the screen), is empty. Most of the information in this file can be found typing these commands: "/HELP INTRO" or "/HELP NEWUSER".

All ircII commands begin with a "/irchelp/" character.

The slash is the default command character. Commands are not case sensitive, and can be abbreviated to their first letters: "/SI" and "/sign " stand for /SIGNOFF and will both end your IRC session, (more in section 2.1).

Anything that does not begin with "/irchelp/" is assumed to be a message to someone and will be sent to your current channel, or to a person you are QUERYing, (the QUERY command will be detailed later on, maybe in section 2.2).

If you are not sure about the spelling of an ircII command, type the prefix of that command, and press the ESCape key twice; ircII will give you a listing of commands and aliases that start with that prefix. Don't forget the "/irchelp/" in front of the command though.

/W
*** Commands:
*** WAIT WALL WALLOPS WHICH
*** WHILE WHO WHOIS WHOWAS
*** WINDOW
*** Aliases:
*** W

This is an example. Your screen may show more aliases, and less commands than shown here, or less aliases and more commands - in other words "your mileage may vary."

1.3 Privacy on IRC

2008-03-21T07:45:00.001+07:00

1.3 Privacy on IRC
You should always keep in mind that messages you send to someone over IRC are passed along all the servers between you and and the person you are writing to. When you're sending a letter to someone, any postman on the way could open it and read its contents.

Well, it's the same on the network. Any IRC-Admin could compile their server in "debug" mode and log whatever messages are transmitted through his node, (it has already been done), so a good rule of thumb is not to trust the servers.

IRC IS NOT A SECURE WAY OF COMMUNICATION!

How to establish direct communications between clients will be explained later, (see DCC CHAT in section 2.5). This should be used when you wouldn't want anybody else on IRC to intercept your private messages.

How to behave on IRC

2008-03-21T07:44:00.002+07:00

1.2 How to behave on IRC
The most widely understood and spoken language on IRC is English. However, as IRC is used in many different countries, English is by no means the only language. If you want to speak some other language than English, (for example with your friends), go to a separate channel and set the topic to indicate that. On the other hand, you should check the topic before you move to a channel to see if there are any restrictions about language. On a non-restricted channel, please speak a language everybody can understand. If you want to do otherwise, change channels and set the topic accordingly.

It's not necessary to greet everybody on a channel personally. Usually one "Hello!" or equivalent is enough. And don't expect everybody to greet you back. On a channel with 20 people that would mean one screenful of hellos. It's sensible not to greet, in order not to be rude to the rest of the channel. If you must say hello to somebody you know, do it with a private message. The same applies to goodbyes.

Also note that using your client facilities, (ircII "ON" command, for instance), to automatically say hello or goodbye to people is extremely poor etiquette. Nobody wants to receive auto-greets. They are not only obviously automatic, but even if you think you are polite, you are actually sounding insincere and also interfering with the personal environment of the recipient. If somebody wants to be auto-greeted on joining a channel, he will auto-greet himself.

Remember, people on IRC form their opinions about you only by your actions, writings and comments, so think before you type. If you use offensive words, you'll be frowned upon. Do not "dump" to a channel or user, (send large amounts of unwanted information). This is likely to get you kicked off the channel or killed off from IRC. Dumping causes network "burps", connections going down because servers cannot handle the large amount of traffic anymore. Other prohibited actions include:

* Harassing another user. Harassment is defined as behavior towards another user with the purpose of annoying them.

* Annoying a channel with constant beeping.

* Any behavior reducing the functionality of IRC.

Getting Started

2008-03-21T07:44:00.001+07:00

1.1 Clients and Servers
IRC (original code was written by Jarkko Oikarinen) is a multi-user, multi-channel chatting network. It allows people all over the internet to talk to one another in real-time. It is a functional replacement and improvement to 'talk'; 'talk' is an old, primitive, atrocious, minimalist sort of keyboard/screen conversation tool, using a grotesque, machine- dependent protocol (blah!). IRC does everything 'talk' does, but with better protocol, allowing more than 2 users to talk at once, with access across the aggregate Internet, and providing a whole raft of other useful features.

There are two ways to enter IRC from a Unix system. If you are using the emacs (editor from Richard Stallman and the Free Software Foundation) lisp client, you just have to type "M-x irc", (if this doesn't work you may need to load the client into your emacs session). If you are using the C client, (easier for beginners), then you usually type "irc". Non-Unix boxes have special clients, each of which has to be configured using a special procedure. Check the manual or help screen for more information.

If you wish to be known by a nickname which is not your login name, type "irc nickname" instead. Each IRC user, ("client"), chooses a nickname. All communication with another user is either by nickname or by the channel that they or you are on (more information about channels later on).

The most important thing to remember about IRC is that you have to be willing to explore and learn to use it. Take your time, try not to get flustered, enjoy yourself, and you will soon be making new friends all over the world!

IRC is based on a client-server model. Clients are programs that connect to a server, a server is a program that transports data, (messages), from a user client to another. There are clients running on many different systems, (Unix, emacs, VMS, MSDOS, VM...), that allow you to connect to an IRC server. The client which will be spoken of here is the most widespread: ircII, (originally designed by Michael Sandrof). Other clients are similar, and often accept ircII commands.

GENERAL IRC COMMANDS USABLE BY ANYONE

2008-03-21T07:31:00.000+07:00

GENERAL IRC COMMANDS USABLE BY ANYONE

* To ignore someone
o type /ignore Nickname
* To send someone a private message
o type /msg username message
* To list the name of people in a channel
o type /names #channel_name
Due to the number of people marked "invisible" on Dalnet, this usually doesn't work, or doesn't work very well...
* To send a notice to someone
o type /notice Nickname Message here
* To send a notice to a channel you are in
o type /notice #Channel_name Message here
* To invite someone to a channel
o type /invite Nickname #channel_name
* To change servers, particularly when lagged
o type /server servername:portnumber (Example: /server irc.dal.net:6668)
* To quit IRC
o type /quit
* To quit IRC - and send a quit message
o type /quit quitmessage (example: /quit See ya laterz!)
* To join a channel
o type /join #channelname
* To leave a channel without quitting IRC completely
o type /part #channelname
* To leave a channel - and send a parting message - without quitting IRC completely
o type /part #channelname message
* To perform an action
o type /me specified action (example /msg waves to everyone)
* To send a private mesaage to someone
o type /msg usenick message
* To get NICKSERV information on a nickname
o type /msg nickserv@services.dal.net INFO Nickname
* To get info on who someone is that's currently online
o type /whois Nickname
* To get CHANSERV information on a #channel
o type /msg chanserv@services.dal.net info #channelname

DALNET INFO LINKS

* DalNet IRC Homepage
* DalNet Acceptable Use Policy
* DalNet Help Page
* DalNet Server List Page

NICKSERV COMMANDS FOR REGISTERED NICKS
for help with NickServ functions, type /msg nickserv@services.dal.net help

* To register your nickname
o type /msg nickserv@services.dal.net REGISTER your_password your_email
* To identify to NickServ for your nick
o type /msg nickserv@services.dal.net IDENTIFY your_password
* To set the "enforce" ("Kill") option on your nick
o type /msg NickServ@services.dal.net SET KILL ON
This prevents other people from using your nick when you're not on.
* To ghost your nickname
o type /msg nickserv@services.dal.net GHOST Nickname your_password
If, for some reason, your Internet connection fails (lag, net-split, computer crash, etc), then your client may not log off IRC properly. When you reconnect, your nickname from before may show up as still being online. This is called a ghost. With this command, you can remove your ghost.
* To recover your nickname from someone else using it
o type /msg nickserv@services.dal.net RECOVER Nickname your_password
use this if you don't have your Nick KILL switch set to "on".
* To release your nickname from NickServ
o type /msg nickserv@services.dal.net RELEASE Nickname your_password
use this after you have used the recover command, to release your nickname from NickServ's Enforcer service. Otherwise, NickServ will hold your nick in custody for two minutes before releasing it on it's own.

MEMOSERV COMMANDS (AVAILBLE TO USERS WITH REGISTERED NICKS)
for help with MemoServ functions, type /msg memoserv@services.dal.net help

* To list your memos
o type /msg memoserv@services.dal.net LIST
* To read a memo
o type /msg memoserv@services.dal.net READ memo_number
ex.: /msg memoserv@services.dal.net READ 2
* To delete a memo
o type /msg memoserv@services.dal.net DEL memo_number
* To undelete a memo
o type /msg memoserv@services.dal.net UNDEL memo_number
* To purge memos
Memos cannot be unprged, they are permanently deleted when this function is used.
o type /msg memoserv@services.dal.net PURGE
* To send a memo
o type /msg memoserv@services.dal.net SEND Nickname Text of memo
ex.: /msg memoserv@services.dal.net SEND Sanguinarius Meet me in chat tonight.
* To send a memo to the SOPs
o type /msg memoserv@services.dal.net SENDSOP #channel_name Messagehere
* To send a memo to the channel aops
o type /msg memoserv@services.dal.net SEND #channel_name Messagehere

OTHER COMMANDS - USEABLE BY OPS ONLY

* To count the number of AOPs SOPs, and AKICKS a channel has
o type /msg chanserv@services.dal.net COUNT #channel_name
* To give someone temporary channel OP status
o type /mode #channel +o Nickname
* To deop someone
o type /mode #channel -o Nickname
* To give someone Voice (only useful in a moderated channel)
o type /mode #channel +v Nickname
ex.: /mode #Sanguinarius +v BloodVamp
* To remove Voice from someone
o type /mode #channel -v Nickname
* To ban someone
o type /ban Nickname
* To kick someone
o type /kick #channel_name Nickname
ex.: /kick #Sanguinarius Mr_Troll
* To kick someone (with a reason)
o type /kick #channel Nickname Reason
ex.: /kick #Sanguinarius Mr_Troll Get out and stay out!!!
* To invite someone to a channel
o type /invite Nickname #channel_name
* To send an ops notice to the OPs of a channel
you must be in the same channel with the ops you want to message
Also, if this command doesn't work, check your chat client's documentation; it may use a different command.
o type /onotice #channel_name Your notice here
ex.: /onotice #Sanguinarius Should we kick Mr_Troll now?
* To view a channels AOP, SOP, or AKICK list - AOPs and above only
o type /msg chanserv@services.dal.net [ AOP | SOP | AKICK ] #channel_name LIST
ex.: /msg chanserv@services.dal.net AOP #Bloodsuckers LIST
ex.: /msg chanserv@services.dal.net AKICK #Sanguinarius LIST
* To add someone to the AOP or AKICK list - SOPs and Founder only
o type /msg chanserv@services.dal.net [ AOP | SOP | AKICK ] #channel_name ADD [ Nick or mask ]
Hostmask example: nick!*email@port.domainname.whatever
ex. /msg chanserv@services.dal.net AOP #Sanguinarius ADD BlakFang
ex.: /msg chanserv@services.dal.net SOP #Psychic_Vampires ADD *!*darkness@*.aol.com
ex.: /msg chanserv@services.dal.net AKICK #Bloodsuckers ADD Mr_Troll!*@*
* To delete someone from the AOP or AKICK list - SOPs and Founder only
o type /msg chanserv@services.dal.net[ AOP | SOP | AKICK ] #channel_name DEL [ Nick | Mask | Entry_number ]
ex.: /msg chanserv@services.dal.net AOP #Sanguinarius DEL BlakHearse
ex.: /msg chanserv@services.dal.net AKICK #Psychic_Vampires DEL *!*johndoe@*.sprint.net
ex.: /msg chanserv@services.dal.net SOP #Bloodsuckers DEL 14

FOUNDER COMMANDS

* To add someone to the SOP list
o type /msg chanserv@services.dal.net[ AOP | SOP | AKICK ] #channel_name ADD [ Nick or mask ]
Hostmask example: nick!*email@port.domainname.whatever
ex. /msg chanserv@services.dal.net AOP #Sanguinarius ADD BlakFang
ex.: /msg chanserv@services.dal.net SOP #Psychic_Vampires ADD *!*darkness@*.aol.com
ex.: /msg chanserv@services.dal.net AKICK #Bloodsuckers ADD BlakFang!*@*
* To delete someone from the SOP list
o type /msg chanserv@services.dal.net[ AOP | SOP | AKICK ] #channel_name del [ Nick | mask |entry_number ]
Hostmask example: nick!*email@port.domainname.whatever
ex. /msg chanserv@services.dal.net AOP #Sanguinarius delBlakFang
ex.: /msg chanserv@services.dal.net SOP #Psychic_Vampires del *!*darkness@*.aol.com
ex.: /msg chanserv@services.dal.net AKICK #Bloodsuckers del 14
* To remove expired nicks from the AOP or SOP list (Founder access only)
o type /msg chanserv@services.dal.net [ AOP | SOP ] #channel_name CLEAN
ex.: /msg chanserv@services.dal.net SOP #Bloodsuckers CLEAN
* To clear the AOP, SOP, or AKICK list
o type /msg chanserv@services.dal.net [ AOP | SOP | AKICK ] #channel_name WIPE
ex.: /msg chanserv@services.dal.net AKICK #Psychic_Vampires WIPE

The SILENCE command

2008-03-21T07:23:00.000+07:00

1 · The SILENCE command

Silence is basically the same thing as /ignore, however, when /ignore halts the msg/notice/etc. from getting to the user on the client side, silence halts it before it even gets to the client. This is more efficient because you can save bandwidth (especially important if you are on a modem).

Syntax: /quote silence +/-host

Information: The +/-host has to be the full host you wish to ignore, including the ident and nickname (basically, nickname!ident@host type).

Note: Wildcards (*) are accepted.

Example: /quote silence +*!mystro@*.canshell.com

This example will silence anyone with the host *!mystro@*.canshell.com.

2 · The LIST command

The /list command allows you to list active channels on the network. Using this command you can take the thousands of channels a large IRC Network usually has and filter them down to a smaller number. It allows you to find channels by their topic, channel name, amount of people or other characteristics.

Options in the list command are seperated by commas rather than being put together; you will see examples of that later in the document. As well, channels are listed in order of newest to oldest created (the server considers a channel 'created' when a single person enters it; this is not the same as the ChanServ channel creation date).

Below are the options you can use for list:

NOTE: You must use the /quote list option if you are using a client that has /list built in (such as mIRC) because it may not accept those options.

2.1 List channels with more than a certain number of people: >Number

Syntax: /quote list >number

Information: The >number option lets the user search for channels with more users than the number specified beside the >

Example: /quote list >1

This example will return all the channels with more than one person in them, in order from newest created channel to oldest.

2.2 List channels with less than a certain number of people:

Syntax: /quote list

Information: The option lets you search for channels with less than the specified number of people in the channel.

Example: /quote list <50

This example will show all the channels with less than 50 people in them.

2.3 List channels created after a specific date: C>Number

Syntax: /quote list C>number

Information: The C>Number will list channels created between now and a Number of minutes ago.

Example: /quote list C>60,>50

This example will show all channels created in the last hour that have more than 50 people in them.

2.4 List channels created before a specific date: C

Syntax: /quote list C

Information: The C

Example: /quote list C<30,>50

This example will list all channels created earlier than 30 minutes ago that have over 50 people in them.

2.5 List channels with topics older than specified: T>Number

Syntax: /quote list T>Number

Information: The T>Number option will list channels whose topic is older than Number of minutes.

Example: /quote list T>60

This example will show all channels in which the topic was changed over 60 minutes ago.

2.6 List channels with topics younger than specified: T

Syntax: /quote list T

Information: The T

Example: /quote list T<30

This example will show all channels whose topic has been changed in the last 30 minutes.

2.7 List channels that match the mask: mask

Syntax: /quote list mask

Information: The mask option allows you to search channel names for the channel you are looking for.

Note: Wildcards (*) are accepted.

Example: /quote list *help*

This example will return channels with 'help' in their name.

2.8 List channels that do not match the mask: !mask

Syntax: /quote list !mask

Information: The !mask allows you to search channels that do not match the mask specified in the list parameter.

Note: Wildcards (*) are accepted.

Example: /quote list !*help*

This example will return channels that do not have anything to do with help in their name.

3 · DCCallow

Due to the many viruses transferred daily on DALnet, the DALnet IRC Server currently has a function that blocks extensions commonly used by trojans ("js", "pl","exe", "com", "bat", "dll", "ini", "vbs", "pif", "mrc", "scr", "doc", "xls", "lnk", "shs"). In order for you to still be able to transfer files with these extensions, the DALnet coding team has added a command called DCCallow.

Syntax: /quote dccallow +/-nickname

Information: The +/-nickname must be the nickname of the person who you wish to allow to be able to send DCC's to you.

Note: The list gets wiped whenever you disconnect and the person you have added to it will be removed whenever they change nicknames or disconnect.

Example: /quote dccallow +mystro

mystro has been added to your DCC allow list

This example will add 'mystro' to your dccallow list, so that he can send files to you even if they have extensions from the list above.

Syntax: /quote dccallow list

Information: The list option lists people which are currently allowed to send you files normally blocked by the server.

Example: /quote dccallow list>

This example will list all users that are on your DCCallow list:

The following users are on your dcc allow list:
mystro (mystro@canshell.com)
End of DCCALLOW list

The nickname is 'mystro' and the host, mystro@canshell.com is in brackets.

4 · Watch

WATCH is a command which notifies a user whenever certain people come online. Newer IRC clients (including new versions of mIRC) automatically use this function for their notify system.

Syntax: /quote watch [s|l] +/-nickname

Information: The s or l options must be set by themselves (i.e. can not be put together in one command). Other than that, the command is very simple: you add a nickname to the list by typing /quote watch +nickname and remove it by -nickname.

Note: The watch list gets wiped whenever you disconnect from IRC, so you will have to input the nicknames again once you come back.

Example: /quote watch +mystro

This example will add mystro to your watch list, and you will receive a response such as this:

mystro ~mystro canshell.com 0 is online

If the person is online.

If not you will recieve a response such as :

mystro * * 0 is offline.

If you do the /quote watch l command you will recieve a response such as:

Mystro mystro 216.6.41.104 975299499 is online
End of WATCH l

Where the 975299499 is the signon time in seconds, counted from January 1st, 1970 (if it seems confusing, just ignore it)

If you do the command /quote watch s you will recieve a response such as:

You have 1 and are on 1 WATCH entries
mystro
End of WATCH s

Although not worded very clearly, all this means is that you have one person on your watch list and you are on one person's watch list.

5 · The WHO command

/quote who can be used to check if somebody is online. It does not work if that person has their user mode set to +i (invisible), unless you are in the same channel as that person.

/quote who, as many other IRC commands has a set of arguments that should be applied when you use it.

In the example below you will see all the arguments and options the /who command can have as well as the actual syntax of the command: /quote who +/-achmnsu args

The letters after + or - are called options (commonly referred to as parameters). I will discuss these in a moment. Some options need additional arguments which are specified after all the options.

In the who reply, the number following the collon is the number of hops you are from that user. Hops being the servers away. If you are on the same server as the user you will get :0, if you are on a server which is linked to another set of servers (i.e. twisted > typhoon > jade) the amount of hops will vary, on the previous example of the twisted > typhoon > jade linkage, it is visible that there are two hops, twisted > typhoon and typhoon > jade.

Just as a note, more than one option can be specified in /quote who, but the arguments must follow in the same order as the option letters (/quote who +hc *.canshell.com #dalnethelp will work,/quote who +hc #dalnethelp *.canshell.com won't).

When you perform a /quote who on a channel or person you will see a capitalized letter (and a symbol if the user is an IRC Operator or an operator/voice in the channel) to the right of their name and before the host.

These symbols are:

H = here, hence not set /away

G = gone, is /away

* = User is an IRC Operator

+ = User is a voice on this channel (the channel will be the very first part of the who)

@ = User is an operator in this channel

And finally, for the mIRC users, I would suggest using /quote who to directly contact the server because /who is a built in mIRC command and it doesn't work exactly like DALnet's /quote who works. As well, the replies may vary between client to client. For the purpose of this document the mIRC IRC client was used.

5.1 List by host: +/-h

Syntax: /quote who +/-h host

Information: The +h option specifies that you only want to see users from a specific host. If you use the -h option, all results will be shown *except* from that specific host. Or more simply, if you are in a very large channel or just doing a /quote who with no channel specified, this will only show the people who have or don't have the host that you specify.

Note: Wildcards (*) are accepted, so if you do not know the actual full hostname feel free to just enter part of the hostname with * surrounding it and it will return the matches it finds and you can narrow it down further more if needed.

Example: /quote +h mystro.canshell.com

This example will return something like:

* Mystro H mystro@mystro.canshell.com :0 Mystro
mystro.canshell.com End of /WHO list.

Another example, using wildcards: /quote who +h *.canshell.com

* Mystro H mystro@mystro.canshell.com :0 Mystro
*.canshell.com End of /WHO list.

Of course you can do a /quote who +h *.com but that would return over 200 replies and ask you to narrow down your search. Even if it worked, this would not be very useful as most people have *.com addresses.

If you did /quote who -h it would just return everyone who didn't match *.canshell.com.

5.2 List by channel: +c

Syntax: /quote who +c #channel

Information: +c narrows down the who list to only people in a specific channel. This will allow you to scan individual channels for people rather than everyone on the network.

Note: You can not do /quote who -c #channel and can not use wildcards (*) for the channel's name.

Example: /quote who +c #DALnetHelp

This example would show everyone in the channel along with their corresponding status (@,+,*). However, as most users are now automatically set +i when they connect to DALnet, the server will not show you them unless you are in the same channel. So you might need to join the channel before typing /quote who +c #DALnetHelp.

5.3 Is the user away: +/-a

Syntax: /quote who +/-a

Information: The +/-a option allows you to eliminate people who are/aren't (depending on the + or the - sign) away. This can be potentially useful if you are a channel operator and wish to see who in your channel is actually there or is just idling.

Note: If you do not wish to use the +/-a command you can just check the G or H sign near the nickname and see if the person is away or not.

Example: /quote who +ac #mystro

#Mystro Mystro H@ mystro@mystro.canshell.com :0 Mystro
#Mystro End of /WHO list.

This is everyone in #mystro who are not /away, however /quote who -a+c #mystro will show:

#Mystro IsraHelp G@ mystro@209.25.158.132 :6 #IsraHelp's bot
#Mystro nekoo G neko@sc-24-130-144-74.socal.rr.com :2 Don Hoover
Mystro End of /WHO list.

nekoo and IsraHelp are the two users who are away at the moment.

5.4 List by usermodes: +/-m

Syntax: /quote who +/-m o|a|A

Information: The +/-m mode allows one to check whether there are/aren't IRC Operators in a specific place. The command takes one argument, either o for IRCop, A for Admin or a for Services Admin.

Example: /quote who +mc o #operhelp

#operhelp End of /WHO list.

This example shows that there were currently no IRCops in #OperHelp

Another example: /quote who -m+c o #operhelp

#operhelp Mystro H mystro@mystro.canshell.com :0 Mystro

There was one person in operhelp who was not an IRCop

5.5 List by nickname: +/-n

Syntax: /quote who +/-n nickname

Information: This option allows one to see all people in a specific place who have the nickname or part of the nickname they are looking for.

Note: You may add wildcards (*) in this mode.

Example: /quote who +cn #mystro Mystro

#mystro Mystro H@ mystro@mystro.canshell.com :0 Mystro
#mystro End of /WHO list.

Another example, this one with wildcards: /quote who +cn #mystro *myst*

#mystro Mystro H@ mystro@mystro.canshell.com :0 Mystro
#mystro End of /WHO list.

And lastly, one with -n: /quote who +c-n #mystro *myst*

#Mystro nekoo G neko@sc-24-130-144-74.socal.rr.com :3 Don Hoover
#Mystro B0T H@ bop@208.46.238.67 :6 http://mirc-egg.net
#Mystro End of /WHO list.

5.6 List by server: +s

Syntax: /quote who +s server

Information: This command allows the user to check who is on a specific server.

Note: You may not use wildcards (*) in this command and therefor must use the full name of the server (i.e. not liberty.* but liberty.nj.us.dal.net). As well you cannot check who isn't on that server.

Example: /quote who +cs #mystro liberty.nj.us.dal.net

#Mystro Mystro H mystro@mystro.canshell.com :0 http://windowsirc.hypermart.net
#Mystro End of /WHO list.

5.7 List by username +u/-u

Syntax: /quote who +/-u username

Information: This option allows the user to see who has or does not have a specific username (or part of a specific username).

Note: Username is considered IDENT by most clients, or in other words, the part before the @ sign in the users address. Wildcards (*) are accepted.

Example: /quote who +cu #mystro mystro

#Mystro Mystro H mystro@mystro.canshell.com :0 http://windowsirc.hypermart.net
#Mystro End of /WHO list.

Another example showing everyone who do not have the word mystro in their username: /quote who +c-u #mystro mystro

#Mystro B0T H@ bop@208.46.238.67 :6 http://mirc-egg.net
#Mystro nekoo G neko@sc-24-130-144-74.socal.rr.com :3 Don Hoover
#Mystro End of /WHO list.

And finally, an example of a wildcard that will show all the users who have 'o' in their username: /quote who +cu #mystro *o*

#Mystro B0T H@ bop@208.46.238.67 :6 http://mirc-egg.net
#Mystro Mystro H mystro@mystro.canshell.com :0 Mystro
#Mystro nekoo G neko@sc-24-130-144-74.socal.rr.com :3 Don Hoover
#Mystro End of /WHO list.

5.8 Show first visible channel user is in: +C

Syntax: /quote who +C nickname

Information: This command lets you see the first visible channel in a /who.

Example:/quote who +C mystro

#mystro Mystro H mystro@mystro.canshell.com :0 Mystro
Mystro End of /WHO list.

5.9 Check for user in channels I am member of: +M

Syntax: /quote who +Ms|u|h

Information: This command checks for the users in the channels the person is part of, it accepts the extra options s, u or h (server, username or hostname).

Example:/quote who +Mh *.canshell.com

#mystro |Mystro| H@ mystro@mystro.canshell.com :0 Mystro
#ravenscar |Mystro| H@ mystro@mystro.canshell.com :0 Mystro
*.canshell.com End of /WHO list.

This example shows the +Mh feature and shows how the server showed all the channels |Mystro| and I were in.

5.10 Example of combining searches

As some of the previous examples demonstrate, it is possible to combine searches to match more than one search criteria. We will provide one further example to illustrate this.

Syntax: /quote who +ch

Information: This command checks for users in a specified channel who match the specified host.

Example:/quote who +ch #mystro *.canshell.com

#mystro |Mystro| H@ mystro@mystro.canshell.com :0 Mystro
End of /WHO list.

This type of search would be particularily useful when trying to track down a relay bot inside a channel that is transmitting the nicknames of everyone in the channel to a mass advertising bot outside the channel.

6 · Conclusion

If you are interested in finding out more or have any questions you may check on IRC the channel #bahamut, or on the web http://www.bahamut.net. As well, if you are interested in looking up these commands by yourselves, please use /quote who ? for WHO help, /quote list ? for LIST help, /dccallow help for DCCallow help. WATCH and SILENCE do not have help in the IRC server itself.

7 · Credits

While writing this document many people have been bugged and harassed. I think that the least I can do for their help is give them some recognition. Thanks goes to Darkrot for the /list information, Hammer for some clarification, LadyDana for all the motivation (and for being such a wonderful leader :) and many people who I just harassed while writing this document. Oh and, yes, some credit goes to Mystro, the lifeless student who wrote this document.
The
DALnet
IRC
Network!

IRC:

/server irc.dal.net 7000 (also port 6667)
Web:

http://www.dal.net/
Help:

http://help.dal.net/
FTP:

ftp://ftp.dal.net/
Email:

help@dal.net (help), docs@dal.net (help documents), suggest@dal.net (suggestions and comments)