DWIRC:Staff Training/Network Introduction

DarkWorld IRC Staff Training
Module 1: DarkWorld IRC Network Introduction

Program	DarkWorld IRC Staff Training Program
Module	1 of 10
Difficulty	Beginner
Estimated study time	60–90 minutes
Assessment	Knowledge check and written assignment
Prerequisite	Acceptance into the training program

Module Overview

This module introduces candidates to the DarkWorld IRC Network, its position within the wider DarkWorld Network, its purpose, community structure, official resources, and staff responsibilities.

Before learning moderation commands or receiving access, every candidate must understand:

• What DarkWorld Network is.
• What the DarkWorld IRC Network is.
• How DWIRC relates to other DarkWorld projects.
• What IRC staff members are expected to do.
• The limits of IRC staff authority.
• How staff decisions should be escalated.
• Why trust, restraint, and accountability are essential.

This module does not provide IRC operator access or authorize a candidate to represent themselves as a DarkWorld staff member.

Learning Objectives

After completing this module, the candidate should be able to:

1. Explain the difference between DarkWorld Network and DarkWorld IRC.
2. Describe the purpose of the DarkWorld IRC Network.
3. Identify the main responsibilities of IRC staff.
4. Explain the difference between IRC staff and project staff.
5. Identify the limits of a trainee's authority.
6. Recognize when a matter should be escalated.
7. Identify official sources of DarkWorld IRC information.
8. Explain why staff access must follow the principle of least privilege.

1. DarkWorld Network

DarkWorld Network is the wider organization and community umbrella under which multiple projects and services operate.

These projects may include:

• DarkWorld IRC Network
• DWShells
• DWBouncers
• DWBots
• DWGames
• DWStats
• DWPaste
• DWVPN
• DWTutorials
• Other current or future DarkWorld projects

Each project may have its own:

• Purpose
• Management
• Staff team
• Rules and policies
• Support procedures
• Technical systems
• Access requirements
• Training program

A person may hold a role in one DarkWorld project without holding authority in another.

For example, a DarkWorld IRC operator does not automatically have authority to:

• Create or suspend DWShells accounts.
• Administer DWBouncers users.
• Access a project server.
• Change a website.
• Modify a project database.
• Represent another project’s management.
• Override another project’s policies.

Similarly, staff members from other DarkWorld projects do not automatically receive IRC operator authority.

Important: DarkWorld Network is the umbrella. DarkWorld IRC Network is one project operating under that umbrella.

2. DarkWorld IRC Network

The DarkWorld IRC Network, also called DWIRC, provides an Internet Relay Chat environment where users can communicate in public channels, private messages, project channels, support channels, and community spaces.

The IRC network is responsible for:

• Maintaining stable IRC connectivity.
• Providing secure TLS connections.
• Operating IRC servers and Services.
• Protecting users and channels from serious abuse.
• Maintaining network-wide rules and policies.
• Supporting registered nicknames and channels.
• Providing official help and support.
• Managing approved relays and bridges.
• Supporting registered projects and communities.
• Maintaining a safe and welcoming environment.
• Responding to technical and security incidents.

The IRC network should be managed fairly and consistently. Staff authority exists to serve and protect the network, not to give individual staff members personal power over users.

3. Purpose of IRC Staff

The purpose of DarkWorld IRC staff is to:

• Assist users.
• Protect the network.
• Apply network policies fairly.
• Resolve or escalate incidents.
• Maintain IRC services and infrastructure where authorized.
• Support channels and registered projects.
• Document important actions.
• Communicate professionally.
• Protect confidential information.
• Work together as a team.

Staff members should not interfere unnecessarily with normal conversations or channel management.

Channel founders and their appointed channel operators are generally responsible for managing their own channels, provided they follow network policies.

Network staff should normally become involved when:

• A network-wide policy is violated.
• Serious abuse affects users or multiple channels.
• A user requests official assistance.
• A channel problem cannot be resolved by its management.
• An IRC server or Services problem occurs.
• A security incident affects the network.
• Staff intervention is required to prevent immediate harm.
• An authorized senior staff member assigns a task.

4. Community Moderation and Network Enforcement

Candidates must understand the difference between channel-level moderation and network-level enforcement.

Channel-Level Moderation

Channel founders and channel operators may manage their channels by:

• Setting channel rules.
• Assigning channel access.
• Giving voice or operator status.
• Removing disruptive users.
• Setting appropriate channel bans.
• Managing topics and channel settings.

A disagreement with a channel operator does not automatically become a network-level issue.

Network-Level Enforcement

DarkWorld IRC staff may become involved when conduct:

• Violates a network-wide policy.
• Involves serious harassment or threats.
• Involves network-wide spam or advertising.
• Includes repeated ban evasion across channels.
• Targets network infrastructure.
• Involves malicious bots, attacks, or exploitation.
• Involves staff impersonation.
• Endangers users or the network.
• Requires Services or IRC operator intervention.

Staff should avoid overriding legitimate channel-management decisions unless a network policy, serious abuse issue, or authorized appeal requires intervention.

5. Staff Roles and Responsibilities

DarkWorld IRC may maintain different staff levels according to operational needs.

Exact titles and permissions may change, but the general structure can include the following roles.

Role	General responsibility	Typical authority
IRC Trainee	Learns procedures and assists under supervision.	No independent network-level enforcement.
Support Staff	Helps users with connections, accounts, Services, and general questions.	Support-related access only.
IRC Operator	Responds to network abuse and operational incidents.	Limited network-level commands appropriate to the role.
Global IRC Operator	Handles incidents affecting multiple servers or the wider network.	Broader network authority as approved.
Services Staff	Assists with nickname, channel, and Services matters.	Selected Services permissions.
Services Administrator	Manages advanced Anope Services operations.	High-level Services permissions.
Network Administrator	Manages network operations, servers, policy, and senior escalations.	Administrative network authority.
Root Administrator	Maintains critical infrastructure and high-level technical systems.	Production access assigned according to responsibilities.
Founder/Network Management	Provides overall direction and final authorization.	Final management responsibility.

Titles alone must not be used to assume access. Actual permissions depend on the staff member’s assigned duties and management approval.

6. Reporting and Escalation

Trainees should follow the established reporting structure.

A normal escalation path is:

1. Attempt to understand the issue.
2. Collect only the information needed.
3. Check the relevant policy or procedure.
4. Resolve the issue if it is within your authority.
5. Contact a mentor or senior staff member if uncertain.
6. Escalate serious incidents immediately.
7. Record the action where required.
8. Follow up if the case remains unresolved.

Escalate Immediately When

A trainee should immediately contact authorized senior staff when:

• The network appears to be under attack.
• A staff account may be compromised.
• A server or Services system is failing.
• A user makes a credible threat.
• Private or sensitive information has been exposed.
• A serious security vulnerability is discovered.
• A large number of users or channels are affected.
• An action could disconnect or ban many users.
• A senior staff member is accused of serious misconduct.
• The correct response is unclear and could cause significant harm.

Trainees must not attempt high-risk actions merely to demonstrate confidence.

Good staff judgment includes knowing when not to act alone.

7. Limits of Staff Authority

Staff authority must have a clear operational purpose.

A DarkWorld IRC staff member must not:

• Use staff access to win a personal argument.
• Threaten users with staff powers.
• Investigate users out of curiosity.
• Reveal IP addresses or confidential account details.
• Access private information without an authorized purpose.
• Interfere in channels without a valid reason.
• use network commands as entertainment.
• Grant unauthorized access to friends.
• Give another person access to a staff account.
• Circumvent approval or review procedures.
• Act outside their assigned project or role.
• Present a personal opinion as official DarkWorld policy.
• punish someone merely for criticizing a staff decision.
• Hide or falsify enforcement actions.
• Retaliate against a user who submits a complaint.

Staff members remain accountable for every use of elevated access.

8. Least Privilege

The principle of least privilege means that a person should receive only the access required to perform their assigned duties.

Examples include:

• A trainee does not require IRC operator access.
• A support team member may not require server access.
• An IRC operator may not require Services database access.
• A Services staff member may not require IRCd configuration access.
• An IRC administrator does not automatically require access to DWShells.
• A project staff member does not automatically require DWIRC staff access.

Least privilege:

• Reduces accidental damage.
• Limits the effect of compromised accounts.
• Protects private information.
• Clarifies staff responsibilities.
• Makes actions easier to review.
• Protects both the network and the staff member.

9. Official Information Sources

Staff should rely on official DarkWorld sources instead of rumors or outdated instructions.

Official resources may include:

• DarkWorld IRC documentation portal
• DarkWorld Wiki
• Approved policy pages
• Official network notices
• Authorized staff channels
• PolicyServ
• RelayServ
• Staff procedures and internal documentation
• Instructions from authorized management

Useful public resources include:

• DarkWorld Network
• DarkWorld IRC Documentation
• DarkWorld Wiki

When two sources conflict, the candidate should:

1. Avoid making assumptions.
2. Check which source is current.
3. Ask an authorized senior staff member.
4. Report outdated documentation.
5. Follow the confirmed current policy.

Bots may assist staff by retrieving information, but a bot response does not replace judgment or management authorization.

10. Official IRC Channels

DarkWorld IRC may maintain official channels for different purposes.

Channel	General purpose
#DarkWorld	Main network and community channel.
#Help	IRC assistance and user support.
#Support	Support for relevant DarkWorld services and projects.
#Abuse	Reporting or discussing network abuse through approved procedures.
#PolicyTeam	Restricted policy, approval, and compliance operations.
#RelayTeam	Restricted relay and bridge compliance operations.

Additional staff and project channels may exist. Access to a channel does not by itself authorize a trainee to make administrative decisions.

Private evidence, account information, IP addresses, access credentials, or sensitive reports must not be posted in public channels.

11. Relationship With Other DarkWorld Projects

DWIRC provides communication infrastructure that may be used by other DarkWorld projects. Project channels may operate on the IRC network, but their internal management remains separate unless formally assigned otherwise.

For example:

• DWShells may use an IRC channel for user support.
• DWBouncers may use IRC bots for account management.
• DWGames may operate community or gaming channels.
• Registered external projects may maintain a verified presence.
• Relays may connect approved external communities to a DWIRC channel.

IRC staff may enforce network-wide IRC policies in these channels, but should not take over project-management responsibilities.

If an issue concerns both IRC policy and a project’s internal rules:

1. Protect the IRC network if immediate action is required.
2. Notify the relevant project staff.
3. Separate the IRC violation from the project issue.
4. Record any network-level action.
5. Escalate disagreements between teams to appropriate management.

12. Candidate Conduct During Training

While enrolled, candidates must:

• Follow all DarkWorld IRC rules.
• Treat trainers, users, and other candidates respectfully.
• Complete their own work.
• Ask questions when uncertain.
• Keep training information confidential where required.
• Avoid claiming to be permanent staff.
• Avoid using training as authority over other users.
• Report mistakes honestly.
• Accept correction professionally.
• Follow instructions during practical exercises.

A candidate’s behavior during training is part of the assessment.

Knowledge alone is not sufficient. A candidate must also demonstrate trustworthiness, restraint, reliability, and sound judgment.

13. Practical Scenarios

Review each scenario and decide the correct response.

Scenario 1: Project Boundary

You are a probationary DWIRC support staff member. A user asks you to increase their DWShells disk quota.

Correct approach:

Explain that DWShells is a separate project and direct or escalate the request to authorized DWShells staff. Do not attempt to modify the account unless you separately hold an authorized DWShells role.

Scenario 2: Channel Disagreement

A user says a channel operator kicked them for being off-topic and demands that network staff remove the operator.

Correct approach:

Ask for the relevant facts and determine whether a network policy was violated. A normal channel-moderation disagreement usually remains with the channel’s management. Do not override channel staff merely because a user is unhappy.

Scenario 3: Private Evidence

A user posts IP addresses and private logs publicly in an abuse channel.

Correct approach:

Ask the user to stop posting sensitive material publicly. Preserve only what is necessary and direct the report through the approved private process. Escalate if personal information has been widely exposed.

Scenario 4: Possible Network Attack

Several servers begin disconnecting while many automated connections join the network.

Correct approach:

Notify senior operational staff immediately, preserve relevant timestamps and observations, and follow the incident procedure. A trainee must not issue broad bans or change server configurations without authorization.

Scenario 5: Friend Requests Access

A friend asks you to give them temporary access to a restricted staff channel.

Correct approach:

Refuse the request. Access must be approved through the authorized process and must never be granted based on friendship.

Scenario 6: Uncertain Policy

You believe a message may violate the advertising policy, but the case is unclear.

Correct approach:

Preserve the relevant context, consult the official policy, and ask an authorized policy or senior staff member. Avoid issuing a serious sanction based only on uncertainty.

14. Knowledge Check

Answer the following questions in your own words.

1. What is the difference between DarkWorld Network and DarkWorld IRC Network?
2. Does completing DWIRC staff training grant authority over DWShells or DWBouncers?
3. What is the primary purpose of IRC staff authority?
4. When should network staff intervene in a channel matter?
5. What is the principle of least privilege?
6. Give three examples of matters that must be escalated immediately.
7. Why must private evidence not be posted publicly?
8. What should you do when two official sources appear to conflict?
9. Can a trainee independently issue major network-level sanctions?
10. Why is good judgment as important as technical knowledge?
11. What should a staff member do after making a mistake?
12. What is the difference between channel moderation and network enforcement?

15. Written Assignment

Write a response of approximately 300–500 words covering the following:

1. Explain the role of DarkWorld IRC within the wider DarkWorld Network.
2. Describe why you want to serve as a DarkWorld IRC staff member.
3. Explain how you would support and protect IRC users.
4. Describe what you would do if you were unsure whether enforcement was necessary.
5. Explain why IRC staff authority must not extend automatically to other DarkWorld projects.

The assignment should be submitted through the approved training process.

Do not post personal information, passwords, IP addresses, confidential reports, or private staff information in the assignment.

16. Module Completion Requirements

To complete this module, the candidate must:

• Read the complete lesson.
• Correctly answer at least 9 of the 12 knowledge-check questions.
• Complete the written assignment.
• Demonstrate an understanding of project boundaries.
• Accept that training does not guarantee a staff appointment.
• Receive approval from the assigned trainer or mentor.

A candidate who does not pass may review the material and attempt the module again.

17. Trainer Evaluation

Evaluation area	Maximum points
Understanding of DarkWorld and DWIRC structure	20
Understanding of staff responsibilities	20
Understanding of authority boundaries	20
Escalation and judgment	20
Written communication and professionalism	20
Total	100

Recommended passing score: 75 points.

The trainer should record:

• Candidate’s score.
• Areas requiring improvement.
• Any conduct concerns.
• Whether resubmission is required.
• Completion date.
• Trainer’s name.
• Final result: Pass, Revision Required, or Fail.

18. Next Module

After passing this module, continue to:

Module 2 — IRC Fundamentals

Candidates should not skip modules unless specifically authorized by the training coordinator.

---

Previous: Program Overview Next: Module 2 — IRC Fundamentals