So you linked to pissnet: Difference between revisions

From pisswiki
mNo edit summary
No edit summary
Line 20: Line 20:
* swhois: A line that shows up when you are /WHOISed
* swhois: A line that shows up when you are /WHOISed
* operclass: I recommend <code>netadmin</code> for this, but you may use <code>netadmin-with-override</code> (be careful: you may accidentally mess things up that usually are not possible by default)
* operclass: I recommend <code>netadmin</code> for this, but you may use <code>netadmin-with-override</code> (be careful: you may accidentally mess things up that usually are not possible by default)
* mask: Set this to <code>*@host</code>. Host would preferably be your bouncer (if you use a shared one, set it to <code>ident@host</code>), your IP address, or localhost.
* mask: Set this to <code>*@host</code>. Host would preferably be your bouncer (if you use a shared one, set it to <code>ident@host</code>), your IP address, or localhost. It can also be a wildcard. Use CIDRs for IP blocks (<code>*@1.2.3.0/24</code>) for security (<code>10.*</code> matches <code>10.example.com</code>), and make sure you use CertFP or a strong password.
* password: You can use <code>password "INSERT CERTFP HERE" { certfp; }</code> if you client supports client certificates. You can obtain the fingerprint by /WHOISing yourself while using the certificate. Then, to oper up, you can do <code>/oper &lt;operblock name&gt;</code>. (<code>/quote oper &lt;operblock name&gt;</code>, if your client enforces some sort of format, like WeeChat.)
* password: You can use <code>password "INSERT CERTFP HERE" { certfp; }</code> if you client supports client certificates. You can obtain the fingerprint by /WHOISing yourself while using the certificate. Then, to oper up, you can do <code>/oper &lt;operblock name&gt;</code>. (<code>/quote oper &lt;operblock name&gt;</code>, if your client enforces some sort of format, like WeeChat.)
* snomask: You can set snomasks to add to yourself upon opering. Example: <code>snomask foobar;</code>
* snomask: You can set snomasks to add to yourself upon opering. Example: <code>snomask foobar;</code>

Revision as of 13:06, 20 January 2022

This page will guide you through on what you can do to improve your setup, and ideas on what to do next.

Set up your client

You may want to set up your client to oper-up on join, set some user modes, and more.

Here is a few suggestions for user modes:

  • User mode +T(*): Disable CTCPs from being sent to you.
  • User mode +J(**): Prevent SAJOIN/SAPARTs.

(*) noctcp module in upstream UnrealIRCd/PissIRCd doesn't prevent other opers from CTCPing you. Patch is relatively straightforward, though.

(**) Requires module third/nosajoinpartmode. You can do snomasks and modes in your operblock too, see below.

Customize your oper block

You can set things such as:

  • swhois: A line that shows up when you are /WHOISed
  • operclass: I recommend netadmin for this, but you may use netadmin-with-override (be careful: you may accidentally mess things up that usually are not possible by default)
  • mask: Set this to *@host. Host would preferably be your bouncer (if you use a shared one, set it to ident@host), your IP address, or localhost. It can also be a wildcard. Use CIDRs for IP blocks (*@1.2.3.0/24) for security (10.* matches 10.example.com), and make sure you use CertFP or a strong password.
  • password: You can use password "INSERT CERTFP HERE" { certfp; } if you client supports client certificates. You can obtain the fingerprint by /WHOISing yourself while using the certificate. Then, to oper up, you can do /oper <operblock name>. (/quote oper <operblock name>, if your client enforces some sort of format, like WeeChat.)
  • snomask: You can set snomasks to add to yourself upon opering. Example: snomask foobar;
  • modes: You can set modes to add to yourself upon opering. Example: modes "+WJT";

Join some channels

There are channels varying from fun to network management to chat channels.

Channels
Channel Description
#pissnet The main channel of the network
#opers Operator channel. Chatting & network issues are discussed here.
#services Service bots
#(╯°□°)╯︵ ┻━┻ An eval bot running Ruby & shell commands
#pisswiki Wiki logs
#wallops WallopsServ bot
##asciiart ASCII art channel
#donger Fight bot
#shitbots Markov bots and other weird bots
#ducks DuckBot channel

Things to avoid

At pissnet you can do a lot of things, but there are a few things we want you to refrain from or not do at all:

  • Do NOT link Eris (eris.berkeley.edu). This will result in a jupe/delink.
  • Please refrain from flooding too much as this causes server and client SendQ overflows and freezing
  • Please refrain from /KILLing a lot
  • Don't run services that manage nick registrations or channel registrations. UserServs are fine, but please no ChanServ's or NickServ's. We won't U-Line servers, either.
  • Please don't mess with other people's pseudoservers or bots whenever possible
  • Be kind to everyone

Suggestions on what to do

If you like programming, you could:

  • Write a pseudoserver
  • Write a few bots

And remember to have fun!