Your server is linked. Here is what to set up next.
Your oper block
Some settings worth adding to your oper block:
operclass:netadminis enough.netadmin-with-overridelets you do things that are normally impossible, including by accident.mask: limit where you can oper from, for example*@203.0.113.0/24or your bouncer's host. Use CIDR for IP ranges:10.*also matches10.example.com.password: use your client certificate instead of a password, withpassword "your-certfp" { certfp; }./whoisyourself while connected with the certificate to see its fingerprint, then oper with/oper <name>.swhois: an extra line in your/whois.snomaskandmodes: added when you oper up, for examplemodes "+T";to block CTCPs.
To join #opers automatically when you oper up:
set {
oper-auto-join "#opers";
}
Channels
| Channel | What happens there |
|---|---|
| #pissnet | The main channel |
| #opers | Opers: network issues and chat |
| #services | Bots and pseudoservers |
| #shitbots | Markov bots and other weird bots |
| ##asciiart | ASCII art |
Things to avoid
- Do not link Eris (
eris.berkeley.edu). It gets juped and delinked. - Don't flood. It overflows SendQs and freezes clients and servers.
- Don't
/killpeople for fun, and don't mess with other people's bots or pseudoservers. - No services that register nicks or channels: no NickServ, no ChanServ. Nobody gets U-lined.
- Be kind. See Pissnet policies.
Ideas
Write a bot or a pseudoserver. Have fun.
Recovered from the old wiki. See the archived page.