Beirut Chat - Beirut Internet Relay Chat Network @
 Beirut IRC Network Oper Policy

Main page
Online Shop
Web Chat
Beirut City
Discover Lebanon
Make a donation


  IRC Operators  

Opers will not use their IRCop privileges when dealing with non policy violations in their own private channels. All kill msgs must clearly state a valid reason for the kill so it's apparent to all why the person was removed from the net. This includes kills of other opers which should clearly state that it is a vanity kill or a congratulations kill. Opers will NOT kill another oper on the request of a user. No vanity kills of users. There must be a valid reason (ie: flooding, spaming, etc...) to kill a user. The net reserves the right to remove any O line/s for an oper with a majority vote by server admins, founders, and global opers.

  • 1.IRC Operator Privileges
  • 2.IRC Operator Responsibilities
  • 3.Beirut Standards for a Server
  • 4.The Beirut Network's Operator Chain Of Command
  • 5.KILL And GlINE
  • 7.OperServ (OS)
  • 8.IRC Operator Broadcast Messages (Wallops)
  • 9.The Beirut IRC Network's Teams
  • 10.Network Related
  • 11.Ammendments

  • -------------------------------

    1.IRC Operator Privileges:

    Being an IRC Operator is a privilege and not a right.

    Do not take IRC Operator Privileges lightly. Abuse of them will get an IRC Operator's O:line suspended, demoted or removed permanently.

    2.IRC Operator Responsibilities :

    Network Administrator (OS access: 1000)

    - Maintain order and control over the network and its IRC Operators. - Create, modify or remove rules which are intended to maintain a properly running IRC network. - Schedule monthly IRC Operator meetings. - Be available at any reasonable time in order to acess issues and concerns from anyone. - Enforce rules upon other IRC Operators and their Server Administrators. - Also responsible for Server Administrator and IRC Operator's responsibilities.

    Server Administrator (OS access: 600)

    - Maintain a server with current Beirut standards. - Maintain a stable server uptime and link time. - Watch over the server's IRC Operators and enforce rules outlined in this document. - Also responsible for IRC Operator responsibilites.

    IRC Operator (OS access: 100 - 400)

    - Spend at least 10 hours a week visiably on IRC. - Protect the network, and its resources against anyone wishing to do harm. - Maintain a routed network. - Join #Beirut #Help #Service and assist the network. - Help all users requesting help in any channel. - Attend IRCop Meetings and provide ideas and suggestions. - Follow all rules of Beirut.

    3.Beirut Standards for a Server :


    - Must be on GNU/Linux or FreeBSD machine. - Must be online 60 minutes in a hour, 24 hours in a day, 7 days in a week. - Upgrade the IRCD within 7 days of a security fix. - Manually update ircd.conf options within 2 days of a request. - Run a time sync program at least once a day. - Upgrade third party software when security issues are known.


    - Run a firewall and block all unused ports and secure open ports

    Failure to follow the REQUIRED standards will result in a server being JUPED or delinked.

    4. The Beirut Network's Operator Chain Of Command :

    To maximize efficiency on Beirut, the Chain Of Command should be followed when dealing with problems that may arise. This Chain of Command refers to the IRC Operators on a Server and then to a Network Administrator.

    This includes not only problems with users on the Network, but also problems with other IRC Operators.

    The Chain Of Command is as follows:

    Local IRCop -> Global IRCop -> Server Admin -> Network Admin

    Emergencies such as someone attempting to hack one of Beirut's servers or services should be immediately reported to a Network Administrator.

    5.KILL and GLINE:

    KILL and GLINE are IRC Operator commands that allow an IRC Operator deal with users who are causing trouble. They are to be used as a last resort when normal user commands and common sense procedures are not working.

    Each IRC Operator is to use their best judgement on when a KILL or GLINE is necessary. If there are any questions on whether it is appropriate, they should be directed to the Server Administrator or a Network Administrator.

    The use of KILL

    All IRC Operators have access to KILL. Local IRCops can only KILL on their local server. Global IRCops, Server and Network Administrators can KILL globally on any server.

    Before an IRC Operator uses KILL to disconnect a user make sure it is absolutely necessary and there is no other way to solve the problem. Just because an IRC Operator can use KILL doesn't mean they have to. The use of IGNORE or BAN is very useful and usually can solve the problem.

    All KILLs should have a clear reason so others will understand why a user was disconnected.

    Examples of when NOT to use KILL:

    1. If a user is harassing and indvidual. (Use /ignore)
    2. If a user is harassing a channel (Use /ban)

    Examples of when to use KILL:

    1. Breaking the rules of Beirut IRC Network or the rules of a Local Server.
    2. When BAN or IGNORE is NOT working and after warning the user of their inappropriate behavior.
    3. If a user is harassing many channels or users.

    The use of GLINE

    Global IRC Operators, Server and Network Administrators may use GLINE to solve any problems that KILL has not been able to stop.

    Before an IRC Operator uses GLINE to BAN a user from Beirut IRC Network, attempt a KILL first to make them think twice about what they are doing. If the user repeatedly continues to abuse the rules, a GLINE may be appropriate.

    The maximum time of a GLINE must be: 1 week. (and 4 weeks for proxy bots - drones)

    All GLINEs should have a clear reason in English so other IRC Operators will understand why a user was banned.

    Examples of when NOT to use GLINE:

    1. Seeing multiple logon and logoff notices from someone.
    2. User should be banned from a single channel.

    Examples of when to use GLINE:

    1. KILL does not seem to persuade a user to stop.
    2. Any attempts on hacking the network is an automatic GLINE. Also notify a Network Administrator ASAP.

    6.CONNECT and SQUIT:

    CONNECT is used to connect one IRC Server to another. SQUIT is used to disconnect an IRC Server from another.

    The Use of CONNECT

    All IRC Operators have access to CONNECT. Local IRC Operators can only CONNECT their local IRC Server to another. Global IRC Operators, Server and Network Administrators can connect remote servers as well as their local server. In order for a CONNECT to be successful, both servers must be configured properly with C:line according to Beirut standards and must have been approved by the Beirut Routing Committee.

    It is the responsibility of all IRC Operators to be aware of when a server is disconnected. Disconnected servers are to be reconnected by its IRC Operators within 15 minutes or an attempt to CONNECT it remotely should be executed if the reason of the disconnect was unplanned.

    If after several attempts, over a reasonable period of time, a server cannot be relinked, then the server should be considered "dead" and further attempts will not be required.

    Servers are only to CONNECT to other servers according to the routing map.

    The Use of SQUIT

    All IRC Operators have access to SQUIT. Local IRC Operators can only SQUIT their local IRC Server from another. Global IRC Operators, Server and Network Administrators can SQUIT remote servers as well as their local server.

    The use of SQUIT should rarely be used since a disconnected server serves no purpose off Beirut IRC Network.

    A SQUIT is most commonly used to reroute a server to another server on the Network to help prevent network lag or prepare for a planned network split.

    Before a server is SQUITed, the IRC Operator of that server should notify the other IRC Operators, preferably a Network Administrator, for the reason of the SQUIT and also perform a Wallop explaining the reason. This helps prevent another IRC Operator from attempting a reconnect and lets everyone know why the server left.

    7.OperServ (OS) :

    An IRC Operator will NOT need to use OS without reason. NS and CS give all the access to the users to handle Oping themselves in their own channel, unbanning themselves or for getting their channel back after someone maliciously takes it over.

    8.IRC Operator Broadcast Messages (Wallops) :

    There are times when IRC Operators may be required to provide warning, notice or discussion over some Server or Network related issues.

    These messages are not ment to be used for general chat, except for Wallops.


    Wallops provide a way of broadcasting messages ONLY to the IRC Operators ONLY the IRC Operators receive these messages. The wallops are reserved only for ircops on Beirut IRC Network. Normally this depends of the server ircd.conf ( if the server allows wallops for normal users, anyone who has UMODE +w can view them as well. )

    These messages are generally used for notices if a server is going to be SQUITed, CONNECTed or any other basic Network Related issues or problems.

    9.The Beirut IRC Network's Teams :

    There are several different teams that run the Beirut IRC Network. These teams provide the network with the latest technology, security, configuration, help the users, etc.

    Channel Service

    #Help Team

    Routing Committee

    Responsible for network configuration, server links and services.

    10.Network Related :

    There are many security and privacy issues to contend with. Most of which should be brought to the attention of the Routing Committee when the time arises.

    Abusive IRCops

    Abuse of an IRC Operator's O:line will not be taken lightly and will result in suspension, demotion or removal of the IRC Operator's O:line if their actions are determined inappropriate by the Routing Committee.

    Abuse of server realated issues may result in the server being JUPEd and its C:line being removed from all HUB servers.

    Abuse is considered violating this document, the Beirut Policy and/or performing actions found inappropriate by the Routing Committee.

    O: line

    All O:lines on all servers are to be approved by the Routing Committee before they are added or removed. This is necessary in order to prevent excessive IRC Operators on the network.

    Each Server may have the following number of O/o:lines after they are approved:

    - One Server Administrator - One Server Co-Administrator (Global IRC Operator) - One Local IRC Operators

    O:lines may be removed/added/modified with the approval of the Routing Committee. We dont allow oper changes, so if you want oper change you must have good reason.

    New IRC Operators

    The user must have had their nick registered with NS for at least 30 days and have been actively participating in network related issues.

    New IRC Operators must attend at least one scheduled IRCop Training Meeting and pass a test showing they know enough to become an IRCop.

    Before a new IRC Operator is allowed an O:line, they must also be approved by all Network Administrators and Routing Committee.

    New IRC Servers

    - The server admin must meet all criteria in routing.php . - If approved, the server will be on a 7 days test link period where it's server admin and ircops are monitored. - At the end of 7 days, a vote is held by all Network Administrators and the Routing Committee.

    Network Routing

    All Network related configuration lines are to be submitted to the Routing Committee at routing at to be approved before they are to be added to the server.

    Net Splits

    Any available IRC Operator must attempt to reconnect the missing server or service immediately. See section 6. --- The Use of CONNECT .

    When a server cannot be relinked or rerouted and attempts have been made for no less than 1 hour, an email must be sent to routing at with the following:

    (1) Which server(s) or service(s) are down. (2) Names of each IRC Operator who participated in attempting to reconnect the server(s) or service(s). (3) Procedures that were attempted to relink.

    Server Software

    The Beirut IRC Network uses the Universal IRCd - IRCU u2.10.11.07


    The use of any program, such as a port sniffer, to intercept communication between servers or between users is prohibited.

    11.Ammendments :

    The Routing Committee and all Network Administrators, reserves the right to change anything contained in this document at any time without prior warning.

    By Stefano & Mitko

    Enjoy Beirut.

    Home|| Partners || Privacy Policy || Terms of Use || Contact us || Link to us
    © XTI Communications. All Rights Reserved.