governance
XYZnet Network Charter
Rules and policies for connecting to and using the XYZnet IRC Network. Inspired by classic network charters (e.g. MooNet), updated for XYZircd and Rustic.
Preface
These guidelines govern participation on the IRC medium known as the
XYZnet IRC Network. They apply to users, operators, and server
administrators linked under the XYZnet name. The network is engineered around
XYZircd and Rustic IRC Services; configuration
conventions (including shared XYZnet.conf) exist to keep leaf servers consistent.
Section 1: Server Administrators
Server administrators are active members of the network, not passive hosts. They keep
their server’s local ircd.conf accurate (name, SID, listeners, SSL, links)
while retaining the network-wide XYZnet.conf unchanged unless coordinated
with other admins.
- Maintain working links to agreed hubs and to services (
services.XYZnet.org). - Train and take responsibility for operators with O:lines on their server.
- Give reasonable prior notice before adding global operators or major routing changes.
- Announce planned downtime to other admins/opers (and users when impact is broad).
- New permanent servers are accepted by admin consensus; test links remain temporary and limited.
- Client ports should include at least 6667 (plain) and 6697 (TLS) where possible; routing ports follow current link policy.
Section 2: Global Operators & Local Operators
Global operators handle network-wide abuse and coordinate with admins. Local operators are typically in training under their server admin. Operators are expected to:
- Know basic IRC, XYZircd tools, and Rustic commands relevant to their role (X/Y/Z).
- Handle spam, clones, open proxies, and policy abuse proportionally (warn → kill → kline).
- Use
/SQUITand major routing changes only with coordination and notice (WALLOPS / global notice as appropriate). - Prefer helping users in
#XYZ(and other official help channels) when online. - Never harass users or abuse oper privileges for personal disputes.
Section 3: Users
- Be respectful. Harassment, hate speech, and illegal content are not welcome.
- No flooding, clones used for disruption, malware distribution, or open proxy abuse.
- Register nicks with
/msg X REGISTER; do not attempt to impersonate staff or services. - Channel owners set channel policy within network rules; network staff may intervene for severe abuse.
- Privacy: host cloaking (
+x) is default; do not attempt to de-anonymize users for harassment.
Section 4: Services
Official services are X, Y, Z, and any
additional bots announced by staff (e.g. Weather, LastFM). Names such as NickServ, ChanServ,
OperServ, etc. may appear as reserved stubs on the network jupe and will direct users to
#XYZ. Do not trust unofficial “services” bots.
Section 5: Servers & Routing
- Only authorized servers may link. Unauthorized hubs will be juped or denied.
- TS6 linking and modern CAPABs are required for new servers.
- Statistics collection (thales-XYZ-v1 / stats.XYZnet.org) is an official network service.
Section 6: Amendments
This charter may be revised by network administrators. Material changes should be announced in official channels. Continued use of the network constitutes acceptance of the current charter.
Historical inspiration: classic network charters such as MooNet (1990s), adapted for XYZnet.