Running a bot on AustNet: rules and requirements

Deploying a bot or script on AustNet requires adherence to the network's Acceptable Use Policy (AUP). Because automated scripts have the potential to disrupt infrastructure or impact user experience, all bots must meet clear identification, registration, and behavioral standards.

Core Requirements for All Bots

1. Register with OPAS / NickOP:
2. Bot owners must properly register their automated clients with network services. Operating unregistered or anonymous background scripts can result in network services blocks or operator intervention.
3. Enable User Mode +B:
4. Every bot must clearly identify itself to the network by applying user mode +B immediately upon connecting and authenticating. This distinguishes automated infrastructure from human chatters.
5. Strictly Prohibited Activities:
6. No Flooding or Spamming: Bots must not flood channels, spam users, or trigger excessive message queues.
7. No Mass Messaging: Unsolicited mass messaging, mass private notices, or automated mass-invites (using tools like OPAS/CTCP for bulk actions) are strictly prohibited.
8. No Unauthorized Data Collection: Gathering or scraping user data without explicit consent violates network policy.
9. No Channel Takeovers: Scripts must not be used to force hostile takeovers, mimic network services (ChanOP / NickOP), or execute disruptive operations.

Best Practices for Bot Operators

1. Handle Reconnects Cleanly: Ensure your bot script handles server splits, lag timeouts, and ping-pong timeouts gracefully without spamming reconnection attempts.
2. Authenticate via SASL: Configure your bot framework to log in securely using SASL at connection time so its nickname is claimed before joining any channels.
3. Respect Channel Rules: Even if a bot is permitted network-wide, channel operators retain the right to ban or remove automated scripts that disrupt their specific community spaces.