An IRC network is a bunch of hubs, leafs and servers connected to each other in a star topology.
Even if IRC is dead simple you might run into problems, that’s why we got this help page.
Here you’ll find the most basic questions and answers but if you run in to a bigger problem or feel that something is missing
please send us an email and let us know.
#Help – Our help channel
If you just want to use your browser you can install Chatzilla in your firefox browser
Do I need a client?
Not really, you are free to use our webchat!
|Server Admin (Set in Oper Block)
|Services Admin (Set in Oper Block)
|Marks you as being a Bot
|Co-Admin (Set in Oper Block)
|Makes it so you can not receive channel PRIVMSGs
|Filters out all the bad words per configuration
|Can send & read globops and locops
|Hide IRCop Status
|Available for help (HelpOp)
|Hide an oper’s idle time (in /whois output) from regular users.
|Invisible (not shown in /who)
|Network Administrator (Set in Oper Block)
|Local IRC Operator (Set in Oper Block)
|Global IRC Operator (Set in Oper Block)
|Hides the channels you are in from /whois
|Only U:Lines can kick you (Services Admins Only)
|Allows you to only receive PRIVMSGs/NOTICEs from registered (+r) users
|Identifies the nick as being registered
|Used to protect Services Daemons
|Can listen to server notices
|Prevents you from receiving CTCPs
|Says you are using a /vhost
|Marks you as a WebTV user
|Receives infected DCC Send Rejection notices
|Lets you see when people do a /whois on you (IRCops Only)
|Can listen to wallop messages
|Gives user a hidden hostname
|Indicates that you are an SSL client
|Only Administrators may join
|Makes the user a channel admin
|Bans the given user from the channel
|No ANSI color can be sent to the channel
|No CTCP’s allowed in the channel
|Exception ban – If someone matches this, they can join a channel even if they match an existing ban
|Channel flood protection. See section 3.12above for an extended description.
|Makes channel G rated. Checks for words listed in the Badword Blocks, and replaces them with the words specified
|Gives half-op status to the user
|Invite exceptions (“invex”) – if someone matches this, they can bypass+i requirements to enter the channel.
|Throttles joins per-user to joins per seconds seconds
|/knock is not allowed
|Sets a key needed to join
|Sets max number of users
|If the amount set by +l has been reached, users will be sent to this channel
|A registered nickname (+r) is required to talk
|Moderated channel. Only +v/o/h users may speak
|No nick name changes permitted
|No messages from outside channels
|Only IRCops may join
|Gives a user channel operator status
|Makes channel private
|Sets channel owner
|Only U:Lined servers can kick users
|This channel is registered (only settable by services)
|Requires a registered nickname to join
|Strips all incoming colors
|Makes channel secret
|Only halfops, chanops, or better can set topic
|No NOTICE’s allowed in the channel
|Auditorium – Makes /names and /who #channel only show channel ops
|/invite is not allowed
|Gives a voice to users. (May speak in +m channels)
|Only clients on a Secure (SSL) Connection may join
|Set by the server to indicate all users on the channel are on a Secure (SSL)Connection. Only active is +z is also set. ULines (eg: BotServ) areignored when counting ‘insecure users’. It’s still up to the serveradmins to make safe server to server links (which could be with the helpof SSL, but also VPN, loopback interface, quantum encryption, etc etc),the IRCd does not and cannot detect this.
ChanServ – Handles channel registration.
/msg NickServ register <password> <email>
Where you remove < and > and insert your own password and your email.
You’ll then get an email with futher instructions.
/msg ChanServ register <channel> <password> <description>
Where you remove < and > and insert your channel, your password and a description about the channel.
For example: /msg ChanServ help