
{{TimoNe` } Please settle down, we are about to start
{ TimoNe` } Let's begin. We have an ambitious agenda so please.. settle in, turn on your logging.. and take note of your questions to ask during the pauses. [L1]
{ TimoNe` } Welcome, those of you joining us in #opschool2, our new "mirror" channel addition (to handle the huge demand for seats) ..{grin}. [L2]
{ TimoNe` } A special welcome to all of you in your "home" channels joining us by way of our "Closed Circuit OpSchool Class" system. We are now offering a "Closed Circuit" Class for your own Channel. For info, /msg underbot motd or view our opschool web site. [L3]
{ TimoNe` } Good Day, this instructional script is brought to you by the Undernet Channel Service. Please send comments, suggestions, or remarks to opschool@undernet.org -- I'd like to welcome you all to the Undernet Channel Service OpSchool (Part One). [L4]
{ TimoNe` } We are pleased to announce that the OpSchool Web Site is online and available for viewing at this URL, //www.wildstar.net/~opschool/. Here you can learn about OpSchool Classes, and follow links to many other useful sites. [L5]
{ TimoNe` } I won't cover how to register a channel in this class. If you have questions about registering your channel, please join our new "operational" class (OpSchool Part 2) or ask your questions in #cservice. We have a lot of very knowledgeable people there to help you. [L6]
{ TimoNe` } Today's session will cover how to harness the powerful commands provided in X and W. Our next session (Part 2) includes topics on Channel operation: registration, preventing abuse, flood protection and more. Sessions are scheduled each week - check by using /msg Underbot motd. [L7]
{ TimoNe` } You can also /msg Underbot filelist, for a list of downloadable CSC help files and forms. Or visit our website at http://cservice.undernet.org/ for online forms and registration info. [L8]
{ TimoNe` } Now for the rules of the class. [L9]
{ TimoNe` } The teaching staff is divided up alphabetically. Each assistant will answer questions for the letter group they are assigned to: A-ETutor handles nicks starting with A through E and so on... MiscTutor handles nicks beginning with numbers or characters such as ^, ], _, and so on, french is "Aidetude", spanish "YoAyudo". [L10]
{ TimoNe` } Please direct your questions by private message to the tutor who covers your name group. [L11]
{ TimoNe` } The channel is set to +m -- moderated to lessen interruptions. If your tutor feels that your question would benefit the whole class, he/she may set you +v so you can ask it in the channel. [L12]
{ TimoNe` } The channel is also set to invite-only, this is to prevent continuous interruptions by people entering. [L13]
{ TimoNe` } Do *NOT* change your nick while in class. Auto-Kick on nick change is *active* so as to keep disruptions to a minimum. You will not be allowed back in if you are kicked for changing your nick. [L14]
{ TimoNe` } Do not message the instructor - My job is to keep the lesson flowing. Remember, you have tutors to answer your questions. The numbers you see at the end of the sentences are lesson reference numbers. Both you and the instructors can use these as a guide to help you keep track of where you are in the lessons. [L15]
{ TimoNe` } SESSION A - SCOPE AND DEFINITIONS: This school is run by the Undernet Channel Service Committee. We provide registration of channels on the Undernet, and the services X and W to hold the channels. [L16]
{ TimoNe` } This registration provides a channel manager with a flexible tool for managing the channel and handling channel affairs. [L17]
{ TimoNe` } X and W are specialized servers often referred to as bots which actually hold the channel open and allow for control. [L18]
{ TimoNe` } Now for a few definitions: [L19]
{ TimoNe` } The Manager - The user who applies for registration of the channel. [L20]
{ TimoNe` } Channel Operators - Users given the privilege of being an operator by the manager. The manager grants them access to the bot. [L21]
{ TimoNe` } Userlist - The database in X or W that holds the information about the channel users added to the bot. [L22]
{ TimoNe` } CService Operator - An experienced IRC user who volunteers his or her time and has been certified to help users on #cservice. [L23]
{ TimoNe` } CService Helper - An experienced CService Operator who has been asked to assist CService in providing user support. [L24]
{ TimoNe` } CService Administrator - A very experienced CService Helper who manages CService responsibilities. [L25]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L26]
{ TimoNe` } *** *** *** *** *** *** *** ***
{ TimoNe` } These are actual statements found on insurance forms where
car drivers attempt to summarize the details of an accident
{ TimoNe` } -
{ TimoNe` } 1) The pedestrian had no idea which direction to run, so I
ran over him.
{ TimoNe` } 2) The guy was all over the road. I had to swerve a number
of times before I hit him.
{ TimoNe` } 3) A pedestrian hit me and went under my car.
{ TimoNe` } 4) I told the police that I was not injured, but on removing
my hat, found that I had a fractured skull.
{ TimoNe` } *** *** *** *** *** *** *** ***
{ TimoNe` } SESSION B - CHANNEL MANAGEMENT: Now...for the instructions on channel management. [L27]
{ TimoNe` } As the channel manager you are ultimately responsible for what goes on in your channel ** whether you are there or not **. Your primary duty is to ensure all the users on your channel understand and are willing to comply with the CService guidelines. [L28]
{ TimoNe` } You are also responsible for maintaining the userlist for your channel. Ensuring it is up-to-date is one of the ways you protect your channel. [L29]
{ TimoNe` } Finally you must make an appearance on the channel at least every 21 days. [L30]
{ TimoNe` } If you need to be away from your channel for more than 21 days, fill out a copy of xtempmgr.frm and e-mail it to X@undernet.org (or W@undernet.org) and specify who you want as a temporary channel manager on your channel. [L31]
{ TimoNe` } If you are going to change or add another service provider (ISP), then you should add the new ID to your userlist under a 2nd nick and then fill out and email xhost.frm to X@undernet.org (or W@undernet.org if for W). [L32]
{ TimoNe` } Be sure to email from your OLD address on record with CService to request any changes of manager or ID. [L33]
{ TimoNe` } Changes to host masks, managers or for a forgotten managers password should be directed to X@undernet.org or W@undernet.org [L34]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L35]
{ TimoNe` } *** *** *** *** *** *** *** ***
{ TimoNe` } Fun Things To Do In An Elevator
{ TimoNe` } -
{ TimoNe` } Stare at your thumb and say "I think it's getting larger."
{ TimoNe` } Grimace painfully while smacking your forehead and
muttering: "Shut up. Damnit, all of you just shut up!"
{ TimoNe` } Crack open your briefcase or purse, peer inside and ask:
"Got enough air in there?"
{ TimoNe` } Offer name tags to everyone getting on the elevator.
{ TimoNe` } Ask each passenger getting on if you can push the button for
them.
{ TimoNe` } Listen to the elevator walls with a stethoscope.
{ TimoNe` } *** *** *** *** *** *** *** ***
{ TimoNe` } SESSION C - LEVEL 0 COMMANDS: Now we'll cover user levels and commands: [L36]
{ TimoNe` } These apply equally to X and W, and to any users that are added to the database in the bots. [L37]
{ TimoNe` } A word of caution here -- *ANY* user with level 1 or higher with AUTOOP ON has all the power of a regular channel operator in an unregistered channel. All regular op commands like ban, kick, etc. are available to them. [L38]
{ TimoNe` } The levels for channel personnel range from 0 - 500 [L39]
{ TimoNe` } Level 0 -- These commands do not affect the operation of the channel, and are mainly used for information. The commands are: access banlist chaninfo help lbanlist login map motd newpass pass showcommands showignore and verify. [L40]
{ TimoNe` } /msg X access #channel {nick} to find a users access level on the channel. This tells you their nick, user@host mask, access level, whether autoop is set, and if they are suspended. To see who last modified a user's entry, type /msg X access #channel nick -modif [L41]
{ TimoNe` } You'll also notice the letters LMPU, or some combination there of in your access listings. Example : -W- USER: Luser (*!*luser@*.blah.com) ACCESS: 1 LMPU. The "L" stands for: loaded into memory (the user matches the one in the database). "M" stands for: modified, not saved to disk; the database is saved to disk every 90 minutes. "P" means: has a password set. And "U" means: In use (properly logged in). [L42]
{ TimoNe` } /msg X banlist #channel shows you the channel banlist. [L43]
{ TimoNe` } /msg X lbanlist #channel shows the list of bans set through X. [L44]
{ TimoNe` } If the Lbanlist is too large, you will get a message from X telling you there are too many entries to display. [L45]
{ TimoNe` } There is a way to see all the entries, but you need to fire up your web browser and visit X or W's homepage. [L46]
{ TimoNe` } The URL for X and W is http://cservice.undernet.org/ You can view both X and W's userlists there. [L47]
{ TimoNe` } Remember, the two ban lists are separate. The channel ban list holds 30 bans. They are set by /mode #channel +b *!*userid@host. The Lbanlist (bot list) holds up to 50 entries. [L48]
{ TimoNe` } A user can exist in one list but not the other. Anyone with @ can add to the channel banlist, even if they are not in X or W. [L49]
{ TimoNe` } When a ban is set in X or W, it may not be in the channel ban list yet. [L50]
{ TimoNe` } The channel list is smaller and is lost if the channel closes (like on a netsplit). Channel bans don't lag when the bot is lagged. The Lbanlist is larger and isn't lost if the channel closes. Bans there can be up to 336 hours (2 weeks). For important bans, put them in both lists. [L51]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L52]
{ TimoNe` } *** *** *** *** *** *** *** ***
{ TimoNe` } Actual Calls to AT&T
{ TimoNe` } -
{ TimoNe` } 1) "I've been on hold four months."
{ TimoNe` } 2) "Where is area code 900?"
{ TimoNe` } 3) "I just dialed a wrong 800 number. Will I be charged?"
{ TimoNe` } 4) "Can I put money in this pay phone?"
{ TimoNe` } 5) "What countries do you usually call?" "Germany and New
Jersey."
{ TimoNe` } 6) "Is this an average size bill for you?" "I think
so...it's usually around 3'' by 5''."
{ TimoNe` } *** *** *** *** *** *** *** ***
{ TimoNe` } /msg X chaninfo #channel gives information about the channel manager's nick and user@host mask. [L53]
{ TimoNe` } /msg X showcommands #channel will show you which commands you have available to you on that channel. These depend on the level you have in X or W for that channel only. [L54]
{ TimoNe` } /msg X help command will explain the usage of that command. Use this to see command syntax and a wealth of helpful reminders. [L55]
{ TimoNe` } /msg X map gives information about how the IRC servers are linked. [L56]
{ TimoNe` } /msg X motd displays X's message of the day. [L57]
{ TimoNe` } /msg X showignore shows a list of users X is ignoring. [L58]
{ TimoNe` } The next 3 commands are different for X and for W. They are pass, newpass, and login. To set a password, the command is newpass. To send a password, use pass OR login. And if you have no password, use login as described below. [L59]
{ TimoNe` } To set a password in X for that channel use /msg X@channels.undernet.org newpass #channel {password} [L60]
{ TimoNe` } To set a password in W for that channel use /msg W@channels2.undernet.org newpass #channel {password}. Notice for W it's channels2. [L61]
{ TimoNe` } You cannot set your password until you have logged in or sent your old password. [L62]
{ TimoNe` } To authenticate yourself with X or W, use /msg X@channels.undernet.org pass #channel {password} or /msg W@channels2.undernet.org pass #channel password. [L63]
{ TimoNe` } Also, you can use /msg X@channels.undernet.org login #channel {password} or /msg W@channels2.undernet.org login #channels {password}. If you have no password. You MUST send /msg X login #channel, or /msg W login #channel. If you have a password, you only need to send pass OR login. Remember, if the U doesn't show in an /access command, then the user is NOT yet authenticated. [L64]
{ TimoNe` } As it stands now, all users with access to X or W are required to set and have a password for access. This is a security precaution. [L65]
{ TimoNe` } You can also setup a password for a user when you first add them to the userlist database. We will cover this when we get to the adduser command later in class. [L66]
{ TimoNe` } A password is important for your protection. Many people don't like to set passwords because they think it's a hassle. This leaves them vulnerable; userid's can be changed pretty easily. Without a password, it would be easy to fake identities. [L67]
{ TimoNe` } The verify command is used to determine if a user is an authenticated IRC Operator, CService Helper, or CService Administrator. Typing /msg X verify {nick} will let you know if the person claiming to be a CService representative is authentic. If a user is not an authenticated CService Representative, then be sure to stop by #cservice and ask about them. [L68]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L69]
{ TimoNe` } SESSION D - LEVEL 50 THROUGH 100 COMMANDS: The next level where new commands are introduced is level 50. [L70]
{ TimoNe` } The additional commands at level 50 are kick and topic. These allow a user to kick someone or change the channel topic even if they are not a channel operator. [L71]
{ TimoNe` } /msg X kick #channel {nick} {reason} will kick someone off, and they will see the reason you supply. Note: Your nickname will appear in the reason; there is *not* an anonymous way to kick users. [L72]
{ TimoNe` } /msg X topic #channel {topic} will change the channel topic. If AutoTopic is turned on by the manager, this can be overridden every 30 minutes by X or W and the topic restored. [L73]
{ TimoNe` } The next command level is 75. [L74]
{ TimoNe` } The commands added at level 75 are ban and unban. [L75]
{ TimoNe` } The usage is /msg X ban #channel {nick} (or nick!user@host.mask) {duration} {level} {reason} Note: ban duration is in hours. Duration, level, and reason are not required for a ban, it just gives you more control over what happens. Note #2: There, again, is not an anonymous way to ban someone; your nickname will appear in the reason. [L76]
{ TimoNe` } Remember, bans set by /msg X ban... are set in the Lbanlist. You must /msg X Lbanlist #channel * to see them, NOT /msg X #channel banlist. "banlist" is for viewing channel bans (which can be viewed by typing /mode #channel +b) , "Lbanlist" is for the bot list. [L77]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L78]
{ TimoNe` } *** *** *** *** *** *** *** ***
{ TimoNe` } Ban levels are important. For example, a level 20 ban will not keep the user off of the channel, but will prevent them from being opped. A level 75 or higher ban will keep them out entirely. [L79]
{ TimoNe` } The unban command has the same syntax and is used to remove a ban. You cannot remove or set a ban that's higher than your own access level. [L80]
{ TimoNe` } The next level is 100, this confers full access to all op commands on the user. In other words, this level is just like being an op in an unregistered channel but allows the user to execute the commands thru X without having ops. [L81]
{ TimoNe` } Commands added at level 100 are op deop invite suspend and unsuspend. [L82]
{ TimoNe` } This is the first level at which your access will allow you to op yourself through X or W. Lower levels of access have to be opped by a channel op, they cannot op themselves. Also, no user level lower than 100 can get ops if the channel is SET to StrictOp mode ON. [L83]
{ TimoNe` } It's important to note that at level 100 the potential for abuse exists. Deopping and/or kicking the CService bots is theoretically not possible, however, if for some reason an operator is able to kick or deop the bot, that is considered abuse of the UnderNet Channel Service, and may result in your channel being placed into NoOp mode or even Purged. [L84]
{ TimoNe` } To op someone Use /msg X op #channel {nick} Note: The person being opped will see who is opping them. This is *not* an anonymous way to op. [L85]
{ TimoNe` } To deop someone type /msg X deop #channel {nick} Note: Again, the individual being deopped will see who is deopping them. [L86]
{ TimoNe` } Example: -X- You're deopped by Baldemar [L87]
{ TimoNe` } To have X invite someone to a channel. type /msg X invite #channel {nick}. You can also use this from outside the channel to invite yourself to the channel. Just authenticate with X/W for that channel and then send the invite command --- /msg X invite #channel {yournick}. Note: Using X/W to mass-invite users is considered abuse. [L88]
{ TimoNe` } You can use the invite on yourself if someone sets +i on your channel, invite yourself in. [L89]
{ TimoNe` } Suspension temporarily stops a user's access to X or W. [L90]
{ TimoNe` } The command is /msg X suspend #channel {nick} {duration [s|m|h|d] } where.. s=seconds, m=minutes, h=hours, and d=days [L91]
{ TimoNe` } An example to suspend Joe for 3 days would be... /msg X suspend #here joe 3 d [L92]
{ TimoNe` } You cannot mix time formats. Use only *one* of time formats.. s, m, h, or d [L93]
{ TimoNe` } To unsuspend type /msg X unsuspend #channel {nick} [L94]
{ TimoNe` } Anyone you give ops to, whether or not they have access to X/W, can kick and ban users from the channel. In practice it's probably best not to op anyone who has less than 100 access. [L95]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L96]
{ TimoNe` } SESSION E - LEVEL 400 COMMANDS: The next command level is 400. [L97]
{ TimoNe` } These users are able to modify the userlist by adding or removing users, and changing their information. [L98]
{ TimoNe` } Naturally you would only place a very trusted person in this position. [L99]
{ TimoNe` } The new commands added at level 400 are adduser remuser modinfo clearmode and status. [L100]
{ TimoNe` } You can add a user two different ways, with, or without an assigned password. [L101]
{ TimoNe` } To add a user to the userlist (where the user sets the password), use /msg X adduser #channel {nick} {*!*user@*host} {access level} [L102]
{ TimoNe` } To add a user with an assigned password to the userlist, use /msg X adduser #channel {nick} {*!*user@*host} {access level} {password}. It is also possible to add them when they are on-line by using /msg X adduser #channel {nick} {access} [L103]
{ TimoNe` } To remove a user it's /msg X remuser #channel {nick}. You can't remove or add users with equal or higher access than your own. [L104]
{ TimoNe` } The clearmode command will clear all channel modes from that channel. [L105]
{ TimoNe` } The command is /msg X clearmode #channel [L106]
{ TimoNe` } This can be useful if there is a keyword left set and you can't get in. [L107]
{ TimoNe` } All of these commands can be sent from outside the channel. Should you need to clear the modes to get in, you send your authentication to X/W, and then issue your command. It will work just like you were issuing the command yourself from inside the channel. [L108]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L109]
{ TimoNe` } Famous last words: What happens if you touch these two wires
tog
{ TimoNe` } Famous last words: It's always sunny there this time of the
year.
{ TimoNe` } Famous last words: Don't worry, it's not loaded.
{ TimoNe` } Famous last words: They'd never (be stupid enough to) make
him a manager.
{ TimoNe` } Modinfo is used to change information about a user in the userlist. These include autoop, access, match, and rempass. [L110]
{ TimoNe` } To set autoop, /msg X modinfo #channel autoop {nick} {on/off} - Autoop is a convenient feature that allows you to be opped by the bot when you enter the channel, once you send your password. [L111]
{ TimoNe` } To change a user@host, /msg X modinfo #channel match {nick} {new-user@host} [L112]
{ TimoNe` } We'll get in to user@hosts and hostmask a bit later in the class. [L113]
{ TimoNe` } To remove a password, /msg X modinfo #channel rempass {nick} [L114]
{ TimoNe` } Status shows the channel settings. Channel settings will be covered when I get to 500 level commands. The command is /msg X status #channel [L115]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L116]
{ TimoNe` } Two guys walk into a bar. You think one of them would have seen it!
{ TimoNe` } Three guys walk into a bar. You'd think the third guy would've ducked!
{ TimoNe` } Q: Whats the difference between a bad golfer and a bad skydiver?
{ TimoNe` } A: A bad golfer goes: WHACK..."Damn"! A bad Skydiver goes: "Damn"!...WHACK.
{ TimoNe` } SESSION F - LEVEL 450 THROUGH 500 COMMANDS: The next command level is 450. Users with 450+ access have virtually the same control over the bot as the manager. The commands for 450-499 are join, part, addchan, remchan, and limited access to the SET command. [L117]
{ TimoNe` } To make X join, type /msg X join #channel [L118]
{ TimoNe` } To make X leave, type /msg X part #channel [L119]
{ TimoNe` } Addchan will cause X to rejoin your channel automatically if it goes down for some reason. It will also tell X to maintain the channel modes set at the time you issue the addchan command. (ie +nt in most cases). [L120]
{ TimoNe` } Addchan saves manager configuration of SET commands. [L121]
{ TimoNe` } The syntax is /msg X addchan #channel [L122]
{ TimoNe` } The remchan command has the opposite effect. You will need to make X join if it ever leaves and it will not maintain any modes. [L123]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L124]
{ TimoNe` } Little Known Fact:
{ TimoNe` } Birds take off at sunrise. On the opposite side of the world, they are landing at sunset. This
causes the earth to spin on its axis.
{ TimoNe` } The final level is 500 and there is only one new command. Set - This command is partially available to 450-499 users, but is mainly used when you originally set up the channel. The set command has a number of parameters to choose from. [L125]
{ TimoNe` } * MassDeopPro is the maximum number of deops by a single user in a 15 second period. This is to prevent channel takeovers by one user deopping everybody else. For example, with massdeoppro set to 5, I can only deop 5 people in 15 seconds. [L126]
{ TimoNe` } * NickFloodPro is the max number of nick changes by a single user in a 15 second period. [L127]
{ TimoNe` } * FloodPro is the maximum number of lines that can be sent to the channel in a 15 second period. This type flood refers to kicks, topic changes, banlist clearing, etc. This does not refer to text lines that users type in the chat window. [L128]
{ TimoNe` } * AlwaysOp means X will always get ops when it enters the channel. [L129]
{ TimoNe` } * OpOnly disables all of X's commands except op. [L130]
{ TimoNe` } To set any of these parameters Use /msg X set #channel {parameter} {value-(on/off)} [L131]
{ TimoNe` } * NoOp set to ON means nobody may be a channel operator except X. This doesn't mean you don't have control of X or the channel. If you have access to X and authenticate with it, you can issue commands like kick, ban, etc. through the bot. You just can't be opped yourself. [L132]
{ TimoNe` } * Lang sets the default language for the channel. The available languages are EN (english) DE (deutsch) FR (francais) and NL (dutch). A SP (spanish) version is currently under development. [L133]
{ TimoNe` } * StrictOp is a parameter that only allows only those users with 100 level or higher access to X/W to be opped. [L134]
{ TimoNe` } With StrictOp set ON -- users that are server opped after a netsplit may retain ops. If this user tries to op anybody who isn't 100+ the user will not be opped and the person doing the opping will be deopped. [L135]
{ TimoNe` } * Set URL {URL} will store the URL associated with that channel, and it will be displayed when a user does a chaninfo on that channel. [L136]
{ TimoNe` } * Set Description {topic} stores the default channel topic, think of this topic as the 'theme' of your channel, and like URL, it too will be displayed using chaninfo. [L137]
{ TimoNe` } * With AutoTopic set to ON -- X/W will reset the channel topic to the official URL and Description every 30 minutes *if* the channel is active. [L138]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L139]
{ TimoNe` } Grasshopper walks into the bar. The bartender "Don't we have a drink named after you?" and
he winks to the grasshopper. The Grasshopper looks surprised and replies, "You have a drink named
Steve?"
{ TimoNe` } How many lawyer jokes are there? Three, the rest are true stories.
{ TimoNe` } SESSION G - HOSTMASK CREATION: That covers the basic command for levels 0 through 500. Now we'll move on to hostmasks and user@hosts. [L140]
{ TimoNe` } A hostmask is the way X/W identifies you when you communicate with it. It has benefits and drawbacks associated with it... [L141]
{ TimoNe` } The benefits are clear, X/W knows who is trying to communicate with it and can verify it against its database. It also allows X/W to identify users that aren't in its database. [L142]
{ TimoNe` } The second part means that when a user issues a command such as ban, kick, etc, X/W uses the hostmask to identify the individual to use the command on. This means that X/W will know you regardless of what nick you currently have. [L143]
{ TimoNe` } There are several drawbacks also. [L144]
{ TimoNe` } First, a hostmask can be TOO general, it can allow other users with PPP accounts to appear to be you. [L145]
{ TimoNe` } NEVER use a host mask like *!*@* ..we consider that abuse and grounds for a channel purge. [L146]
{ TimoNe` } Example: A user's whois info is Meathead ~meathead@ppp23.texasweb.net -- a good hostmask would look like *!*meathead@*.texasweb.net [L147]
{ TimoNe` } The *!* compensates for the ~ in front of the userid (and/or nick)... [L148]
{ TimoNe` } The * behind the @ compensates for the changing ppp port (ppp23) [L149]
{ TimoNe` } We'll pause briefly in case you have any questions that you need to ask your tutor. [PAUSE] [L150]
{ TimoNe` } Attorney: This is a complicated case, be a little more pessimistic. Defendant: Yes and its in the
hands of 12 people who couldn't figure out how to get out of jury duty!
{ TimoNe` } Famous last words: "Don't worry, I can handle it."
{ TimoNe` } Famous last words: "If you were as smart as you think you are, you wouldn't be a cop."
{ TimoNe` } If you make it too general, perhaps *!*@*.texasweb.net, you could open yourself up for trouble. [L151]
{ TimoNe` } *Anybody* on texasweb.net could appear to be the user you are trying to identify. [L152]
{ TimoNe` } This is one of the best reasons for all users being required to set a password for X/W. A password guarantees that nobody else will be able to use your access to cause trouble. [L153]
{ TimoNe` } For IP Addresses (example: ~user765@205.208.228.63) the same principles apply. Normally the last set of digits are the only ones that change on an IP address. [L154]
{ TimoNe` } So a good hostmask would look like this: *!*user765@205.208.228.* (Never use 2 wildcards * in an IP --} *!*user@120.130.* is ok, *!*user@120.130.*.* is NOT. [L155]
{ TimoNe` } There are 2 ways your host address may resolve. One is a DNS NAME (like *gnn.com), and the other is as an IP Address (like 205.226.43.*). [L156]
{ TimoNe` } Your userid@host must match the entry in X/W for the bot to recognize you. Some servers may resolve the host one way, others the other way... [L157]
{ TimoNe` } Try changing servers to find one that will resolve as you need to match the bot. You can also have a 2nd ID entered in X/W so that it will recognize you BOTH ways. [L158]
{ TimoNe` } A user can have any number of entries in X or W depending on the number of internet accounts they have. Generally you may need to add a second entry to cover his/her IP Address. [L159]
{ TimoNe` } Remember, the wildcards *!* and * replace information that changes each time the user connects to his or her ISP. [L160]
{ TimoNe` } You can get more help with hostmasks in #cservice. [L161]
{ TimoNe` } We'll pause briefly in case you have any questions to ask your tutor. [PAUSE] [L162]
{ TimoNe` } Did you hear about the Indian who drank too much tea?
{ TimoNe` } he drowned in his teapee
{ TimoNe` } Waiter! what's this fly doing in my soup?.... Backstroke, sir
{ TimoNe` } I'll save our other topics for next time.. when you can join us for OpSchool Part 2: "A Channel User's Guide to the Galaxy." You'll hear how to get and keep a registered channel, what Undernet considers abuse, survival skills for netsplits, and an all-time favorite. [L163]
{ TimoNe` } Surviving Floods: * A Noah's Ark for all users! * [L164]
{ TimoNe` } This script was made possible with the help of quite a few people. I'd like to thank the originators.. Pucker, MatthewA, Jini, D-in-Tx, Manning, Teal, SeKs, Coccyx, BitBT, Rotundo, Cyke, and more recently, DrCkTaiL, MarkT, Mike, Robinb, Signe and Gentle1..and who ever else that I forgot. =D [L165]
{ TimoNe` } I'd also like to thank all the people who volunteer their time to help out presenting this class... without you folks, it just wouldn't be possible to do this! Thanks! [L166]
{ TimoNe` } On a personal note... [L167]
{ TimoNe` } I've had fun helping out here today.. Thank you all for listening so politely {g}. [L168] { TimoNe` } You now have all the commands you need to help yourself and others make Undernet kinder and gentler. I hope you will try them out, learn them and share with others. [L169]
{ TimoNe` } This concludes our class, thank you for taking the time to attend. [L170]
{ TimoNe` } I would also like to thank the channels that have participated by way of our "Closed Circuit OpSchool Class" system. [L171]
{ TimoNe` } We will now open the channel up for general questions. [END] [L172]
{ TimoNe` } To find out when the next opschool class is scheduled type in /msg underbot motd The latest info will reply back to you. Also you can go to http://www.wildstar.net/~opschool/
{ TimoNe` } To get a copy of #opschool log do /msg underbot get log or /msg underbot mail log (email@address). Also, you can go to http://www.wildstar.net/~opschool/