Gary`s`WebSite

Gazduire site-uri web nelimitata ca spatiu si trafic lunar la doar 15 eur / an. Inregistrare domenii .ro .com .net .org .info .biz .com.ro .org.ro la preturi preferentiale. Pentru oferta detaliata accesati site-ul BluePink

Gary`s`website`for`friends`and`enemies

Welcome to Gary`s website , please have fun here, contact emails: <<<<< IRC@K.Ro >>>>> and GaRiCi@gmail.com

phone nr: 0721164266; my sites: www.ioNeL.Tk ;

Undernet.Org Commands by Gary

Session Start: Sat Apr 15 06:07:58 2006

Session Ident: #opschool

[06:07] * Now talking in #opschool'

[06:07] * Set by X on Sat Apr 15 05:40:53

[06:07] * X sets mode: +o [nIckmenza]

[06:18] <[nIckmenza]> Hello everyone :o) [L1]

[06:18] <[nIckmenza]> Please sit back, turn your logging on and keep for later review. [L2]

[06:18] <[nIckmenza]> This instructional script is brought to you by the Undernet Channel Service Committee. Please send comments, suggestions, or remarks to cservice@undernet.org [L3]

[06:18] <[nIckmenza]> In this class, we will give you all of the answers to make Usernames & Channel Registrations easier to understand, and the guidelines we require for all channel applications. [L4]

[06:18] <[nIckmenza]> I'd like to welcome you all to the Undernet Channel Service OpSchool (Part One). [L5]

[06:19] <[nIckmenza]> Now for the rules of the class.... [L6]

[06:19] <[nIckmenza]> The teaching staff is divided up alphabetically. Each assistant will answer questions for the letter group they are assigned to: A-F_Tutor handles nicks starting with A through F and so on... [L7]

[06:19] <[nIckmenza]> MiscTutor handles nicks beginning with numbers or characters such as ^, ], _, and so on, French is "AideTout", Spanish "YoAyudo", Romanian "EuAjut". [L8]

[06:19] <[nIckmenza]> If your nick falls under the letter A, please use the tutor of the first letter in your nick (ex. Ace would /msg A-F_Tutor) [L9]

[06:19] <[nIckmenza]> Please direct your questions by private message to the tutor who covers your name group. [L10]

[06:19] <[nIckmenza]> The channel is moderated (+m) and may be set to invite-only (+i) to lessen interruptions. If you get disconnected, please message a tutor to be invited back into class. [L11]

[06:19] <[nIckmenza]> You will not be permitted to change your nickname during this class. A ban on *!*@* prohibits nickname changes. [L12]

[06:19] <[nIckmenza]> Do not message the instructor - My job is to keep the lesson flowing. Remember, you have tutors to answer your questions. [L13]

[06:19] <[nIckmenza]> 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. [L14]

[06:19] <[nIckmenza]> To get rid of disruptions of people leaving or quitting, you may wish to put these messages in your status window. In mIRC, go to options, and uncheck Joins/Parts in channel, and Quits in channel. [L15]

[06:20] <[nIckmenza]> We will now take a brief pause in order for you to turn on your logging and locate your tutor. [ph] [L16]

[06:20] <[nIckmenza]> While Undernet Channel Service has many methods of educating the network public about the nuances of our services, many people seem determined to avoid the FAQs, the online classes, and often even the common sense advice rendered in our help channel. [L17]

[06:20] <[nIckmenza]> This in turn ends up creating these work-producing, expectation-shattering ideas, several of which are simplistically explained below. [L18]

[06:20] <[nIckmenza]> Understanding the basic misconceptions held about Undernet Channel Services will make your username and channel registration and maintenance experience much easier. [L19]

[06:20] <[nIckmenza]> We'll start by learning how to create and register a username with X. [L20]

[06:21] <[nIckmenza]> In order to use X at all or to register a channel, you need to have a username. Keep in mind, this is *NOT* registering a nickname. Undernet does not provide nickname registration. Just to keep this clear :o) [L21]

[06:21] <[nIckmenza]> Now, to create a username, go to our website at: http://cservice.undernet.org/live/ [L22]

[06:21] <[nIckmenza]> At about the middle of the page, under the login box, there is a line labeled: "If you do not have an account create one now!" Click on the "Create one" link. [L23]

[06:21] <[nIckmenza]> There are 8 steps on the next page that *MUST* be completed or you will not receive a username. They are as follows... [L24]

[06:21] <[nIckmenza]> *Step 1 - Age Statement* - You must specify whether or not you are above the age of 13 or not. If you are below the age of 13, we cannot ask you personal questions such as your name or email address without parental consent. Thus meaning you cannot register a username, since we cannot verify you. [L25]

[06:21] <[nIckmenza]> *Step 2 - Choose a Username* - Here is where you pick your username. Remember, it has to be unique. There are over 140,000 usernames. Someone probably thought of the one you want before you did :o)Choose it carefully cause you won't be able to change it later! [L26]

[06:22] <[nIckmenza]> *Step 3 - Enter your email address* - This should be your email address, given to you by your internet service provider. If you are unsure what your email address is, contact your provider. [L27]

[06:22] <[nIckmenza]> Free emails, such as hotmail, yahoo, geocities, and other non-paid emails are not accepted for registration. This is due to way to much abuse from users on these providers. [L28]

[06:22] <[nIckmenza]> *Step 4 - Language of choice* - Here you will be able to choose the language you desire to use with X commands replies later. [L29]

[06:22] <[nIckmenza]> *Step 5 - Secret Question/Answer* - This is for password/username retrieval. Makes sure when you make your selection and input in this field, you write down your answer somewhere safe and keep it. You will need this if you forget your password. [L30]

[06:22] <[nIckmenza]> *Step 6 - Security Code* - This is the code who prevent multiple submitions for username registrations.Enter the code you see in the above picture into the below input box (upper/lower case doesn't matter). [L31]

[06:22] <[nIckmenza]> *Step 7 - READ THIS INFO: Individuals are granted the use of a Channel Service username specifically to gain access to channel services. While you need not use channel services to have a username, be aware that attempts to register multiple usernames to the same person will result in a suspension of all the offending names. Don't jeopardize your access to channel services by trying to register multiple usernames on our system. [L32]

[06:23] <[nIckmenza]> Finally, Step 8, Click on submit. After you do so, a link will be emailed to you. Make sure you have cookies enabled in your web browser, then click on the link provided in email or simple copy/paste the link into your browser and visit it. [L33]

[06:23] <[nIckmenza]> This will take you to a webpage that will give you your password. PLEASE write it down somewhere safe, and do not lose it. It can be quite difficult to retreive your password if you lose it. [L34]

[06:23] <[nIckmenza]> This is the basics of username registration. If you have any questions regarding anything specific, ask your tutor, or join #usernames and ask one of our many qualified helpers. [L35]

[06:23] <[nIckmenza]> We will now pause briefly to allow you to catch-up and to ask any questions to your tutor that you need. [ph] [L36]

[06:23] <[nIckmenza]> Next we`ll have a look on channel registration system and the maintainance of channels registered with X. [L37]

[06:24] <[nIckmenza]> Active unregistered channels are owned by the groups that use them, and usually there a consensus about who are the founders, and therefore owners, of the channels. [L38]

[06:24] <[nIckmenza]> Many applications for channel services are submitted by folks who either have no existing relationship with the channel, or are doing so without the knowledge or support of the channel membership. [L39]

[06:24] <[nIckmenza]> They are termed "takeover applications". Any such applications are rejected and the applicant placed on a probation if he tries it repeatedly. [L40]

[06:24] <[nIckmenza]> Also to prevent abusing of our registration system: [L41]

[06:24] <[nIckmenza]> * A new username will be prevented from registering a channel for 10 days after its creation. [L42]

[06:24] <[nIckmenza]> * A new username will be prevented from supporting any channels for 5 days after its creation. [L43]

[06:25] <[nIckmenza]> * A user won't be able to support more than 2 channels at any given time. [L44]

[06:25] <[nIckmenza]> <Applicant>: All I need to get my channel registered is 10 usernames? [L45]

[06:25] <[nIckmenza]> The requirement for registration support on the application is 10 people, not 10 usernames. Admittedly, usernames are the only way we can verify that the 10 supporters are real, and that they actually support the applicant as manager. [L46]

[06:25] <[nIckmenza]> That is why we require 10 usernames for supporters, generally only one e-mail address is allowed per person with an ISP account. [L47]

[06:25] <[nIckmenza]> Supporters need to be people who frequent your channel and have helped to establish it as a viable channel entity deserving of registration services. [L48]

[06:25] <[nIckmenza]> A channel is registered only after its application has been accepted by CService, not after the application has been successfully submitted. [L49]

[06:26] <[nIckmenza]> It takes 10-12 days for your application to be reviewed, verified, checked, twisted, turned; a length of time called the posting period. [L50]

[06:26] <[nIckmenza]> Having posted an application does indicate a claim of ownership, but the claim must be validated, and this takes time. [L51]

[06:26] <[nIckmenza]> We will now take a brief pause in order for you ask your tutor any questions. [ph] [L52]

[06:26] <[nIckmenza]> <Applicant>: My channel is in incoming. What does incoming mean?? [L53]

[06:26] <[nIckmenza]> Incoming is the time immediately after your application is posted on the web site. All channels are in incoming for 72 hrs, or when all supporters have voted on the application. [L54]

[06:27] <[nIckmenza]> <Applicant>: My channel is currently in Pending Traffic Check. Explain this please. [L55]

[06:27] <[nIckmenza]> Traffic check is the step in registration process where we check the traffic of your supporters and users in your channel. [L56]

[06:27] <[nIckmenza]> <Applicant>: My channel application is now Pending Notification. Explain "Pending Notification" please. [L57]

[06:27] <[nIckmenza]> This means the application has fulfilled the initial traffic requirements. You will receive notices in your channel that your application is pending and everyone will be able to object via web to the application for 3 days (72 hours). [L58]

[06:27] <[nIckmenza]> The objections must have valid reasons or will NOT be taken into consideration. [L59]

[06:27] <[nIckmenza]> There are also many reasons for what your channel can get rejected anytime during this period is posted on web.It can be cause of multiple supporters of same person used in the application or just because one or more of your supporters got fraud or suspended during the application process. [L60]

[06:28] <[nIckmenza]> <Applicant>: My channels status shows it is waiting for review. What does that mean? [L61]

[06:28] <[nIckmenza]> Ready for Review refers is the final step in the process and your channel will be reviewed in the next 2-3 days.This doesn't mean will be accepted.The decision could be also rejected. [L62]

[06:28] <[nIckmenza]> <Applicant>: I'll use this username from this guy in another channel, he'll never know I did. [L63]

[06:28] <[nIckmenza]> Actually he will. All usernames used on the application are sent a notice when they login on the web or to X on IRC, giving them the opportunity to call your bluff. [L64]

[06:28] <[nIckmenza]> If someone replies to a notice of support saying "I never gave my consent" or "I don't know this guy" or "get me off your mailing list", then you've blown it. [L65]

[06:28] <[nIckmenza]> Your application will be rejected, your username and channel will be placed on NOREG list for 3 days and you won't be able to apply for the channel until then.Make sure that the usernames that you use are people you know (and trust not to back stab you) and are active in your channel. [L66]

[06:29] <[nIckmenza]> <Applicant>: I just opened my channel and I need X to get it off the ground. [L67]

[06:29] <[nIckmenza]> A simple quote from our registration web page, authored by a most clooful admin, is appropriate here: [L68]

[06:29] <[nIckmenza]> "Channel registration is not meant as a means to start a new channel.It is meant for previously established channels to have an opportunity to have some stability.If you are first starting a new channel, then just start using your channel and give it time to see if a reasonable user base develops to justify registration." [L69]

[06:29] <[nIckmenza]> We'll know if you don't have the required traffic for registration and you'll waste 6-8 days in the posting period finding out that we know.Once your channel is rockin', then registration should be fairly easy. If it doesn't yet rock, then be patient until it does :) [L70]

[06:29] <[nIckmenza]> Let's pause here so that you may ask questions of your Tutors.. ask now while your questions are fresh. [ph] [L71]

[06:36] <[nIckmenza]> Let's look at some of what you need to do to apply to register at our website: http://cservice.undernet.org/live/ . First you need to login, Enter your username and password in the box provided at the site. Then click on the link "Register a Channel" on the left. [L72]

[06:36] <[nIckmenza]> Read the Acceptable Use Policy or AUP carefully. It will give you vital information on Channel Registration. If you agree to bide by the AUP click on "I ACCEPT THE ABOVE". If you do not agree or your channel is in violation of the AUP, Then you can not register your channel. [L73]

[06:36] <[nIckmenza]> As a channel manager you are responsible for the channel and seeing that your channel users and ops follow all Channel Service guidelines, so PLEASE READ IT BEFORE YOU APPLY [L74]

[06:37] <[nIckmenza]> The automated site walks you through each step of the process.. so it pays to be prepared. Realize that Cservice gets 150 applications a day.. over 1000 a week! Help yourself and us by taking the time to follow the steps. [L75]

[06:37] <[nIckmenza]> Have the following information ready *before* you try to apply: 1) Channel info: #channel-name, description.. 2) Manager information: That your personal information 3) Supporter info: 10 Usernames [L76]

[06:37] <[nIckmenza]> The channel name must be not currently registered or on probation due to past abuse and it must begin with alpha-numeric or ASCII (enhanced) characters only. Also, the name *must* describe the channel in some way (eg: #!!!:P is unacceptable). [L77]

[06:37] <[nIckmenza]> The description refers to why users join.. eg: #CarTalk - autorepair. While Cservice does not censor channel content, NO channels are permitted for illegal activities, such as warez trading or child pornography (more on this later). [L78]

[06:37] <[nIckmenza]> The manager's information is important so we may contact you if needed. Please make sure that the information on your username is correct, it will be kept confidential [L79]

[06:37] <[nIckmenza]> The 10 supporters you enter will be notified from X next time they login. Note that they are supporters, NOT necessarily users you plan to make Ops. Once the channel is registered, the manager is the only access that is in X .. you then add those people you choose at the appropriate levels [L80]

[06:38] <[nIckmenza]> Don't even think of trying to register *more* than one channel - if you try, you will lose BOTH, pronto! Cservice screens applications for many issues: Known abusers, Prohibited activities, Bogus supporters, Multiple registrations and much more. (Trust me, these folks are tenacious.. so, help by supporting the rules). [L81]

[06:38] <[nIckmenza]> With that in mind, realize that when you register a channel, you agree to take care of that privilege by preventing abuse and understanding the rules. Let's move on to see how to keep your channel from being purged, now that you have worked hard to get it this far. [L82]

[06:38] <[nIckmenza]> There are two main ways you can lose the services of X in your channel: Abandonment (or apparent absence) and Abuse. Since this can happen as often out of not knowing as out of malice, it's crucial that you have the facts. Getting X purged from your channel is.. a very bad thang ®. [L83]

[06:38] <[nIckmenza]> A channel manager has a large responsibility that takes time and commitment. You agree to take care of what happens, *even when you are off-line*. Start by preventing a purge for your absence or for low traffic. [L84]

[06:38] <[nIckmenza]> Your 500 level access is the key. You need to login to *that* access regularly, with no absence longer than 21 days. CService gets a list of all managers that have failed to login like that. They will look at the channel and decide whether to purge the channel or seek out a new manager. The decision is theirs and is final. [L85]

[06:38] <[nIckmenza]> A registered channel is up for grabs if the manager is missing for 21 days. [L86]

[06:39] <[nIckmenza]> There any number of reasons why a manager may be missing. We do require that a manager authenticate his user account at least every 21 days as a bookmark for review, usually channels are not purged and made available for reapplication so quickly. [L87]

[06:39] <[nIckmenza]> We try to establish if the manager is indeed present but can't authenticate due to a forgotten password.If the manager is truly gone but the channel has a lot of traffic, we try to mediate and establish who the consensus new manager should be and let the registration remain. [L88]

[06:39] <[nIckmenza]> Channels purged for missing manager usually also have no traffic anymore and are indeed open for reapplication. Remember that the channel still belongs to the community that resides there, and their consensus will be required in choosing a new manager. [L89]

[06:39] <[nIckmenza]> <Channel Manager>: I'm changing ISPs and I'll have a new e-mail, no need to contact CService about it. [L90]

[06:39] <[nIckmenza]> If you are going to change ISPs, use the e-mail change form available at http://cservice.undernet.org/ followed by clicking on "Web Interface". You must be able to login to your username to change the e-mail address. [L91]

[06:39] <[nIckmenza]> Our only way of verifying who is really the manager of a channel is by their "e-mail of record", the e-mail that was used on the application for your username. [L92]

[06:40] <[nIckmenza]> If you forgot to change email before you change the ISP simply go to http://cservice.undernet.org/docs where you will find the forms to change your email on record via email to X@undernet.org. [L93]

[06:40] <[nIckmenza]> Select the form for your language and copy/paste into your new email address you want for the username,fill the form with info about your username and send it to the email address we specified before. [L94]

[06:40] <[nIckmenza]> PLEASE use this form ONLY if you can't access your old email we have on record with your username anymore. [L95]

[06:40] <[nIckmenza]> Also incomplete forms with missing informations will not be proccessed so you better remember something about your username info or there will be impossible for us to verify it is really you who owns the username. [L96]

[06:40] <[nIckmenza]> Any official contact with the manager by CService is done with this e-mail address. That is why it is paramount that CService have a current e-mail on record for every channel manager. [L97]

[06:40] <[nIckmenza]> Any channel manager or user with a 500 level access must update a new e-mail of record with CService to maintain your channel ownership.Do this *before* you change ISPs, so we can see your form request from the current e-mail of record and know it is really you. [L98]

[06:41] <[nIckmenza]> <Channel Manager>: I'm there everyday; how can someone say I'm a missing manager? [L99]

[06:41] <[nIckmenza]> The usual circumstance here is ignorance of our system. There is only one 500 account and it is awarded to the manager when his application is accepted. Usually a manager will add a 499 account with a second username, so he can still login. [L100]

[06:41] <[nIckmenza]> What the manager neglects to do is tell CService they lost their e-mail account or password for the 500 access. If you don't authenticate a 500 account, we have no way of knowing whether you are really there. [L101]

[06:41] <[nIckmenza]> This is a simple process and can be fixed at http://cservice.undernet.org/ followed by clicking on "Web Interface". There you will see the "Forgotten Password" link. [L102]

[06:41] <[nIckmenza]> We will now take a brief pause in order for you ask your tutor any questions. [ph] [L103]

[06:43] <[nIckmenza]> The userlist is another key to channel activity. How often do users join and get op'd *without* logging in? The result is that those listed with access to X appear as away longer than they really are. Beware: channels with few active listed users as well as an aging 500 access may be purged. [L104]

[06:43] <[nIckmenza]> Prevent your channel from appearing as inactive, low traffic or idle by *always* logging into X with passwords! And have your Ops do the same. [L105]

[06:43] <[nIckmenza]> Channels also get purged for abuse by the Ops and users: Abuse of.. 1) X.. 2) Users.. 3) Other channels.. and 4) Prohibitions against illegal activities. Since the manager is ultimately responsible, be sure you know what Undernet considers abuse so that you can recognize and control trouble before it puts your channel at risk. [L106]

[06:43] <[nIckmenza]> Undernet has a concise policy towards abuse: *zero tolerance* . The Server Admins and Irc Ops collaborate to detect and remove clones, flooders and others who harass users. In fact, one of the channels where you can find help on abuse is #zt.. meaning zero tolerance. [L107]

[06:44] <[nIckmenza]> 1) Abuse of X: While kicking or de'opping X can't usually be done, any efforts to do so waste resources and trigger an immediate response from CService. Often it is a bot or script, so insist that *all* such bots disable net hack protection so they don't interfere with X. [L108]

[06:44] <[nIckmenza]> 2) Abuse of Users: Many of you have probably experienced floods or denial of service attacks. We will cover ways to protect yourself in another session. Any channels harboring or condoning such attacks are at immediate risk and, once purged, may lose the privilege of any re-registration. [L109]

[06:44] <[nIckmenza]> Mass messages or mass inviting is also abuse. Aside from being annoying and rude, they are a terrible waste of bandwidth and a drain on resources. Alert your users and report any such incidents to #cservice. [L110]

[06:44] <[nIckmenza]> <Channel Manager>: One of my high-level ops was spamming invites to our channel, but I wasn't online so it's not my fault. [L111]

[06:44] <[nIckmenza]> But you will get blamed. You are responsible for anything that is done by ops in your channel. [L112]

[06:44] <[nIckmenza]> It's important that you realize that the ops you chose will reflect directly on you and your channel and must behave on the net according to the established do's and don't's. [L113]

[06:45] <[nIckmenza]> A user spamming invites, flooding users or channels, taking over channels, while authed in a registered channel makes that channel, and you, responsible. [L114]

[06:45] <[nIckmenza]> 3) Abuse of Other Channels: Attacks or takeover attempts on other channels, whether registered or not, are grounds to purge X. Note: "they started it" is *not* an acceptable reason to retaliate. Report any incidents, instead of engaging in abuse yourself. [L115]

[06:45] <[nIckmenza]> 4) Prohibited Activities: Illegal acts include trading warez or pirated software, software used to damage other systems, stolen services or accounts and involvement with child pornography. Not only will these result in a purge of X but also in appropriate criminal charges. Undernet cooperates with responsible authorities to eliminate these forms of abuse. [L116]

[06:45] <[nIckmenza]> While most channels don't harbor abuse knowingly, it's important that you recognize all we have mentioned. Report incidents by sending a timestamped log with relevant /whois details to -> abuse@undernet.org. [L117]

[06:45] <[nIckmenza]> You also prevent abuse by giving Ops access carefully.. appointing only users you know and trust, and by making sure they know what your channel permits. They represent your channel, especially when you are not on-line. [L118]

[06:45] <[nIckmenza]> Let's pause here so that you may ask questions of your Tutors.. and careful not to flood 'em :o) [ph] [L119]

[06:47] <[nIckmenza]> I'll save our other topics for next time.. when you can join us for OpSchool Part 2: "The Lost World of X". [L120]

[06:47] <[nIckmenza]> This script was made possible with the help of quite a few people. I'd like to thank the originators.. Pucker, MatthewA, D-in-Tx, Manning, Teal, SeKs, Coccyx, and more recently, Mikey-, LordLuke and DaveB, and who ever else that I forgot :o) [L121]

[06:47] <[nIckmenza]> 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! [L122]

[06:47] <[nIckmenza]> Let's not forget the past leader of OpSchool Team - Isaiah (CService Admin)...Rest in peace dear friend... [L123]

[06:47] <[nIckmenza]> On a personal note... [L124]

[06:48] <[nIckmenza]> I've had fun teaching this class, and I hope you learned something during this session. [L125]

[06:48] <[nIckmenza]> This concludes our session, thank you for taking the time to attend. [L126]

[06:48] <[nIckmenza]> We will now open the channel up for general questions. (Rev.nIckmenza 1/4/2005) [END] [L127]

Session Close: Sat Apr 15 06:48:58 2006

[09:09] <nIckmenza> Hey Hey :o) [L1]

[09:10] <nIckmenza> 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. [L2]

[09:10] <nIckmenza> I'd like to welcome you all to the Undernet Channel Service OpSchool (Part Three). [L3]

[09:10] <nIckmenza> We have a lot of very knowledgeable people there to help you. Just be patient after you ask your question :o) [L4]

[09:10] <nIckmenza> You'll hear what Undernet considers abuse, survival skills for floods and netsplits, and an all-time favorite... [L5]

[09:10] <nIckmenza> Now for the rules of the class.... [L6]

[09:10] <nIckmenza> The teaching staff is divided up alphabetically. Each assistant will answer questions for the letter group they are assigned to: A-F_Tutor handles nicks starting with A through F and so on... [L7]

[09:11] <nIckmenza> MiscTutor handles nicks beginning with numbers or characters such as ^, ], _, and so on, French is "AideTout", Spanish "YoAyudo", Romanian "EuAjut". [L8]

[09:11] <nIckmenza> If your nick falls under the letter A, please use the tutor of the first letter in your nick (ex. Ace would /msg A-F_Tutor) [L9]

[09:11] <nIckmenza> Please direct your questions by private message to the tutor who covers your name group. [L10]

[09:11] <nIckmenza> The channel is moderated (+m) and may be set to invite-only (+i) to lessen interruptions. If you get disconnected, please message a tutor to be invited back into class. [L11]

[09:11] <nIckmenza> You will not be permitted to change your nickname during this class. A ban on *!*@* prohibits nickname changes. [L12]

[09:11] <nIckmenza> Do not message the instructor - My job is to keep the lesson flowing. Remember, you have tutors to answer your questions. [L13]

[09:12] <nIckmenza> 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. [L14]

[09:12] <nIckmenza> To get rid of disruptions of people leaving or quitting, you may wish to put these messages in your status window. In mIRC, go to options, and uncheck Joins/Parts in channel, and Quits in channel. [L15]

[09:12] <nIckmenza> We will now take a brief pause in order for you to turn on your logging and locate your tutor. [ph] [L16]

[09:13] <nIckmenza> SESSION A - FLOOD PROTECTION: Flood attacks are unfortunately not a rare enough occurance on the Undernet. [L17]

[09:14] <nIckmenza> What is a flood? Flooding comes in several varieties, including: [L18]

[09:14] <nIckmenza> CHANNEL TEXT FLOODS -- (multi lines of text sent to the channel chat window) -- are usually considered floods if over about 5 lines [L19]

[09:14] <nIckmenza> NICK FLOODS -- changing nicks over and over rapidly causing the channel window to be flooded with nick change notices [L20]

[09:14] <nIckmenza> DCC FLOODS -- attempts to send rapid and massive amounts of dcc chat requests and/or files to you [L21]

[09:14] <nIckmenza> And finally CTCP FLOODS -- where a user rapidly sends ctcp info requests to you. These are usually in the form of /ping , /version , /time , etc. [L22]

[09:14] <nIckmenza> Most client programs are setup to automatically respond to such requests by sending back the requested info. Therefore, your own system rapidly overloads itself and causes you to disconnect. This is why the CTCP flood is the most troublesome. [L23]

[09:15] <nIckmenza> The other floods are annoying, but do not usually cause disconnects (with their associated loss of presence -- and therefore ops -- on your channel) [L24]

[09:15] <nIckmenza> One other type of flood is an ICMP flood... This type sends massive data packets directly to your dialer connection and ties up your connection port. Your IRC client program therefore doesn't find time to respond to server pings and eventually times out and disconnects. [L25]

[09:15] <nIckmenza> You can recognize an ICMP flood because your program will act like its locked up (no text coming in) and your modem lights will be very busy. Also, if you run a packet tracing program it can sound an alarm. [L26]

[09:15] <nIckmenza> Note: For help on protecting against and tracing recent versions of the "blue screen" attacks (muerte, winnuke), join #help or #userguide. Some of these programs send OOB (out of band) packets to freeze Win95 or NT. Also see the Microsoft homepage for approved patches. [L27]

[09:15] <nIckmenza> We'll cover what to do to defend against floods in a moment. [L28]

[09:15] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L29]

[09:16] <nIckmenza> Fortunately, every user has the tools already available to combat flooders in a responsible way. [L30]

[09:16] <nIckmenza> NEVER retaliate against a flooder by flooding back. All flooding is wrong and abuses Undernet resources. [L31]

[09:17] <nIckmenza> Here are some advice to stop flooders... [L32]

[09:17] <nIckmenza> 1. Set up an alias key to *** /silence *!*@* . When a flooder starts, just hit that alias key. It will stop all CTCP and PRIVMSG from reaching you (use /silence -*!*@* to turn off). See the documentation for your particular IRC client to learn how to set an alias [L33]

[09:17] <nIckmenza> Then you can also /ignore *!*userid@host on the offender to silence any channel flooding to you or DCC and /msg. Get their userid@host from a /whois. [L34]

[09:17] <nIckmenza> As for ICMP floods, the only defense is to log in connected to a firewall ( run by your Provider - ask them for details) , or through a shell account or telnet connection. [L35]

[09:17] <nIckmenza> These simple techniques are all any user needs to defend against most flooders. You should also set your DCC file get to "auto refuse" when you see a flood attack start. [L36]

[09:17] <nIckmenza> Hopefully you won't be subject to any flood attacks, but these tools should help protect you. [L37]

[09:18] <nIckmenza> In a moment, we'll go over how to log a flooder and report them to their Provider to request their account be suspended or removed.. [L38]

[09:18] <nIckmenza> We'll now pause briefly so you can msg your tutor if need be. [PH] [L39]

[09:19] <nIckmenza> CTCP and ICMP flooding are "denials of service" and are forbidden under internet rules (and are also felonies under U.S. law). [L40]

[09:19] <nIckmenza> It's a good idea to log your status window at all times (this is where a ctcp flood will show up). In mIRC, just type /log on in the status window. It will be saved to a file called status.log in your mIRC directory. [L41]

[09:19] <nIckmenza> When you detect a CTCP flood, you should get the /whois info on the flooder. That will include their userid@port.domain (if the user changes nicks, use /whowas within a minute to retrieve the info). [L42]

[09:19] <nIckmenza> Even when a user is logged in with a fake userid, this information can be used by their Provider to trace them and identify the real user. You will need the exact time, date and time zone of the incident also. [L43]

[09:20] <nIckmenza> You can setup a simple script to help get that info. For help with setting up scripts please join #help or #userguide. [L44]

[09:20] <nIckmenza> Email webmaster@domain or you may try to look up the abuse email Address at http://www.abuse.net/lookup.phtml and email with a short log of the flood, and the userid@port.domain and time/date information. Be sure to send the email right away, many Providers delete their own port utilization logs every 24 hours or less. [L45]

[09:20] <nIckmenza> In your e-mail, tell them that an abusive user from their site flooded you in an attempt at denial of service as indicated in the log you are including. Do not *attach* the log - copy and paste it *directly* into the body of your email. [L46]

[09:20] <nIckmenza> If the user is using a hidden host with *.users.undernet.org please report it to abuse@undernet.org . [L47]

[09:20] <nIckmenza> Tracing ICMP is a bit more involved. In windows 3.1, just enable IP tracing in winsock. The last few IPs shown in the trace from just before you got disconnected will show large packet sizes and the IP of the ICMP flooder. The problem with this, is most ICMP floods are spoofed and ISP will not act one them. [L48]

[09:20] <nIckmenza> When you get back online, try a /dns <IP> to get the domain name of the user that flooded you. (this command only works in mIRC, ask someone to do it for you if you don't have mIRC). You can also try emailing to webmaster@<IP> (example webmaster@123.456.78.10) -- just change the last set of numbers to a 10 in for the email address. [L49]

[09:21] <nIckmenza> Another way to find the domain name of the IP numbers is to use a utility program like wsPing ... you enter the IP and select lookup or trace. It will try to find the domain name and report it to you. [L50]

[09:21] <nIckmenza> Just like with the CTCP flood information needed, you will want to note the exact time and date and timezone when reporting the ICMP flood to the Provider. [L51]

[09:21] <nIckmenza> A quick sidenote... While current versions of the most popular irc clients like Mirc, Pirch, and Virc support text enhancements like color, bold, underline, and reverse video, not all irc clients do. [L52]

[09:21] <nIckmenza> In addition, abusive use of these features (intentional or unintentional) can disrupt normal channel conversation, flood yourself and/or other users, and is a waste of bandwidth. [L53]

[09:21] <nIckmenza> For these reasons we'd like to ask you to use these features sparingly. [L54]

[09:21] <nIckmenza> 2. There is another recently possiblity to avoid flood atacks over your client or ip you use.Users can now /mode +x for host hiding. This will show ident@username.users.undernet.org . ie: Nick is ident@username.users.undernet.org.You will need to be login with you registered username to X and than type /mode nickname +x . [L55]

[09:22] <nIckmenza> We'll pause briefly again now so you can /msg your tutor with any questions. [ph] [L56]

[09:23] <nIckmenza> SESSION B - NETSPLITS AND DESYNCHS: NetSplits and server Desynchs are two problems that we live with on the net. [L57]

[09:23] <nIckmenza> They can range from merely bothersome to outright trouble. So lets take a minute to review them briefly. [L58]

[09:23] <nIckmenza> Netsplits are caused when a hub gets overloaded and the routing buffers fail to handle the flow. Translation: Bad things happen, and a server disconnects from the network. [L59]

[09:24] <nIckmenza> The most common symptoms that will show up are; 1) A sudden rash of quits by a group of users ; 2) a /luser showing less the full 41 servers means that some are split. However, some servers are only connected for parts of the day, for various reasons. [L60]

[09:24] <nIckmenza> There is nothing you can do to prevent or cause a netsplit. If the split last more then a few minutes, you might want to change to another server and try to get onto the other side of the netsplit that way. [L61]

[09:24] <nIckmenza> If X is gone from your channel due to a netsplit. You will need to wait patiently for it to return [L62]

[09:24] <nIckmenza> Occassionaly, during a netsplit, servers will become desynched.. [L63]

[09:24] <nIckmenza> You can recognize a desynch by some or all of the following.. [L64]

[09:24] <nIckmenza> -- some people say they can see the topic on the channel and some can't (though there are other reasons this may happen). [L65]

[09:25] <nIckmenza> -- users without ops are able to op/deop/etc others (those "invisible" ops are on a desynched server) [L66]

[09:25] <nIckmenza> A Desynch is like a partial netsplit. The servers send incomplete (or un-time-sychronized) info to each other and get confused as to the status of user and channel modes. [L67]

[09:25] <nIckmenza> There isn't much you can do about a desynch except "ride it out" ... or you can log into the server that the desynched ops are on and get the upper hand that way. [L68]

[09:25] <nIckmenza> You can also resynch your channel by having everyone (including X) leave the channel so that it closes.. then rejoin the channel. [L69]

[09:25] <nIckmenza> Remember, commands you send thru X to op/deop, ban, etc are then sent to *all* the servers by X... therefore, that is a way to effectively override a user that is riding a netsplit and giving you problems in your channel. However, you may be lagged to X, or they may be lagged to the person trying to cause trouble. [L70]

[09:25] <nIckmenza> We'll pause briefly again now so you can /msg your tutor with any questions. [ph] [L71]

[09:26] <nIckmenza> SESSION c - NEW CSERVICE WEB SECTION: [L72]

Comenzi NickServ si ChanServ pentru DaLNet:::::::::

Comenzi NickServ

NickServ-ul va permite sa inregistrati un nick, prevenind, in acest fel, folosirea acelui nick de catre alte persoane. Daca nickul respectiv nu este folosit timp de 14 zile, el va expira.Urmatoarele comenzi va vor arata cum sa inregistrati un nick si ce puteti face in momentul in care ati inregistrat un nick, /msg NickServ comanda. Pentru mai multe informatii despre o comanda anume, folositi /msg NickServ HELP comanda.

Comenzi NickServ:

IDENTIFY Va identifica, folosind parola aleasa de dvs.

ACCESS Modifica lista acceselor autorizate.

LINK Va linkeaza un nick la un altul, deja inregistrat (foloitoare in cazul in care aveti un anume acces pe un nick, si doriti sa aveti acelasi acces si pe alte nickuri)

SET Seteaza diverse optiuni, inclusiv protectia la kill (ATENTIE, nu va protejeaza la comanda /kill ce poate fi folosita de un ircop)

DROP Renunta la un nick deja inregistrat.

RECOVER Un user care v-a luat nickul este scos de pe iRC (comanda folositoare in cazul in care v-a aflat cineva parola)

RELEASE va recuperati nickul dupa folosirea comenzii RECOVER

* Alte comenzi: UNLINK, GHOST, INFO, LIST, STATUS. IMPORTANT: Acest serviciu este oferit pentru ca userii de pe IRC sa isi poate pastra nickul dupa ce se deconecteaza, in acest fel nici un alt user nu va putea sa foloseasca un nick deja inregistrat de catre un alt user. Totodata, sinteti protejati impotriva "furarii" de nickuri sau a altor actiuni. Folosind NickServ-ul veti reduce la minim pierderea sau "furarea" de nickuri.

Comanda REGISTER:

Sintaxa: /msg nickserv REGISTER parola adresa@e-mail

Va inregistrati nickul in baza de date a NickServ-ului. O data ce nickul va este inregistrat, puteti folosi comenzile SET and ACCESS pentru a va configura setarile pentru nickul dvs., dupa cum doriti.Asigurati-va ca retineti parola pe care o folositi la inregistrare - veti avea nevoie de ea mai tirziu, atunci cind veti dori sa efectuati schimbari la nickul dvs.IMPORTANT! "FIDO", "Fido", si "fido" sint parole diferite (sau, altfel spus, parola pe care o setati este "case sensitive").

Comanda IDENTIFY:

Sintaxa: /msg nickserv IDENTIFY parola

Ii indicati NickServ-ului ca nickul pentru care folositi parola respectiva (in cazul in care este corecta) este al dvs. Multe comenzi cer identificarea personala (folosirea comenzii /msg NickServ identify parola) inainte de utilizarea lor. Parola trebuie sa fie acceasi cu cea pe care ati introdus-o in momentul in care ati inregistrat nickul.

Comanda ACCESS:

Sintaxa: /msg nickserv ACCESS ADD mask, ACCESS DEL mask, ACCESS LIST Modifica sau arata lista de accese pentru nickul dvs. Aceasta este o lista cu adrese care vor fi recunoscute automat de NickServ drept avind acces la nickul dvs. Daca vreti sa folositi nickul de la o adresa diferita, va trebui sa folositi comanda IDENTIFY pentru determina NickServ-ul sa va recunoasca.

Comanda LINK:

Sintaxa: LINK nick parola

Va linkeaza nickul cu un altul (in acest fel, nickul dvs devenind un alias al nickului respectiv). Cind executati aceasta comanda, lista de accese pentru nickul pe care il folositi este stearsa si inclocuita cu cea a nickului cu care ati fost linkat; toate mesajele nickului precedent (la care linkati noul nick) se muta automat in lista de mesaje a noului nick (aceasta poate cauza umplerea listei de mesaje, caz in care va trebui sa stergeti din mesaje,pentru a putea receptiona altele). O data ce linkul este stabilit, nickul va fi transformat in copia perfecta a celuilalt, in sensul ca va copia toate atributele si toate accesele si levelurile celuilalt. Va fi prezent in toate listele de Servicii, exceptind comenzile UNLINK si DROP, comenzi specifice NickServ-ului. De exemplu, puteti folosi acest nick pentru a citi acelasi set de "memo" (iar memo-urile celuilalt nick vin in aceeasi lista). Daca va identificati pentru un nick, automat veti fi identificat si pentru celalalt, cu care acesta este linkat.Daca celalalt nick este pe lista de accese a unui canal, atunci ambele nickuri vor beneficia de aceleasi privilegii. Pentru a putea folosi aceasta comanda, trebuie sa va identificati pentru nickul pe care il folositi (folosind IDENTIFY comanda), iar apoi trebuie sa dati o parola pentru nickul pe care doriti sa il linkati.

Comanda SET:

Sintaxa: /msg nickserv SET optiune parametri

Seteaza diferite optiuni pentru un nick. Aceste optiuni pot fi ON sau OFF:

PASSWORD Seteaza parola pentru nick

LANGUAGE Seteaza limba in care Serviciile sa va relateze despre serviciul MEMO

URL Asociaza un URL nickului dvs.

EMAIL Asociaza o adresa de E-mail nickului dvs.

KILL Schimba optiunea de kill (optiunea de kill in cazul in care cineva va foloseste nickul, si doriti sa ii dati kill prin GHOST) ON sau OFF.

SECURE Schimba optiunea de securitate ON sau OFF

PRIVATE Previne aparitia nickului dvs. la o eventuala comanda /msg NickServ LIST

HIDE Ascunde informatii despre nick

Pentru a putea folosi aceste comenzi, in primul rind trebuie sa va identificati.

Comanda RELEASE:

Sintaxa: /msg nickserv RELEASE nick [parola]

Ii indica NickServ-ului sa scoata si sa opreasca nickul dvs. (lucru cauzat de protectia automata la kill sau folosirea comenzii RECOVER. Aceasta setare este facuta "by default" sa retina nickul 1 minut inainte de a-l putea folosi; aceasta comanda executa eliberarea imediata a acestuia.Pentru a putea folosi comanda RELEASE pentru un nick, adresa dvs. din lista ce apare la /WHOIS trebuie sa fie identica cu cea care o are nickul pe lista de acces, sau trebuie sa stiti parola exacta.

Comanda DROP:

Sintaxa: /msg nickserv DROP

Va scoate nickul dvs. (inregistrat) din baza de date a NickServ-ului. Un nick la care s-a renuntat este liber de a fi inregistrat de orice alt user. Pentru a putea folosi aceasta comanda, in primul rind trebuie sa va identificati.

Comanda UNLINK:

Sintaxa: /msg nickserv UNLINK [nick pass]

Sterge un link dintre 2 nickuri. Atunci cind linkul este sters, toate flag-urile si accesele nickului precedent (la care s-a facut link-ul) sint copiate inapoi si pot fi schimbate independent de nickul care a fost linkat ulterior. Notice-urile "Memo" nu sint copiate; toate aceste notice-uri vor ramine in memoria nick-ului la care s-a facut linkul. Oferind un nick si o parola, puteti de-linka un nick inainte de a face acest lucru folosindu-va de nickul pe care doriti sa il delinkati de orice alte nickuri linkate ulterior.

Comanda GHOST:

Sintaxa: /msg nickserv GHOST nick [parola]

Determina un "ghost" care se afla pe IRC sa paraseasca serverul. Acest "ghost" este o imagine pe care o are serverul, not actually connected, o conexiune "virtuala", cauzata de faptul ca ati avut conexiunea intrerupta momentan, sau din alte motive, lucru care determina nickul dvs. sa ramina conectat, dar neutilizabil. Pentru a putea folosi comanda GHOST pentru un nick, adresa dvs. din lista ce apare la /WHOIS trebuie sa fie identica cu cea care o are nickul pe lista de acces, sau trebuie sa stiti parola exacta.

Comanda INFO:

Sintaxa: /msg nickserv INFO nick [ALL]

Arata informatii despre nickul specificat, cum ar fi: cine este proprietarul nickul, cind a fost vazut ultima oara pe iRC si de la ce adresa, precum si optiunile nickului. Daca sunteti identificat ca fiind proprietarul nickului despre care cereti informatii, si este specificata optiunea ALL, veti putea beneficia de absolut toate datele referitoare la nickul respectiv.

Comanda LIST:

Sintaxa: /msg nickserv LIST host

Listeaza toate nickurile inregistrate care se potrivesc cu hostul cerut, in formatul nick!user@host. Nickurile care au setata optiunea PRIVATE nu vor fi aratate.

Comanda STATUS:

Sintaxa: /msg nickserv STATUS nick

Vi se ofera o anumita informatie despre nickul respectiv. Raspunsul este de urmatoarea forma:

nickname status-cod

unde nickul este cel specificat in comanda, iar status-cod este unul din urmatoarele:

0 - userul nu este on-line sau nickul nu este inregistrat

1 - userul nu este recunoscut ca fiind proprietarul nickul respectiv (identificat prin /msg nickserv identify parola)

2 - userul este recunoscut ca fiind proprietarul nickului respectiv gratie hostului sau, prezent in lista de acces a nickului respectiv

3 - userul este recunoscut ca fiind proprietarul nickului respectiv, fiind identificat prin parola (/msg nickserv identify parola).Folosind aceasta comanda, puteti afla informatii de pina la 16 nickuri. Celelalte vor fi ignorate de sistem. Nu este generat nici un mesaj de eroare daca nu este specificat un nick.

Comanda PASSWORD:

Sintaxa: /msg nickserv SET PASSWORD parola-noua

Puteti schimba parola actuala a nickului, dupa ce va identificati ca fiind proprietarul sau (/msg nickserv identify parola).

Comanda LANGUAGE:

Sintaxa: SET LANGUAGE cod

Schimba limba pe care o folosesc Serviciile cind va trimit un anumit mesaj (de exemplu, cind va raspund la o comanda pe care le-ati trimis-o). Codul trebuie ales din urmatoarele:

1) Engleza

2) Italiana

3) $BF|K\8l!J(BJIS$B%3!<%I!K(B (Japoneza / codata prin metoda JIS)

4) AIŒÎ›Î¬Îˆi!EEUCY3!1YÎ™!Î› (Japoneza / codata prin metoda EUC)

5) .IŠ.{OeÂiSJISfRÂ[fhÂj (Japoneza / codata prin metoda SJIS)

6) Portugheza

7) Spaniola

8) Turca

Comanda URL:

Sintaxa: /msg nickserv SET URL url

Asociaza un URL cu nickul dvs. Acest URL va fi afisat ori de cite ori cineva va cere informatii despre nickul dvs., folosind comanda INFO.

Comanda EMAIL:

Sintaxa: /msg nickserv SET EMAIL e-mail

Ii asociaza nickului dvs. adresa de email specificata. Aceasta adresa va aparea ori de cite ori cineva va cere informatii despre nickul dvs.

Comanda KILL:

Sintaxa: /msg nickserv SET KILL {ON | QUICK | IMMED | OFF}

Schimba optiunea de "protected kill" ON sau OFF. Cind protectia are activata optiunea ON, atunci cind orice alt user care incearca sa va foloseasca nickul, in afara dvs., va avea 1 minut la dispozitie sa isi schimbe nickul, sau sa ofere parola corecta pentru el, timp dupa care, in cazul in care nu isi schimba nickul sau nu ofera parola corecta, va fi automat scos de pe Irc de catre NickServ. Daca aveti selectata optiunea QUICK, in loc de un minut, userul va avea la dispozitie numai 20 de secunde. Daca selectati opiunea IMMED, userul va fi eliminat instantaneu, fara sa fie avertizat, in prealabil; va rugam sa nu folositi aceasta comanda decit atunci cind considerati ABSOLUT necesara folosirea ei.

Comanda SECURE:

Sintaxa: /msg nickserv SET SECURE {ON | OFF}

Aceasta comanda ii indica NickServului ca trebuie sa activeze optiunile de securitate ON sau OFF pentru nickul dvs. Cind optiunea este SETATA, va trebuie sa introduceti parola nickului pentru a fi recunoscut ca fiind proprietar al acesuia, chiar daca hostul dvs. se afla pe lista de acces a nickului. In orice caz, daca sinteti pe lista de acces, NickServ-ul nu va va elimina de pe Irc exceptind cazul in care nu s-a folosit optiunea "kill".

Comanda PRIVATE:

Sintaxa: /msg nickserv SET PRIVATE {ON | OFF}

Ii indica NickServ-ului sa seteze optiunea de PRIVATE on or off pentru nickul dvs. Cind aceasta optiune este setata, nickul dvs nu va apare in lista oferita de nickserv la o eventuala comanda /msg NickServ LIST. (Oricum, daca cineva va stie nickul, poate obtine aceasta informatie (daca sinteti on-line sau nu), folosind comanda INFO.)

Comanda HIDE:

Sintaxa: /msg nickserv SET HIDE {EMAIL | USERMASK | QUIT} {ON | OFF}

Previne afisarea de date despre nickul dvs. atunci cind cineva foloseste comanda NickServ INFO pentrul nickul dvs. Va puteti ascunde adresa de email (EMAIL), ultima oara cind ati fost vazut si de la ce adresa ati fost conectat [user@host] (USERMASK), precum si mesajul de quit pe care l-ati avut (QUIT). Al doilea grup de parametri indica daca aceste optiuni sa fie setate ON (informatiile sa fie aratate) sau OFF (sa nu indice nici o informatie).

Comenzi MemoServ

Comanda SEND:

Sintaxa: /msg memoserv SEND nick mesaj

Puteti lasa mesaj chiar daca persoana respectiva nu este on-line in acel moment. Persoana careia-i trimiteti mesaj, trebuie sa aiba nick-ul inregistrat.

Comanda LIST:

Sintaxa: /msg memoserv list {new}

Iti listeaza toate mesajele tale.

Comanda READ:

Sintaxa: /msg memoserv read {last | new | 1 }

Puteti citii mesajele

Exemplu:

/msg memoserv read last

Va afiseaza ultimul mesaj primit.

/msg memoserv read 4

Va afiseaja mesajul numarul 4.

Comanda DEL:

Sintaxa: /msg memoserv del

Sterge mesajul.

Exemplu:

/msg memoserv del 4

Sterge mesajul numarul 4.

* Atentie: Numarul maxim pe mesaje pe care le puteti primii este de 20.

**********************************************************

Comenzi ChanServ

IDENTIFY Va identifica pe dvs. cu parola.

SET Seteaza optiunile canalului.

ACCESS Modifica lista userilor care au acces la ChanServ.

LEVELS Redefineste lista de accese a unui canal.

AKICK Mentine lista de autokick-uri.

DROP Renuntati la inregistrarea unui canal.

* Alte comenzi: INFO, LIST, INVITE, OP, DEOP, UNBAN, CLEAR ATENTIE! In cazul in care un canal nu este folosit timp de 14 zile (aceasta presupunind ca nici un user cu acces nu intra in canalul respectiv in aceasta perioada), inregistrarea va fi automat anulata.

Comanda REGISTER:

Sintaxa: /msg chanserv REGISTER #canal parola descriere

Inregistreaza un canal in baza de date a ChanServ-ului. Pentru a putea folosi aceasta comanda, trebuie, in primul rind, sa fiti operator pe canalul pe care doriti sa il inregistrati. Parola este folosita impreuna cu comanda IDENTIFY, lucru care va va permite sa efectuati schimbari ulterioare in canal. Ultimul parametru, care trebuie inclus, este descrierea generala a canalului.Atunci cind inregistrati un canal, sinteti automat inregistrat ca "founder" al acestui canal.Founder-ul unui canal are posibilitatea de a schimba toate setarile pentru canalul respectiv;ChanServ-ul va acorda automat founder-ului privilegii de operator de canal atunci cind acesta intra in canalul respectiv. Pentru alte informatii, a se vedea comanda ACCESS.

Comanda IDENTIFY:

Sintaxa: /msg chanserv IDENTIFY #canal parola

In momentul in care executati aceasta comanda, sinteti identificat la Chanserv drept founderul acelui canal. Multe comenzi pentru Chanserv necesita identificarea de mai sus pentru a putea fi executate. Totodata, parola trebuie sa fie identica cu cea care a fost folosita la inregistrarea canalului.

Comanda SET:

Sintaxa: /msg chanserv SET #canal optiuni parametri

Aceasta comanda ii permite founder-ului unui canal sa seteze diferite optiuni sau sa schimbe anumite informatii. Founder-ul trebuie sa foloseasca comanda IDENTIFY inainte de a folosi comanda SET.

Optiuni ale comenzii SET:

FOUNDER Seteaza founder-ul canalului respectiv

SUCCESSOR Seteaza un succesor pentru canalul respectiv

PASSWORD Seteaza parola canalului

DESC Seteaza o descriere a canalului

URL Ii asociaza un URL canalului

EMAIL Ii asociaza canalului o adresa de E-mail.

ENTRYMSG Seteaza un mesaj care le apare userilor in momentul in care acestia intra pe canalul respectiv.

TOPIC Seteaza topicul canalului.

KEEPTOPIC Mentine topicul atunci cind pe canal nu se afla nici un user.

TOPICLOCK Topicul poate fi schimbat NUMAI cu comanda SET TOPIC.

MLOCK Seteaza modul "lock" on sau off

PRIVATE Ascunde canalul, astfel incit la comanda LIST numele acestuia sa nu

apara in lista canalelor de pe server(e).

RESTRICTED Restringe accesul userilor pe canal

SECURE Activeaza optiunile de securitate maxima ale ChanServ-ului.

SECUREOPS Seteaza un control strict al celor care se opeaza (nu se poate acorda +o celor care nu sint trecuti in lista de accese a Chanserv-ului)

LEAVEOPS Nu se pot de-opa userii, exceptind cazul cind se foloseste comanda DEOP.

OPNOTICE Se trimit notice-uri in momentul in care sint folosite comenzile OP/DEOP.

Comanda ACCESS:

Sintaxa : /msg chanserv ACCESS #canal ADD nick level

ACCESS #canal DEL {nick | entry-num | list}

ACCESS #canal LIST [mask | list]

Mentine lista de accese pentru un canal. Lista de accese mentioneza ce useri au permisiunea sa fie +o sau au acces la comenzile ChanServ-ului, pe acel canal.Level-ul diferit va da diverse posibilitati si optiuni de acces pe un canal si la ChanServ. Comanda /msg ChanServ HELP ACCESS LEVELS va poate oferi pentru mai multe informatii. Orice nick ce nu se afla pe pe lista de acces are level 0.Comanda ACCESS ADD adauga nickuri in lista de accese, cu un level dorit de cel care da acces; daca nickul respectiv (caruia i se da acces)este deja prezent pe lista, level-ul sau este schimbat cu level-ul specificat in comanda.Level-ul specificat trebuie sa fie mai mic decit al celui care acorda acces, iar daca nick-ul este deja pe lista de accese,level-ul care se acorda trebuie sa fie mai mic decit al celui care da acces.Comanda ACCESS DEL sterge din lista de accese un nick, care se specifica.Daca este specificat un numar din lista, acel numar este sters din lista. (Vedeti exemplul LIST de mai sus.)Comanda ACCESS LIST arata lista acceselor de pe o camera.Daca este specificat si un mask, numai acele nickuri cu mask-ul respectiv vor fi listate.Daca se specifica si un anumit numar, numai nickurile care se afla in lista la numerele respective vor fi listate; de exemplu: /msg chanserv ACCESS #canal LIST 2-5,7-9 Listeaza pe cei care sint in lista de acces de la nr. 2 la nr. 5 si de la nr. 7 la nr. 9

Comanda LEVELS:

Sintaxa: /msg chanserv LEVELS #canal SET type level

LEVELS #canal {DIS | DISABLE} type

LEVELS #canal LIST

LEVELS #canal RESET

Comanda LEVELS permite controlul level-urilor folosite pentru acel canal. Folosind aceasta comanda, puteti defini lista de accese ceruta pentru cele mai multe comenzi ale ChanServului.(Comenzile SET FOUNDER and SET PASSWORD, la fel ca si aceasta comanda, nu pot fi executate decit de foundr-ul unui canal.)Comanda LEVELS SET permite ca lista de accese (levele, totodata) sa fie schimbata, pentru a avea acces la o o functie sau un grup de functii.Comanda LEVELS DISABLE (sau DIS, mai pe scurt) dezactiveaza tot ce este legat de levels (automatic features) si blocheaza accesul la functiile unui canal (numai founderul poate avea acces la aceste functii).Comanda LEVELS LIST arata levelurile cerute pentru a putea executa o functie sau un grup de functii.Comanda LEVELS RESET reseteaza nivelurile la modul "default" al unui canal nou creat.Pentru o lista a avantajelor si a functiilor ce pot fi setate, folositi comanda HELP LEVELS DESC.

Comanda AKICK:

Sintaxa: /msg chanserv AKICK #canal ADD mask [motiv]

AKICK #canal DEL mask

AKICK #canal LIST [mask]

AKICK #canal ENFORCE Mentine lista de AutoKick-uri list valabila pentru un canal. Daca un user care se afla pe lista de AutoKick-uri incearca sa intre in acel canal, ChanServ-ul il va bana si ii va da kick.Comanda AKICK ADD adaugata unui nick sau unui host va introduce nickul respectiv pe lista de AutoKick-uri.Daca un motiv a fost adaugat in momentul adaugarii acelui user pe lista, acel motiv va aparea atunci cind userul respectiv va primi kick; daca nu este adaugat nici un motiv, mesajul "by default" este "You have been banned from the channel".Comanda AKICK DEL sterge un nick sau un host de pe lista cu AutoKick-uri.In nici un caz nu poate ridica un ban pus prin AutoKick. Banurile vor trebui scoase de un operator.Comanda AKICK LIST arata lista de AutoKick-uri, sau, numai acele AutoKick-uri care au acelasi host cu cel cautat.Comanda AKICK ENFORCE determina ChanServ-ul sa dea AKICK tuturor acelor useri care au hostul specificat in comanda AKICK.

Comanda DROP:

Sintaxa: /msg chanserv DROP #canal

Se renunta la un canal deja inregistrat. Poate fi folosita doar de un founder de canal, care trebuie sa fi folosit in prelabil comanda IDENTIFY.

Comanda INFO:

Sintaxa: /msg chanserv INFO #canal [ALL]

Listeaza informatii despre canalul dorit, inclusiv numele founder-ului, data inregistrarii, descriere, si mode lock, daca exista vreunul. Daca sinteti identificat ca founder al canalului, va vor fi afisate TOATE informatiile referitoare la acel canal, plus mesajul care le apare tuturor userilor cind cind intra in canalul respectiv, precum si succesorul.

Comanda LIST:

Sintaxa: LIST

Afiseaza o lista cu toate canalele existente pe server in momentul in care se da comanda, exceptindu-le pe cele care au setate optiunea PRIVATE.

Comanda INVITE:

Sintaxa: INVITE #canal

Folosind aceasta comanda, ChanServ-ul va invita in canalul specificat. Aceasta comanda este accesibila numai pentru canalele unde aveti acces mai mare decit 0.

Comanda OP:

Sintaxa: /msg chanserv OP #canal nick

Seteaza modul +o(opeaza) pentru nickul selectat, pe un canal.

Comanda DEOP:

Sintaxa: /msg chanserv DEOP #canal nick

Seteaza modul -o(deopeaza) pentru nickul selectat, pe un canal.

Comanda UNBAN:

Sintaxa: /msg chanserv UNBAN #canal

Aceasta comanda ii indica ChanServ-ului sa scoata banurile de pe un anumit canal. Pentru a-i putea da Chanserv-ului aceasta comanda, accesul dvs. trebuie sa fie mai mare de 0.

Comanda CLEAR:

Sintaxa : CLEAR #canal x

Aceasta comanda ii indica ChanServ-ului sa scoata anumite moduri sau setari ale canalului. x poate avea urmatoarele valori:

MODES Scoate toate modurile existente pe un canal (i.e. aceastea pot fi i,k,l,m,n,p,s,t).

BANS Scoate toata banurile de pe canal.

OPS Scoate modul +o de la toti operatorii de canal.

VOICES Scoate modul +v de la toti cei care au acest mod setat.

USERS Scoate (prin kick-uri) toti userii de pe un canal.

Accesul dvs. trebuie sa fie minim 10 pentru a putea folosi aceasta comanda.

Comanda FOUNDER:

Sintaxa: /msg chanserv SET #canal FOUNDER nick

Schimba founderul unui canal. Noul nick trebuie sa fie inregistrat. Aceasta comanda poate fi folosita doar de actualul founder al canalului.

Comanda SUCCESOR:

Sintaxa: /msg chanserv SET #canal SUCCESSOR nick

Schimba succesorul unui canal. Daca nickul founder-ului expira, sau i se da "drop" atit timp cit canalul este inca inregistrat, succesorul va deveni noul founder al canalului. Oricum, daca succesorul are deja prea multe inregistrate (1), the canalul va fi automat deinregistrat, daca succesorul nu a fost desemnat.Noul nick (cel al succesorului) trebuie sa fie unul inregistrat.

Comanda PASSWORD:

Sintaxa: /msg chanserv SET #canal PASSWORD parola

Seteaza parola folosita pentru identificarea founderului unui canal.

Comanda DESC:

Sintaxa: /msg chanserv SET #canal DESC descriere

Seteaza descrierea unui canal, descriere ce apare in dreptul canalului respectiv in momentul in care se efectueaza comanda LIST sau INFO.

Comanda URL:

Sintaxa: /msg chanserv SET #canal URL [adresa]

Aceasta comanda ii asociaza unui canal un URL. Acest URL va fi afisat in orice moment in care cineva va cere informatii despre acel canal folosind comanda INFO. Daca nici un URL nu este specificat, aceasta comanda sterge orice URL specificat pentru acel canal.

Comanda EMAIL:

Sintaxa: /msg chanserv SET #canal EMAIL [adresa]

Aceasta comanda ii asociaza unui canal o adresa de E-mail. Adresa va fi afisata in orice moment in care cineva va cere informatii despre acel canal, folosind comanda INFO. Daca nu este specificata nici o adresa de E-mail, aceasta comanda sterge orice adresa de E-mail specificata pentru acel canal.

Comanda ENTRYMSG:

Sintaxa: /msg chanserv SET #canal ENTRYMSG [mesaj]

Seteaza mesajul ce le va fi trimis tuturor userilor cind intra intr-un canal, sub forma de "notice". Daca nu este specificat nici un mesaj, userii nu vor receptiona nici un "notice" cind vor intra in acel canal.

Comanda TOPIC:

Sintaxa: /msg chanserv SET #canal TOPIC text

Aceasta comanda ii indica ChanServ-ului sa seteze topicul unui canal. Totodata, aceasta comanda este extrem de folositoare in asociere cu comanda SET TOPICLOCK.

Comanda KEEPTOPIC:

Sintaxa: /msg chanserv SET #canal KEEPTOPIC {ON | OFF}

Aceasta comanda seteaza modul "lock" sau "unlock" pentru un topic, pe un canal specificat. Daca este setata optiunea pentru retinerea topicului, acesta va fi retinut de ChanServ de fiecare data cind ultimul user paraseste canalul, si va fi retinuta pentru urmatoarea data cind se creeaza un canal cu acelasi nume.

Comanda TOPICLOCK:

Sintaxa: /msg chanserv SET #canal TOPICLOCK {ON | OFF}

Seteaza optiunea "lock" sau "unlock" pentru un topic, pe un canal. Atunci cind topicul este setat "locked", ChanServ-ul nu va permite ca topicul sa fie schimbat, exceptind cazul cind se foloseste comanda SET TOPIC.

Comanda MLOCK:

Sintaxa: /msg chanserv SET #canal MLOCK modes

Seteaza anumite moduri, ce sint specificate, lock sau unlock. ChanServ-ul va permite sa definiti anumite moduri pentru a fi intotdeauna on (sau off). Aceste moduri, ce pot fi setate pe modul "on" (sau locked) sint i, k, l, m, n, p, s, and t. Fiecare din aceste moduri poate fi setat "locked on", "locked off", sau "not locked". Aceasta comanda se foloseste exact ca si comanda /MODE command; in acest fel, modurile urmate de "+" sunt setate "locked on", iar modurile urmate de "-" sint setate "locked off". ATENTIE: Daca setati anumite moduri, precum in al doilea exemplu de mai jos, trebuie, de asemenea, sa folositi optiunea RESTRICTED pentru canal; in caz contrat, oricine prezent in canal in momentul in care setati acest mod va putea vedea codul setat pentru modul "k"! Exemple:

/msg chanserv SET #canal MLOCK +nt-iklps

Modurile n si t sunt "on", iar modurile i, k, l, p, si s sint "off". Modul m este lasat la libera alegere, sa fie "on" sau "off".

/msg chanserv SET #canal MLOCK +knst-ilmp codul-meu

Modurile k, n, s, si t sint "on", iar modurile i, l, m, si p sint "off". Totodata, codul canalului (key) este "codul-meu".

/msg chanserv SET #canal MLOCK +

Scoate toate modurile setate de pe o camera; toate modurile unui canal pot fi "on" sau "off".

Comanda RESTRICTED:

Sintaxa: /msg chanserv SET #canal RESTRICTED {ON | OFF}

Seteaza optiunea "acces restrins" pentru un canal. Cind acest acces este setat, userii care,in mod normal nu ar trebui sa aiba privilegiul de a fi moderatori (userii cu acces negativ sau, cind optiunea "secure ops" este setata, userii care nu se afla pe lista de accese) vor primi kick si ban.

Comanda SECURE:

Sintaxa: /msg chanserv SET #canal SECURE {ON | OFF}

Seteaza sau dezactiveaza optiunile de securitate ale ChanServ-ului pentru un canal. Atunci cind optiunea SECURE este setata, numai userii care au nicuri inregistrare si sunt identificati la Nickserv vor avea acces pe canal, acest lucru fiind posibil prin prezenta lor pe lista de acces.

Comanda SECUREOPS:

Sintaxa: /msg chanserv SET #canal SECUREOPS {ON | OFF}

Seteaza sau dezactiveaza optiunea "secure ops" pentru un canal. Atunci cind aceasta optiune este setata, cei care nu se afla pe lista de useri nu vor putea sa fie moderatori de canal (ChanServ-ul nu va permite ca un moderator sa seteze modul +o pentru acesti useri).

Comanda LEAVEOPS:

Sintaxa: /msg chanserv SET #canal LEAVEOPS {ON | OFF}

Seteaza sau dezactiveaza aceasr optiune pentru un canal. Cind este setata, ChanServ-ul nu va de-opa un user in acel canal, in afara de cazul cind se va folosi comanda DEOP.

Comanda OPNOTICE:

Sintaxa: /msg chanserv SET #canal OPNOTICE {ON | OFF}

Seteaza sau dezactiveaza optiunea de a trimite notice-uri moderatorilor unui canal, ori de cite ori este folosita comanda "OP" sau "DEOP" de catre cei care au acces minim 5 la ChanServ.

E-mail me at::::::

Mehedinti@4x.ro

Gary@Mehedinti.org

Gary@K.Ro

IRC@K.RO

and others...

O urare d3l@ Gary pt cei care intra pe websitul meu:

Sa iubesti, de parca nimeni nu te-ar fi suparat !

Sa lucrezi, de parca nu ai avea nevoie de bani !

Sa dansezi, de parca nimeni nu s-ar uita la tine !

Sa canti, de parca nimeni nu te-ar auzi !

Sa traiesti, de parca ai trai in Rai !

SA AI O ZI FRUMOASA !!!

[09:27] <nIckmenza> The new CService web section: "Complaints" is located at http://cservice.undernet.org/live . [L73]

[09:27] <nIckmenza> Complaint Website was designed to assist users to the maximum and lessen the waiting period.It is user friendly so don't be afraid :o) [L74]

[09:27] <nIckmenza> You need to be logged into your Username (for better and quicker result) or simply having an e-mail *that actually works* would be sufficient. [L75]

[09:27] <nIckmenza> Complaint is usually replied between 3-5 days. [L76]

[09:27] <nIckmenza> You may post a complaint regarding all issues - from username being suspended to abuse report with (preferably) or without logs (this will just takes longer). [L77]

[09:27] <nIckmenza> Steps on complaint: [L78]

[09:28] <nIckmenza> * Once you submitted a complaint, you will be issued a ticket number + link sent to your e-mail (if the e-mail you have on records doesn't work, you may specify which e-mail you currently have that can be used). [L79]

[09:28] <nIckmenza> * Then you must click the link sent to your e-mail inbox to activate the complaint ticket. Failure to do this will result on the complaint not being process and deleted. [L80]

[09:28] <nIckmenza> * Once this is done, you have nothing to do beside wait until an Admin review the complaint. [L81]

[09:28] <nIckmenza> You can always check on the progress of the complaint with the ticket number you have by going to one of the 2 urls you have in the email sent by CService when you confirmed the complaint.One url is for visit the status,the other one is to close the ticket if your problem is solved. [L82]

[09:28] <nIckmenza> Once the matter is resolved, you will be e-mailed regarding the complaint and the result. Then only the complaint ticket are closed by a CService Admin. [L83]

[09:28] <nIckmenza> We'll pause briefly now so you can submit your "complaints" to the tutor assigned ;o) [ph] [L84]

[09:30] <nIckmenza> SESSION D - LATEST NEWS ON UNDERNET: [L85]

[09:30] <nIckmenza> The Undernet Coders have been working hard and steady on the improvement of Undernet servers.This brings new features for users. [L86]

[09:30] <nIckmenza> One of those is the hide host option which was explained few minutes ago.But there are few more options :o) [L87]

[09:30] <nIckmenza> * Users can now set +r on any channel they have ops in. If a channel is +r then only users who are logged into X (have a username) can join the channel, this can help a lot with flood nets. This is not restricted to registered channels, this feature is for all channels. [L88]

[09:31] <nIckmenza> * Users can now be invited into any channel by an chanop they wouldn't normally be able to join because they are banned, the channel is keyed, invite only or registered users only. [L89]

[09:31] <nIckmenza> * Users can now see who users are (the user's username) when they /whois another user who is logged into an X username. [L90]

[09:31] <nIckmenza> * Your server will remember who you are logged in as, and will automatically log you in to X again after net splits so you don't have to log in again. [L91]

[09:31] <nIckmenza> We'll pause briefly again now so you can /msg your tutor with any questions. [ph] [L92]

[09:33] <nIckmenza> I'll save our other topics for next time.. when you can join us for OpSchool Part 1: "Username & Channel Registrations". [L93]

[09:33] <nIckmenza> This script was made possible with the help of quite a few people. I'd like to thank the originators.. Pucker, MatthewA, D-in-Tx, Manning, Teal, SeKs, Coccyx, BitBT, Rotundo, Cyke, and more recently, DrCkTaiL, Lordluke, MarkT, Mikey-, Robinb, Signe and DaveB ..and who ever else that I forgot.:o) [L94]

[09:33] <nIckmenza> I'd also like to thank all the people who volunteer their time to help out bringing up and presenting the classes.Without you it just wouldn't be possible to do this! Thanks :o) [L95]

[09:33] <nIckmenza> Let's not forget past leader of OpSchool - Isaiah (CService Admin)...Rest in peace dear friend... [L96]

[09:33] <nIckmenza> If you ever have any questions about the material you see here in Opschool or about the Undernet in general...please join #cservice. Cservice volunteers will be glad to try to help you with your problem...or if they can't they'll do their best to tell you where to go to find the help you need. [L97]

[09:34] <nIckmenza> Our site can be found at http://cservice.undernet.org/main/opschool (you'll find more in a few days there:o) [L98]

[09:34] <nIckmenza> I've really enjoyed teaching here today...I hope you have enjoyed being here and have learned something that will make your time on the Undernet more enjoyable...I want to thank you all for listening so politely :o) [L99]

[09:34] <nIckmenza> You now have all the know-how you need to help yourself and others make the Undernet a friendlier place. I hope you will try out what you've learned and share with others. [L100]

[09:34] <nIckmenza> This concludes our class, thank you for taking the time to attend. [L101]

[09:34] <nIckmenza> We will now open the channel up for general questions. (Rev.nIckmenza 1/04/2006) [END] [L102]

NeStart of #Opschool buffer: Fri Apr 21 17:23:41 2006

[16:32] <nIckmenza> Hello again :o) [L1]

[16:32] <nIckmenza> 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. [L2]

[16:32] <nIckmenza> I'd like to welcome you all to the Undernet Channel Service OpSchool (Part Two). [L3]

[16:32] <nIckmenza> We have a lot of very knowledgeable people there to help you. Just be patient after you ask your question. :) [L4]

[16:32] <nIckmenza> Today's session will cover how to harness the powerful commands provided in X. [L5]

[16:33] <nIckmenza> Now for the rules of the class.... [L6]

[16:33] <nIckmenza> The teaching staff is divided up alphabetically. Each assistant will answer questions for the letter group they are assigned to: A-F_Tutor handles nicks starting with A through F and so on... [L7]

[16:33] <nIckmenza> MiscTutor handles nicks beginning with numbers or characters such as ^, ], _, and so on, French is "AideTout", Spanish "YoAyudo", Romanian "EuAjut". [L8]

[16:33] <nIckmenza> If your nick falls under the letter A, please use the tutor of the first letter in your nick (ex. Ace would /msg A-F_Tutor) [L9]

[16:33] <nIckmenza> Please direct your questions by private message to the tutor who covers your name group. [L10]

[16:33] <nIckmenza> The channel is moderated (+m) and may be set to invite-only (+i) to lessen interruptions. If you get disconnected, please message a tutor to be invited back into class. [L11]

[16:34] <nIckmenza> You will not be permitted to change your nickname during this class. A ban on *!*@* prohibits nickname changes. [L12]

[16:34] <nIckmenza> Do not message the instructor - My job is to keep the lesson flowing. Remember, you have tutors to answer your questions. [L13]

[16:34] <nIckmenza> 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. [L14]

[16:34] <nIckmenza> To get rid of disruptions of people leaving or quitting, you may wish to put these messages in your status window. In mIRC, go to options, and uncheck Joins/Parts in channel, and Quits in channel. [L15]

[16:34] <nIckmenza> We will now take a brief pause in order for you to turn on your logging and locate your tutor. [ph] [L16]

[16:38] <nIckmenza> SESSION A - SCOPE AND DEFINITIONS: Channel Service Committee - We provide registration of channels on the Undernet and the service X to hold the channels. [L17]

[16:38] <nIckmenza> This registration provides a channel manager with a flexible tool for managing the channel and handling channel affairs. [L18]

[16:39] <nIckmenza> X is a specialized server often referred to as a bot which actually hold the channel open and allow for control. [L19]

[16:39] <nIckmenza> A special note, when giving the commands, I will use < > for required elements and [ ] for optional elements. [L20]

[16:39] <nIckmenza> Now for a few definitions: [L21]

[16:39] <nIckmenza> The Manager - The user who applies for and owns the channel. [L22]

[16:39] <nIckmenza> Channel Operators - Users given the privilege of being an operator by the manager. The manager grants them access to the bot. [L23]

[16:39] <nIckmenza> Userlist - The database in X that holds the information about the channel users added to the bot. [L24]

[16:40] <nIckmenza> CService Operator - An IRC user experienced in the X commands and is an authorized member of the CService Team [L25]

[16:40] <nIckmenza> CService Helper - An experienced CService Operator who has been asked to assist CService in providing user support. [L26]

[16:40] <nIckmenza> CService Administrator - A very experienced CService Helper who manages CService responsibilities. [L27]

[16:40] <nIckmenza> Please keep in mind that all CService personnel volunteer their time, effort, and resources to make CService as best as it possibly can be. [L28]

[16:40] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L29]

[16:43] <nIckmenza> SESSION B - CHANNEL MANAGEMENT: Now...for the instructions on channel management. [L30]

[16:44] <nIckmenza> As the channel manager YOU are ultimately responsible for what goes on in your channel ** whether you are there or not **. [L31]

[16:44] <nIckmenza> Your primary duty is to ensure all the users on your channel understand and are willing to comply with the CService guidelines. [L32]

[16:44] <nIckmenza> You are also responsible for maintaining the userlist for your channel. This includes making sure your ops login to their access when in the channel and ensuring that the userlist is up-to-date and active. [L33]

[16:44] <nIckmenza> Finally you must login to your 500 access at least once every 21 days. [L34]

[16:44] <nIckmenza> Changes to managers emails or forgotten password should be handled via the website or via one of our CService mailinglists: [L35]

[16:44] <nIckmenza> * X@undernet.org for EMail Changes if the username owner can't access email address on record anymore. [L36]

[16:45] <nIckmenza> * usernames@undernet.org for username unsuspensions if the username was suspended previously by a CService Administrator for being hacked/abused or /join #usernames and ask there. [L37]

[16:45] <nIckmenza> * Object@undernet.org for other issues that cannot be handled via X@undernet.org. [L38]

[16:45] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L39]

[16:46] <nIckmenza> SESSION C - LEVEL 0 COMMANDS: Now we'll cover user levels and commands: [L40]

[16:47] <nIckmenza> These apply to X and to any users that are added to the database in the bots. [L41]

[16:47] <nIckmenza> The levels for channel personnel range from 0 - 500 [L42]

[16:47] <nIckmenza> Level 0 -- These commands do not affect the operation of the channel, and are mainly used for information. The commands are: access, chaninfo, help, lbanlist, login, motd, pass, showcommands, showignore,and verify . [L43]

[16:47] <nIckmenza> /msg X access #channel <search string> to find a users access level on the channel. This tells you their username, 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 username -modif [L44]

[16:47] <nIckmenza> A note here, the search string can be anything from a nick to a user@host to a wildcard (*). It is just that, telling X what to look for. [L45]

[16:47] <nIckmenza> /msg X lbanlist #channel <search string> shows the list of bans set through X. [L46]

[16:48] <nIckmenza> In order to do the banlist or lbanlist commands, you MUST be in the channel. [L47]

[16:48] <nIckmenza> If there are more than 15 users in the Lbanlist, you will get a message from X telling you there are too many entries to display. You will need to fire up your web browser and visit the CService website at http://cservice.undernet.org to see the full list. [L48]

[16:48] <nIckmenza> Remember, the two ban lists are separate. The channel ban list holds 45 bans. They are set by /mode #channel +b *!*userid@host. The Lbanlist (bot list) is unlimited. [L49]

[16:48] <nIckmenza> 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 2400 hours (100 Days). For important bans, put them in both lists. [L50]

[16:48] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L51]

[16:49] <nIckmenza> /msg X chaninfo #channel-name gives information such as the channel manager's username as well as the Channel Description and URL. [L52]

[16:49] <nIckmenza> /msg X showcommands #channel-name will show you which commands you have available to you on that channel. These depend on the level you have in X for that channel only. [L53]

[16:49] <nIckmenza> /msg X help command will explain the usage of that command. Use this to see command syntax and a wealth of helpful reminders. [L54]

[16:49] <nIckmenza> /msg X motd displays X's message of the day. [L55]

[16:50] <nIckmenza> /msg X showignore shows a list of users X is ignoring *note* if you are on the ignore list, you will not be able to see this information. If you feel that you are, ask someone to check for you. [L56]

[16:50] <nIckmenza> To authenticate yourself with X , use /msg X@channels.undernet.org LOGIN <username> <password> [L57]

[16:50] <nIckmenza> To change your password for that channel use you can no longer use X. For better security it can only be changed on the website now. [L58]

[16:50] <nIckmenza> You will need to go to http://cservice.undernet.org/live/ and login with your current username and password. Then select the "New Password" link on the left and follow the instructions. [L59]

[16:50] <nIckmenza> Lang sets the default language for the individual user. Available languages codes: dk - Danish, en - English, es - Spanish, fr - French, hu - Hungarian, it - Italian, no - Norwegian, ro - Romanian, tr - Turkish, ar - Arabic, ca - Catalan, de - German, ea - Easter, gr - Greek, ha - halloween, mk - macedonian, nl - Dutch, pt - Portuguese, sv - Svenska. Lang is a level 1 command and can be set by any user at any userlevel with /msg X set lang <lang_code> [L60]

[16:50] <nIckmenza> The verify command is used to determine if a user is an authenticated IRC Operator, CService Official, 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 and pretends it is from CService, then be sure to stop by #cservice and ask about them. [L61]

[16:51] <nIckmenza> Verify also shows the username of the person . [L62]

[16:51] <nIckmenza> This is One of the newest command /msg x set noadduser On/Off - when that command is ON, an username won't be able to be added to any channel. This prevents users adding you to other channels you don't wish to be added. If you want to be added on the channel just turn it OFF and you will be added. [L63]

[16:51] <nIckmenza> /msg x status #channel gives the user information about the channel, such as the number of users, Floating limit settings, Default flags, and the people authenticated in the channel. This command is a Level 1 command. [L64]

[16:51] <nIckmenza> /msg X banlist #channel <search string> shows you the channel banlist. This is also a level 1 command. [L65]

[16:51] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L66]

[16:53] <nIckmenza> SESSION D - LEVEL 25 THROUGH 100 COMMANDS: The next level where new commands are introduced is level 25. [L67]

[16:54] <nIckmenza> /msg x voice #channel <nick1> <nick2> <nick3> and so on... This makes X Give +v (or voice) to the nicknames specified. Just typing /msg x voice #channel will have X voice you. [L68]

[16:54] <nIckmenza> /msg x devoice #channel <nick1> <nick2> <nick3> and so on... This has X DEvoice you, or -v on said channel. As above, just typing the command without a nickname, will have X devoice you. [L69]

[16:54] <nIckmenza> 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. [L70]

[16:54] <nIckmenza> /msg X kick #channel-name <nick> [reason] will kick someone off, and they will see the reason you supply. Note: Your username will appear in the reason; there is *not* an anonymous way to kick users. [L71]

[16:54] <nIckmenza> /msg X topic #channel-name <topic> will change the channel topic. If AutoTopic is turned on by a 450+ op, this can be overridden every 30 minutes by X and the topic restored. Note, with topic, your username will proceed the topic you set. [L72]

[16:54] <nIckmenza> The next command level is 75, which gives access to the ban and unban commands. [L73]

[16:55] <nIckmenza> The usage is /msg X ban #channel-name <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. If duration and level are not designated, the default is 72 hours at level 75. Note #2: There, again, is not an anonymous way to ban someone, your username will appear in the reason. [L74]

[16:55] <nIckmenza> 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-name banlist. "banlist" is for viewing channel bans (which can be viewed by typing /mode #channel +b) , "Lbanlist" is for the bot list. [L75]

[16:55] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L76]

[16:57] <nIckmenza> 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. [L77]

[16:57] <nIckmenza> To unban /msg X unban #channel-name <nick> (or nick!user@host.mask). You cannot remove or set a ban that's higher than your own access level. [L78]

[16:57] <nIckmenza> 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 through X without having ops. [L79]

[16:57] <nIckmenza> Commands at level 100 are op deop invite suspend and unsuspend. [L80]

[16:57] <nIckmenza> This is the first level at which your access will allow you to op yourself through X. 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. [L81]

[16:58] <nIckmenza> To op someone Use /msg X op #channel-name <nick> Note: The person being opped will see who is opping them. This is *not* an anonymous way to op. [L82]

[16:58] <nIckmenza> To deop someone type /msg X deop #channel-name <nick> Note: Again, the individual being deopped will see who is deopping them. [L83]

[16:58] <nIckmenza> You can also op several nicknames with the same command: /msg X op #channel-name <nick1> <nick2> <nick3> .same thing goes for deop command. [L84]

[16:58] <nIckmenza> To have X invite yourself to a channel. type /msg X invite #channel-name You can use this from outside the channel to invite yourself to the channel. Just authenticate with X and then send the invite command --- /msg X invite #channel-name [L85]

[16:58] <nIckmenza> /msg X suspend #channel <username> <duration [m|h|d]> <level>. This temporarily stops a user's access to X. Note: m=minutes, h=hours, and d=days.If you don't set the level in suspend commands then X will set the suspend at the higher level you have in channel. [L86]

[16:58] <nIckmenza> An example to suspend username Joe for 3 days would be... /msg X suspend #here joe 3 d 500<-- note there is a space between the duration and the time format . [L87]

[16:59] <nIckmenza> Please remember two things about the suspend command. First, you cannot mix time formats. Use only *one* of the time formats ... s, m, h, or d. Second, you must use the username as it appears in the userlist. [L88]

[16:59] <nIckmenza> To unsuspend type /msg X unsuspend #channel-name <username> Note: You cannot suspend or unsuspend anyone with higher access than yourself. If a user with higher access suspends a user, someone with higher access has to unsuspend. [L89]

[16:59] <nIckmenza> Anyone you give ops to, whether or not they have access to X, can kick and ban users from the channel. In practice, it's probably best not to op anyone who has less than 100 access. [L90]

[16:59] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L91]

[17:00] <nIckmenza> SESSION E - LEVEL 200 COMMANDS: We will now start with the level 200 commands. [L92]

[17:00] <nIckmenza> There are only a few changes in the section of level 200, the Senior channel operator. They are as follows: [L93]

[17:01] <nIckmenza> You can now mass kick users matching a given nick!user@host pattern. [L94]

[17:01] <nIckmenza> If a channel key has been set you can also view it from outside the channel by typing /msg x status #channel, 200+ ops will receive the channel key as part of the channel status info, it is listed near the top of that status beside the modes. [L95]

[17:01] <nIckmenza> Once you have the key, you can simply /join #channel-name Key-Word-Here (it is case sensitive). [L96]

[17:01] <nIckmenza> If your channel is +i as well, you will need to do the invite command before joining the channel. [L97]

[17:01] <nIckmenza> SESSION F - LEVEL 400 COMMANDS: The next command level is 400. [L98]

[17:01] <nIckmenza> These users are able to modify the userlist by adding or removing users, and changing their information. The new commands added at level 400 are adduser, remuser, modinfo, clearmode, and status. [L99]

[17:02] <nIckmenza> To add a user to the userlist, use /msg X@channels.undernet.org adduser #channel <username> <access level> [L100]

[17:02] <nIckmenza> To remove a user it's /msg X remuser #channel <username>. You can't remove or add users with equal or higher access than your own. HOWEVER you can remove yourself from a channel at any level, EXCEPT level 500. [L101]

[17:02] <nIckmenza> 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, and then issue your command. It will work just like you were issuing the command yourself from inside the channel. [L102]

[17:02] <nIckmenza> /msg X clearmode #channel, will clear all channel modes from that channel and will have to have the modes reset by an op afterwards. [L103]

[17:02] <nIckmenza> This command can be useful if someone sets a key on your channel (+k) or sets the channel to invite (+i) while you are away and you can't get in. **NOTE**: The clearmode command should be done as a last resort. [L104]

[17:02] <nIckmenza> Modinfo is used to change information about a user in the userlist. These include automode and access. [L105]

[17:03] <nIckmenza> For all of these commands be sure you use the username that is in X. If you are unsure, you can do an access check on the user. [L106]

[17:03] <nIckmenza> To set automode, /msg X modinfo #channel automode <username> <OP/VOICE/NONE> - Automode is a convenient feature that allows you to be opped or voiced by the bot when you enter the channel, once you send your password. [L107]

[17:03] <nIckmenza> To change a user's access level in a channel type /msg x modinfo #channel access <username> <new level> [L108]

[17:03] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L109]

[17:04] <nIckmenza> SESSION G - LEVEL 450 THROUGH 499 COMMANDS: Users with levels 450-499 have a limited access to the SET command. [L110]

[17:04] <nIckmenza> /msg x SET <#channel> <variable> <value> - Set variables are userflag, autotopic, url, massdeoppro, description, and keywords. [L111]

[17:05] <nIckmenza> The first of the set commands is userflag . Which is similar to the old one, except now you can specify voice instead of op, or none at all. Value 2 is for Voice, value 1 is for OP, and value 0 turns them off (Neither Op, nor voice). [L112]

[17:05] <nIckmenza> * With AutoTopic set to ON -- X will reset the channel topic to the official URL and Description every 30 minutes *if* the channel is active. [L113]

[17:05] <nIckmenza> * 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. [L114]

[17:05] <nIckmenza> * 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. [L115]

[17:05] <nIckmenza> * Set Keywords <keywords> This sets keywords for your channel that will trigger on a SEARCH (level 0) of channels. If no keywords are specified, the current keywords are reset. The maximum string of keywords is 80 characters long. [L116]

[17:05] <nIckmenza> Floating Limit. These setting will allow X to reset the channel limit within a preset margin above the number of users in the channel, and within a preset period of time. [L117]

[17:06] <nIckmenza> /msg x SET <#channel> <variable> <value> - Set variables are floatlim, floatgrace, floatmargin, floatmax, and floatperiod. [L118]

[17:06] <nIckmenza> FLOATLIM - Sets the floating-limit feature on or off. By default, this feature is off. When turned on, the STATUS command will show the settings on the "Flags set:" [L119]

[17:06] <nIckmenza> FLOATGRACE - Sets the floating-limit grace value to be used in the channel. This number can be between 0-19. This makes X avoid changing the limit if it will be smaller than the grace value. The default value is 1. [L120]

[17:06] <nIckmenza> FLOATMARGIN - Sets the floating-limit margin to be used in the channel. This number can be between 2-20. The limit that X resets will be: number of users in the channel + FLOATMARGIN. The default value is 3. [L121]

[17:06] <nIckmenza> FLOATMAX - Sets the maximum limit for the floating-limit setting. This can be any number desired, and will prevent X from changing the channel limit to a number higher than the chosen number. The default value is 0, which turns the setting off. [L122]

[17:06] <nIckmenza> FLOATPERIOD - Sets the floating-limit period, in seconds, to be used before X resets the channel limit. This number must be between 20-200. The default value is 20 seconds. [L123]

[17:07] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L124]

[17:09] <nIckmenza> To make X join, type /msg X set #channel autojoin ON - This insures that X will always rejoin your channel after a netsplit. [L126]

[17:10] <nIckmenza> To make X leave, type /msg X set #channel autojoin OFF - This is to make X part and stay off your channel. (Not really recommended). [L127]

[17:10] <nIckmenza> You can also make X join/part temporarily, and not effect the channel settings, you can type: [L128]

[17:10] <nIckmenza> /msg x join #channel - Does exactly what it says, joins the channel. [L129]

[17:10] <nIckmenza> /msg x part #channel - Parts the channel. [L130]

[17:10] <nIckmenza> NOTE: Part command will show who parted the bot. *** Parts: X [cservice@undernet.org] (At the request of TheBeast) for example.Join command can be used at level 450+ also. [L131]

[17:10] <nIckmenza> Next command is SET. This allows you to customize your level of protection for the channel. To set any of these parameters Use /msg X set #channel <parameter> <on/off> [L132]

[17:11] <nIckmenza> * 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. [L133]

[17:11] <nIckmenza> * 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. [L134]

[17:11] <nIckmenza> * StrictOp is a parameter that allows only those users with 100 level or higher access to X to be opped. [L135]

[17:11] <nIckmenza> We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L136]

[17:12] <nIckmenza> I'll save our other topics for next time.. when you can join us for OpSchool Part 3: "A Channel User's Guide to the Galaxy." You'll hear what Undernet considers abuse, survival skills for floods and netsplits, and an all-time favorite... [L137]

[17:12] <nIckmenza> This script was made possible with the help of quite a few people. I'd like to thank the originators.. Pucker, MatthewA, D-in-Tx, Manning, Teal, SeKs, Coccyx, and more recently, Mikey-, LordLuke and DaveB, and who ever else that I forgot :o) [L138]

[17:13] <nIckmenza> 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! [L139]

[17:13] <nIckmenza> Let's not forget past leader of OpSchool Team - Isaiah (CService Admin)...Rest in peace dear friend... [L140]

[17:13] <nIckmenza> 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. [L141]

[17:13] <nIckmenza> This concludes our class, thank you for taking the time to attend :o) [L142]

[17:13] <nIckmenza> We will now open the channel up for general questions. (Rev.nIckmenza 1/4/2005) [END] [L143]

End of #Opschool buffer Mon Feb 26 02:38:55 2007 by Gary