United Collective of Systems and Networks
Writeup: Digibase Operations, (March 22nd-29th, 2010)
IRC Network Regulations Document (UCSN IRC-NRD)
Consultation: Various channels, Exiled Systems, ShatteredTears, KitsuneParadise
Document Status: Ratified
Digibase Operations - Signed: Kradorex Xeron - On this Monday, 29th day of March of the year 2010.
ShatteredTears - Signed: Keiro Dreamwalker - On this Monday, 29th day of March of the year 2010.
Kitsuria - Signed: Samui Shiiba - On this Monday, 29th day of March of the year 2010.
Exiled Systems - Signed: Karusune Kiyoraka - On this Tuesday, 30th day of March of the year 2010.
AGNPH - Signed: Flygon - On this Sunday, 25th day of December in the year 2011.
This document is enforceable within the scope of the United Collective of Systems and Networks collaborative IRC network.
The network is defined as "collaborative" as it does not fall under the mandate or authority of a single organization outside of basic administration guidance, therefore certain additional regulations may be applied depending on the server in which one is connected.
Terms used within this document:
- "IRC Network Administration" - The authoritative group that manages the IRC network and its resources
- "Network Regulations" - This document
- "Server Regulations" - One or more terms of service or acceptable usage policy documents that are specific to a member organization.
- "Assets" - Resources such as nicks and channel names, typically held through registration services
- "MUST" - An indication of obligatory action that must be performed or loss of privleges or access to systems may occur. "NOT" may also be applied at which point the action must be avoided.
This document will outline definitions of basic words that may be interpreted as to prevent interpretation and to enforce a single definition. These words are placed in quotation then defined after the regulation. Definitions may also appear to be redundant, this is to ensure clarity.
1.1. User Rights
"Rights" are defined as unwaivable abilities.
- Users have the right to fair decisions.
- Users have the right to review and appeal of decisions made by IRC Network administration.
- Users have the right to communciate in their native language with one another.
(Users must be capable of speaking English as to communicate with IRC Network administration)
1.2. User Privileges
"Privileges" are defined as that of which is granted by default and sustained with compliance with regulations, but may be revoked if regulations are breached.
- Users have the privlege to connect and to join channels.
- Users have the privlege to establish channels and place their own regulation upon such channels, provided such regulations do not contradict network regulations.
- Users have the privlege to utilize registration services to protect assets such as channels and nicks.
1.3. User Obligations
"Obligations" are defined as that of which must be fullfilled. Failure to do so will result in removal from channels, servers, or the network.
- Users have the obligation to follow Network Regulations.
- Users have the obligation to follow the organization's regulations of the system in which they are connected.
- Users have the obligation to follow channel regulations of which they are joined to.
- Users have the obligation to understand all regulations.
- Users have the obligation to take full responsibility of any and all content they post.
2.1. Channel Regulations
All channels may operate under their own rules and regulation and are encouraged to create and exercise such regulation. Channel regulation that subverts, reduces, or countermands Network or Server Regulations is prohibited.
2.2. Channel Obligations
All channels are held to following certain regulations, failure to comply will incite IRC Network administration's intervention.
- Illegal content such as child pornography is forbidden
- Illegal content such as illegally obtained software is forbidden
- Channels shall not condone hatred against specific groups based off of race, gender, sexual preference, employment, or beliefs.
- "Harassment" toward any individual or group is prohibited.
- Cursing shall NOT be prohibited by network regulations.
- Channel operators must to the best of their abilities ensure users of their channels follow Network Regulations.
- Channel operators must maintain channel rules and these rules must be in a format that may be reviewed by IRC Network Administration upon request.
- "Closed community" channels must set mode +s.
- Channels must admit IRC Operators to their channel at the IRC Network Administration's disgression.
- "Harassment" is defined as an action where a user badgers, threatens, intentionally upsets or disturbs another user or group.
- "Closed community" is defined as a community where channel operators desire no external interference by unknown users to the channel operator.
2.3. Channel Abandonment
Any channel deemed "abandoned" and without "presence of authority" may become under the authority of IRC Network administration
- "abandonment" is defined as the act, or lack thereof of the Channel Founder failing to identify for their nickserv registration within a reasonable time period of 2 weeks
- "presence of authority" is defined as a presence of a channel administrator (mode +oa) and/or channel successor who may speak on behalf of the channel's interests
2.4. Offensive Content
Any "offensive content" within one channel shall be dealt with by the channel operator at the operator's discretion
Any "offensive content" within two or more channels may result in IRC Network administration intervening against the individual posting content.
- "Offensive content" is defined as content that offends one or more individuals within one or more channels
2.5. Channel Invasion
Channel "invasion" is prohibited and those participating will be removed from the network.
- "Invasion" is defined as the act of users migrating to a channel for the sole purpose of creating issues.
2.6. Channel Operator
A Channel Operator is defined as an individual with channel mode +o set or higher. Channel Operators have authority to designate rules and regulations of their channel as well as take actions within the allowment of server and Network Regulations.
A Channel Operator has the obligation to enforce their channel regulations and to ensure their channel is in compliance with Server and Network Regulations.
3.1. Takeovers of Assets
Assets, such as nicks and channels obtained via "takeovers" shall be locked, restricted, or otherwise rendered inoperable temporarily by IRC Network administration until at which point it is deemed the asset(s) may be released to its correct "registrant".
- "Takeovers" are defined as the act of obtaining access codes or passwords for assets held by another individual or organization as to deny that party access to their resources.
- "Registrant" is defined as an individual who originally registered an asset with registration services.
3.2. Excessive Registration
Users shall not register assets for the sole purpose of preventing their use. those doing so shall have these registrations revoked and at the discretion of IRC Network administration, may be restricted from utilising registration services.
Users bulk-registering assets may be questioned.
Users may not register assets for the purpose of appearing to be an individual or organization they are not.
3.4. Virtual Hosts
Users may request virtual hosts, however, their granting is at IRC Network Administration's discretion and may be revoked without notice.
Virtual hosts that resolve to a common internet address, such as a valid domain name or hostname MUST EITHER/OR:
- Resolve to the IP the user will primarily utilize to connect to the network.
- Be proven that the user in question owns the domain name or hostname to the satisfaction of IRC Network Administration.
3.5 Asset Limits and ExpirationAssets shall expire after a specific period of time, not exceeding 30 days of non-use. Registrants MUST adhere to perscribed limits.
- Nickname assets MUST NOT exceed 20 registrations held per registrant.
- Channel assets MUST NOT exceed 10 registrations held per registrant.
- Registrants may apply to the IRC Network Administration to have no more than 10 Nickname registrations set to "non-expiry", those applying are expected to produce reason they require this. Final decision will be at the discretion of the IRC Network Administration and may be reviewed at any time.
- "non-expiry" is defined as a state where an asset will not be automatically purged.
3.6. Asset Reservation
Users may not register assets for the purpose of "squatting". Such assets shall be locked or deleted at the IRC Network Administration's discretion.
- "Squatting" is defined as the act of withholding assets for the purpose of preventing their legitimate use.
4.1. Network Offenses
Offenses incurred within the scope of the network are when this document is directly breached. Any offenses shall be dealt with by any attending IRC Operator or Administrator at their discretion.
- "Offenses" are defined as an act or series of acts that results in breach of regulations.
4.2. Server Offenses
Offenses incurred within the scope of the server are when a member organization's terms of service (ToS) document or other acceptable usage policy (AUP) is breached. Any offences within this scope shall be dealt with by that organization's policy.
4.3. Channel Offenses
Offenses incurred within the scope of a channel are when channel rules or regulations are breached and are at the discretion of the Channel Operator. Decisions will be enforced by IRC Network administration if requested by Channel operator or "deemed required".
- "Deemed required" is defined as the IRC Network administration re-enforcing a prior decision established by the Channel operator, even if the Channel operator is not present.
5. BOTS AND SERVICES
5.1. User-Operated Bots
Users are permitted to place their own "bots" on the network. Users will be responsible for any and all malfunctions that bots they operate may incurr.
- "Bots" are defined as any automated, or semi-automated client that connects to the IRC network.
User-Operated Bots MUST NOT:
- Be operated for the sole purpose of advertisment
- Be operated to repeatedly post automated messages to channels
- Idle on otherwise empty channels
- Pose as a network service
It is recommended that User-Operated Bots:
- Set user mode +B as to identify as bots to the IRC network
- That are widely used be known to IRC network administration
- That hold user databases of their own encrypt or hash user passwords or access codes
5.2. Network-Operated Bots or Services
Member organizations of UCSN may operate bots or "services", these are regulated both by Network Regulations and their operating organization's discretion.
- "Services" are defined as any program that interfaces directly to the IRC network at the server-level.
Users MUST NOT:
- Repeatedly request resources or information in bulk from bots or services
- Attempt to exploit services or otherwise take bots or services down
- Attempt to create any situation where a channel the user does not operate is unusable
Network services implemented MUST:
- Encrypt or hash user passwords - md5 or stronger is recommended
6.1. System Security
Any attempt or threat by Users to breach security of any system or service shall result in restriction or up to and including permanant removal from the IRC network. It may also be at the discretion of the threatened organization to move to adjust security of systems to restrict access.
6.2. Third Party Security
If there is a threat made toward a third party system or network not associated to the UCSN, it may be at the discretion of IRC Network administration to forward a report to the threatened system or network operator with any identifying information of users involved in the threat.
7.1. Content Indemnification
Content is exclusively the responsibility of Users. UCSN or any of its organizations are obsolved of any content posted to the IRC Network by Users.
7.2 ImpersonationUsers shall not identify utilising names and titles they are not privy, identify as authority without authorization, or otherwise misrepresent their identity.
- Users impersonating other users shall be at the discretion of the attending Channel Operator.
- Users impersonating channel operators shall be at the discretion of the attending Channel Operator.
- Users impersonating officers of UCSN organizations shall be at the strict discretion of the IRC Network Administration regardless of channel regulations.
8. Operator/Administrator Powers
8.1. Actions/Powers as AuthorityOperators and Administrators utilizing "commands" that require "authentication" of one or more services and servers are deemed to be acting with authority and held to this section (Section 8) of this document.
- "commands" are defined as instructions to services and servers.
- "authentication" is defined as the act of gaining additional access above that of a user.
8.2. Non-Interference[See §10.5]Operators and Administrators shall not interfere with regular channel or user activities that are within the scope of regulations. This includes, but is not limited to:
- Modify channel attributes, including modes, settings and other configuration items without explicit permission of the channel operator.
- Modify user attributes, including nicks, hostnames, vhosts, ident ("user" field), settings, and other such items without explicit permission of the user.
8.3. Personal Use of Power[See §10.5]All Operators and Administrators are expected to utilize their powers of authority for official tasks only, Personal usages of power are completely unacceptable and not at all congruent to regulations.
- Threats, or acting against a user or group who is within regulations are unacceptable.
- Favours, or providing power, directly (distributing credentials), or indirectly (utilising powers on behalf of) to users or groups are unacceptable.
9. Governance Committee Powers
9.1. Override of RegulationsA Majority vote of the UCSN Governance committee may temporarily rescind any and all regulations as to ensure effective action in regards to situations that may not be covered effectively by regulations. Accountability is required of all parties that acted outside of regulations. Overrides are not permitted to exceed the original purpose and purposes must be clear and known.
10. Document History[10.1]: Original Writeup: 22-29 March 2010
[10.2]: Ratified: 30 March 2010
[10.3]: Revision: 30 November 2010
[10.4]: Revision: 15 May 2011,
- 2.2. Channel ObligationsAdded:
- 3.5 Asset Limits and Expiration
- 7.2 Impersonation
- 8. Operator/Administrator Powers
- 8.1. Actions/Powers as Authority
- 8.2. Non-Interference
- 8.3. Personal Use of Power
- 9. Governance Committee Powers
- 9.1. Override of Regulations
signed by Digibase Operations, ShatteredTears/EidolonHost, AyhiocIRC, 24/7 Servers
[10.5] Exemption "#Exclusion_Zone": 23 May 2011,
- 0. Preface
- 2.1. Channel Regulations
- 2.2. Channel Obligations
- 3.3. Impersonation
- 4.3. Channel Offenses
- 6.1. System Security
- 9.1. Override of RegulationsAdded:
- 2.6. Channel Operator
- 3.6. Asset Reservation
- 4.1. Network Offenses
- 4.2. Server OffensesRemovals:
- 4.1. Decisions in regards to offenses
signed by ShatteredTears/EidolonHost, 247/Servers, Kitsuria Network, Exiled Systems, Digibase Operations
- 8.2. Non-Interference
- 8.3. Personal Use of Power