It is currently Sat Dec 16, 2017 7:58 am

All times are UTC [ DST ]




 Page 1 of 1 [ 7 posts ] 
Author Message
 Post subject: #opschool folder
PostPosted: Mon May 11, 2009 7:53 am 

Joined: Sun May 10, 2009 9:52 pm
Posts: 40
Location: HÖLLENSTRASSE
Arrangement:

- Username and Channel registrations

- The lost world of X

- A channel user's guide to the Galaxy

- Frequently asked questions in #cservice (new)

- Autoinvite X command and Forms updated


See below.


Last edited by kN_ on Sun Jun 14, 2009 11:09 pm, edited 2 times in total.


_________________
-kN
kn@undernet.org
Offline
 Profile  
 
 Post subject: Username and Channel registrations
PostPosted: Mon May 11, 2009 7:53 am 

Joined: Sun May 10, 2009 9:52 pm
Posts: 40
Location: HÖLLENSTRASSE
Hello to everyone who's currently watching the class, we hope you’ll enjoy your stay :) [L1]
Please sit back, turn your logging on and keep for later review. [L2]
This instructional script is brought to you by the Undernet Channel Service Committee. Please send comments, suggestions, or remarks to cservice@undernet.org [L3]
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]
I'd like to welcome you all to the Undernet Channel Service OpSchool (part I). [L5]
Now for the rules of the class... [L6]
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]
MiscTutor handles nicks beginning with numbers or characters such as ^, ], _, and so on, French is "AideTout", Spanish "YoAyudo", Romanian "EuAjut", Turkish "TrYardim", Italian "Io_Aiuto". [L8]
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]
Please direct your questions through private message to the tutor who covers your name group. [L10]
The channel is moderated (+m) and the Delayed Join Mode is activated (+D) to lessen interruptions from join/part activity or nickname changes. [L11]
We’d like to remind you that you can enable your logging now using: /log <on|off> <window-goes-here> [-f filename-here]. [L12]
Do not message the instructor - My job is to keep the lesson flowing. Remember, you have tutors to answer your questions. [L13]
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]
The lesson will start shortly so grab your popcorn and drinks, turn off the TV and pay attention! :) [L15]
We will now take a brief pause in order for you to turn on your logging and locate your tutor. [ph] [L16]
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]
This in turn ends up creating these work-producing, expectation-shattering ideas, several of which are simplistically explained below. [L18]
Understanding the basic misconceptions held about Undernet Channel Services will make your username and channel registration and maintenance experience much easier. [L19]
We'll start by learning how to create and register an username with X. [L20]
In order to use X at all or to register a channel, you need to have an username. Keep in mind that by registering an username doesn't mean you'll register a nickname, it's not like in other networks, UnderNet does *NOT* support any registration for nicknames and more than this nicknames are not owned on UnderNet; in order to indentify ourselves we do it by our usernames not by our nicknames. [L21]
Now, to create an username, go to our website: http://cservice.undernet.org/live/ [L22]
And on the left screen from the website there's an option called "Register!"; click on it and follow the steps; Below are the steps that must be followed. [L23]
There are 8 steps on the next page that *MUST* be completed or you will not receive an username. They are as follows... [L24]
*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 an username, since we cannot verify you. [L25]
*Step 2 - Choose an Username* - Here is where you pick your username. Remember, it has to be unique as in a later not planning to change it into a different name as it's not possible. As a sidenote: username patterns like *cserv* or *ircop* are forbidden so don’t even think about registering them. This is a measure of preventing possible impersonation. [L26]
*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. By the way, the strongly recommend the usage of ISP e-mails, you can recover them if anything, by contacting the provider. [L27]
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. Note: free e-mails are still accepted by us, but as soon as it's coming an abuse from that domain, we'll simply block it, with no questions asked. [L28]
*Step 4 - Language of choice* - Here you will be able to choose the language you desire to use with X commands replies later. Note: you will be however free to change it later on via X commands whenever you wish, chosing from one of the available language. [L29]
*Step 5 - Secret Question/Answer* - This is for password/username retrieval. Make 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]
*Step 6 - Security Code* - This is the code which prevents multiple attempts for username registrations. Enter the code you see in the above picture into the below input box (upper/lower case doesn't matter). [L31]
*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 to use channel services to have an 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]
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 the email or simple copy/paste it into your browser; you have to confirm the registration by clicking on the link within 24 hours or else it will expire and you'll have to register the username again. Once you click on it, your username is activated and can be used. [L33]
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]
These are 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]
We will now pause briefly to allow you to catch-up and to ask any questions to your tutor that you need. [ph] [L36]
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]
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]
They are termed "takeover applications". Any such applications are rejected and the applicant placed on a probation if he tries it repeatedly. [L40]
Also to prevent abusing of our registration system: [L41]
* A new username will be prevented from registering a channel for 10 days after its creation. [L42]
* A new username will be prevented from supporting any channels for 5 days after its creation. [L43]
* A user won't be able to support more than 2 channels at any given time. [L44]
<Applicant>: All I need to get my channel registered is 10 usernames? [L45]
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]
That is why we require 10 people as supporters, generally only one e-mail address is allowed per person with an ISP account. [L47]
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]
A channel is registered only after its application has been accepted by CService, not after the application has been successfully submitted. [L49]
It takes 7-12 days for your application to be reviewed, verified, checked, twisted, turned; a length of time called the posting period. [L50]
Having posted an application does indicate a claim of ownership, but the claim must be validated, and this takes time. [L51]
We will now take a brief pause in order for you ask your tutor any questions. [ph] [L52]
<Applicant>: My channel is in incoming. What does incoming mean?? [L53]
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 and more than this *If* in case the supporters don't confirm their support within 72 hours. Channel and the applicant username will be placed in NOREG automatically for another 72 hours (3 days). [L54]
<Applicant>: My channel is currently in Pending Traffic Check. Explain this please. [L55]
Traffic check is the step where we check the traffic of your supporters and assure yourself that all of them will join frequently your channel ALREADY LOGGED IN. X will monitor only their joins, others joins are not counted nor text-channel messages as X is deaf. This step takes between 1 days and 3 days, if there's not enough supporter activity in other words lack of activity the channel will be rejected automatically. [L56]
<Applicant>: My channel application is now Pending Notification. Explain "Pending Notification" please. [L57]
This means the application has fulfilled the initial traffic requirements. You will receive notices in your channel that your application is pending in every one hour and everyone from the channel will be able to object or to check the channel application status via the link is given in the notice sent. This step takes approximately 5 days. [L58]
The objections must have valid reasons or will NOT be taken into consideration. [L59]
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]
<Applicant>: My channels status shows it is waiting for review. What does that mean? [L61]
Ready for Review is the final step in the process before Accepted or Rejected and your channel will be reviewed in the next 1-3 days; sometimes it might take more than 3 days due to the amount of applications we've received and it has to be checked by our Cservice administrators. This doesn't mean your application will be accepted. The decision could be also rejected. [L62]
<Applicant>: I'll use this username from this guy in another channel, he'll never know I did. [L63]
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]
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]
Your application will be rejected, your username and channel will be placed on the NOREG list for 3 days and you won't be able to apply for the channel until then. Make sure the usernames you use are people you know (and trust not to back stab you) and are active in your channel. [L66]
<Applicant>: I just opened my channel and I need X to get it off the ground. [L67]
A simple quote from our registration web page, authored by a most clooful admin, is appropriate here: [L68]
"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]
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]
Let's pause here so that you may ask questions of your tutors.. ask now while your questions are fresh. [ph] [L71]
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]
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]
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]
The automated site walks you through each step of the process.. so it pays to be prepared. Realize that CService gets 150 applications per day... over 1000 per week! Help yourself and us by taking the time to follow the steps. [L75]
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]
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]
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]
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]
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]
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]
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]
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]
A channel manager has a large responsibility that takes time and commitment. You agree to take care of what happens, *even when you are offline*. Start by preventing a purge for your absence or for low traffic. [L84]
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]
A registered channel is up for grabs if the manager is missing for 21 days. [L86]
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]
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]
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]
<Channel Manager>: I'm changing ISPs and I'll have a new e-mail, no need to contact CService about it. [L90]
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]
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]
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]
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]
PLEASE use this form ONLY if you can't access your old email we have on record with your username anymore. [L95]
Also incomplete forms with missing information 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]
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]
Any channel manager or user with a 500 level access must update a new e-mail of record with CService to maintain the 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]
<Channel Manager>: I'm there everyday; how can someone say I'm a missing manager? [L99]
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]
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]
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]
We will now take a brief pause in order for you ask your tutor any questions. [ph] [L103]
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]
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]
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]
Undernet has a concise policy towards abuse: *zero tolerance* . The Server Admins and Irc Operators collaborate to detect and remove clones, flooders and others who harass users. If you spot an abusive channel that’s registered and you have solid proof in form of logs about it, please do not hesitate to report it to us via e-mail at cservice-abuse@undernet.org. Remember to copy/paste the proof in the e-mail’s body *NOT* attaching them as documents. [L107]
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]
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]
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]
<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]
But you will get blamed. You are responsible for anything that is done by ops in your channel. [L112]
It's important that you realize that the ops you choose 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]
An user spamming invites, flooding users or channels, taking over channels, while authentified in a registered channel makes that channel, and you, responsable. [L114]
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]
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]
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. [L117]
Let's pause here so that you may ask questions to your tutors... and careful not to flood 'em :) [ph] [L118]
I'll save our other topics for next time... when you can join us for OpSchool part II: "The Lost World of X". [L119]
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, k1dnapper (the current OpSchool team leader), Panzer-, Spidel, and whoever else that I forgot :) [L120]
I'd also like to thank all the people who volunteered their time presenting this class... without you folks, we were nothing! Thanks! [L121]
Let's not forget one of the past leaders of the OpSchool Team - Isaiah (CService Admin)... Rest in peace dear friend... [L122]
As a personal note... [L123]
I've had fun teaching this class, and I hope you learnt something during this session. [L124]
I've really enjoyed teaching here today... I hope you have enjoyed being here and learnt something that will make your time on the Undernet more enjoyable... I would like to thank you all for your patience and time spent here :) [L125]
We will now open the channel up for general questions.
et more enjoyable... I would like to thank you all for your patience and time spent here :) [L125]
We will now open the channel up for general questions.



_________________
-kN
kn@undernet.org
Offline
 Profile  
 
 Post subject: The lost world of X
PostPosted: Mon May 11, 2009 7:55 am 

Joined: Sun May 10, 2009 9:52 pm
Posts: 40
Location: HÖLLENSTRASSE
Hello again :) [L1]
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]
I'd like to welcome you all to the Undernet Channel Service OpSchool (part II). [L3]
We have a lot of very knowledgeable people there to help you. Just be patient after you ask your question. :) [L4]
Today's session will cover how to harness the powerful commands provided in X. [L5]
Now for the rules of the class... [L6]
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]
MiscTutor handles nicks beginning with numbers or characters such as ^, ], _, and so on, French is "AideTout", Spanish "YoAyudo", Romanian "EuAjut" Turkish "TrYardim", Italian "Io_Aiuto". [L8]
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]
Please direct your questions by private message to the tutor who covers your name group. [L10]
The channel is moderated (+m) and Delayed Join Mode is active (+D) to lessen interruptions by join/part activity as well as nickname changes. [L11]
We’d like to remind you that you can enable your logging now using: /log <on|off> <window-goes-here> [-f filename-here]. [L12]
Do not message the instructor - My job is to keep the lesson flowing. Remember, you have tutors to answer your questions. [L13]
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]
The lesson will start shortly so grab your popcorn and drinks, turn off the TV and pay attention! :) [L15]
We will now take a brief pause in order for you to turn on your logging and locate your tutor. [ph] [L16]
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]
This registration provides a channel manager with a flexible tool for managing the channel and handling channel affairs. [L18]
X is a specialized server often referred to as a bot which actually hold the channel open and allow for control. [L19]
A special note, when giving the commands, I will use < > for required elements and [ ] for optional elements. [L20]
Now for a few definitions: [L21]
The Manager - The user who applies for and owns the registered channel. [L22]
Channel Operators - Users given the priviledge of being an operator by the manager. The manager grants them access to the bot. [L23]
Userlist - The database in X that holds the information about the channel users added to the bot. [L24]
CService Operator - An IRC user experienced in the X commands and is an authorized member of the CService Team [L25]
CService Representative - An experienced CService Operator who has been asked to assist CService in providing user support. [L26]
CService Administrator - A very experienced CService Helper who manages CService responsibilities. [L27]
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]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L29]
SESSION B - CHANNEL MANAGEMENT: Now... for the instructions on channel management. [L30]
As the channel manager YOU are ultimately responsible for what goes on in your channel ** whether you are there or not **. [L31]
Your primary duty is to ensure all the users on your channel understand and are willing to comply with the CService guidelines. [L32]
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]
Finally you must login to your 500 access at least once every 21 days or else according to Channel Services AUP document, your channel can and will be purged. [L34]
Changes to managers emails or forgotten password should be handled via the website or via one of our CService mailinglists: [L35]
* X@undernet.org for EMail Changes if the username owner can't access email address on record anymore. [L36]
* usernames@undernet.org for username unsuspensions if the username was suspended previously by a CService Administrator for being hacked/abused or better yet /join #usernames and ask there for any usernames related issues. [L37]
* cservice-abuse@undernet.org for other issues that cannot be handled via X@undernet.org. [L38]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L39]
SESSION C - LEVEL 0 COMMANDS: Now we'll cover user levels and commands: [L40]
These apply to X and to any users that are added to the database in the bots. [L41]
The levels for channel personnel range from 0 - 500 [L42]
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]
/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]
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]
/msg X lbanlist #channel <search string> shows the list of bans set through X. [L46]
You can perform the banlist or lbanlist commands either while in the channel or outside of it. [L47]
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/live , login and click *Channel info* on the left menu to see the full list. [L48]
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) can hold a maximum of 300 bans. [L49]
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]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L51]
/msg X chaninfo #channel_name - gives information such as the channel manager's username as well as the Channel Description and URL. [L52]
/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]
/msg X help - command will explain the usage of that command. Use this to see command syntax and a wealth of helpful reminders. [L54]
/msg X motd - displays X's message of the day. [L55]
/msg X set noadduser ON/OFF - Whether this option is enabled, user can't be added in any channels unless it will disable it to the initial form which is OFF. [L56]
/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. [L57]
To authenticate yourself to X, use /msg X@channels.undernet.org LOGIN <username> <password> [L57]
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. [L59]
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. [L60]
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> [L61]
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. [L62]
Verify also shows the username of the person. [L63]
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. [L64]
/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. [L65]
/msg X banlist #channel <search string> shows you the channel banlist. This is also a level 1 command. [L66]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L67]
SESSION D - LEVEL 25 THROUGH 100 COMMANDS: The next level where new commands are introduced is level 25. [L68]
/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. [L69]
/msg X devoice #channel <nick1> <nick2> <nick3> and so on... This has X DEvoice you, or -v on the given channel. As above, just typing the command without a nickname, will have X devoice you. [L70]
The additional commands at level 50 are kick and topic. These allow a user to kick someone or change the channel topic even if they are not a channel operator. [L71]
/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. [L72]
/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. [L73]
The next command level is 75, which gives access to the ban and unban commands. [L74]
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 included, the default is 5 minutes at level 75. The maximum ban duration is 2400 hours or 100 days. Note #2: There, again, is not an anonymous way to ban someone, your username will appear in the reason. [L75]
Remember, bans set by /msg X ban... are set in the Lbanlist. You must /msg X Lbanlist #channel_name * 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. [L76]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L77]
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. [L78]
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. [L79]
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. [L80]
Commands at level 100 are op deop invite suspend and unsuspend. [L81]
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. [L82]
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. [L83]
To deop someone type /msg X deop #channel_name <nick> Note: Again, the individual being deopped will see who is deopping them. [L84]
You can also op several nicknames with the same command: /msg X op #channel_name <nick1> <nick2> <nick3>. same thing goes for deop command. [L85]
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 [L86]
/msg X suspend #channel <username> <duration [s|m|h|d]> <level>. This temporarily stops an user's access to X. Note: s=seconds, 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. [L87]
An example to suspend username Joe for 3 days at level 500 (channel manager level) would be... /msg X suspend #here joe 3d 500 [L88]
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. The maximum duration is 372 days. [L89]
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. [L90]
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. [L91]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L92]
SESSION E - LEVEL 200 COMMANDS: We will now start with the level 200 commands. [L93]
There are only a few changes in the section of level 200, the Senior channel operator. They are as follows: [L94]
You can now mass kick users matching a given nick!user@host pattern. [L95]
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 a part of the channel status info, it is listed near the top of that status beside the modes. [L96]
Once you have the key, you can simply /join #channel_name key_goes_here (it is case sensitive). [L97]
If your channel is +i as well, you will need to do the invite command before joining the channel. [L98]
SESSION F - LEVEL 400 COMMANDS: The next command level is 400. [L99]
These users are able to modify the userlist by adding or removing users, and changing their information. The commands at level 400 are adduser, remuser, modinfo, clearmode, and status. [L100]
To add an user to the userlist, use /msg X@channels.undernet.org adduser #channel <username> <access level> - You can't add an higher access on the channel or equal with yours, ONLY below. [L100]
To remove an user it's /msg X remuser #channel <username>. You can't remove users access that have the same level or higher than yours. HOWEVER you can remove yourself from a channel at any level, EXCEPT level 500. [L101]
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]
/msg X clearmode #channel - will clear all the channel modes from that channel. [L103]
This command can be useful if someone sets a key in 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]
Modinfo is used to change information about an user in the userlist. It includes automode and access. [L105]
For all of these commands make sure you use the username that is in X. If you are unsure, you can do an access check on the user. [L106]
To set automode, /msg X modinfo #channel_name 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. [L107]
To change an user's access level in a channel type /msg x modinfo #channel_name access <username> <new level> [L108]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L109]
SESSION G - LEVEL 450 THROUGH 500 COMMANDS: Users with levels 450-499 have a limited access to the SET command. [L110]
/msg x SET <#channel> <variable> <value> - Set variables are userflags, autotopic, url, description, and keywords. [L111]
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 (you can either specify 1/op or 2/voice or 0/none, all of them work). [L112]
* 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]
* 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]
* 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]
* 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. Note: The search option based on channel keywords doesen’t work anymore, they serve as additional info about the channel. [L116]
Floating Limit. This 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]
/msg x SET <#channel> <variable> <value> - Set variables are floatlim, floatgrace, floatmargin, floatmax, floatperiod. [L118]
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]
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]
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]
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]
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]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L124]
To make X join, type /msg X set #channel_name autojoin ON - This insures that X will always rejoin your channel after a netsplit. [L126]
To make X leave, type /msg X set #channel_name autojoin OFF - This is to make X part and stay off your channel. (Not really recommended). [L127]
You can also make X join/part temporarily, and not effect the channel settings, you can type: [L128]
/msg X join #channel_name - Does exactly what it says, joins the channel. [L129]
/msg X part #channel_name - Parts the channel. [L130]
NOTE: Part command will show who parted the bot. *** Parts: X [cservice@undernet.org] (At the request of k1dnapper) for example. Join command can be used at level 450+ also. [L131]
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]
* NoOp set to ON means no one can get ops in the channel 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]
* 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]
* StrictOp is a parameter that allows only those users with 100 level or higher access to X to be opped. While this option prevents massban performed by unknown oped people, remember that the people added with 75+ access on the channel access list can still massban via X command.[L135]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L136]
I'll save our other topics for next time... when you can join us for OpSchool part III: "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]
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, Mikey, LordLuke and DaveB, and more recently k1dnapper (your efforts and ambition are appreciated mate) and whoever else that I forgot :) [L138]
I'd also like to thank all the people who volunteered their time presenting this class... without you folks, we were nothing! Thanks! [L139]
Let's not forget the past leader of our beloved project - Isaiah (CService Admin)... Rest in peace dear friend... [L140]
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]
This concludes our class, thank you for taking the time to attend :) [L142]
We will now open the channel up for general questions.



_________________
-kN
kn@undernet.org
Offline
 Profile  
 
 Post subject: A channel user's guide to the Galaxy
PostPosted: Mon May 11, 2009 7:56 am 

Joined: Sun May 10, 2009 9:52 pm
Posts: 40
Location: HÖLLENSTRASSE
Hello all :) [L1]
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]
I'd like to welcome you all to the Undernet Channel Service OpSchool (part III). [L3]
We have a lot of very knowledgeable people there to help you. Just be patient after you ask your question :) [L4]
You'll hear what Undernet considers abuse, survival skills for floods and netsplits, and an all-time favorite... [L5]
Now for the rules of the class.... [L6]
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]
MiscTutor handles nicks beginning with numbers or characters such as ^, ], _, and so on, French is "AideTout", Spanish "YoAyudo", Romanian "EuAjut" Turkish "TrYardim", Italian "Io_Aiuto". [L8]
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]
Please direct your questions by private message to the tutor who covers your name group. [L10]
The channel is moderated (+m) and Delayed Join Mode is active (+D) to lessen interruptions by join/part activity as well as nickname changes. [L11]
We’d like to remind you that you can enable your logging now using: /log <on|off> <window-goes-here> [-f filename-here]. [L12]
Do not message the instructor - My job is to keep the lesson flowing. Remember, you have tutors to answer your questions. [L13]
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]
The lesson will start shortly so grab your popcorn and drinks, turn off the TV and pay attention! :) [L15]
We will now take a brief pause in order for you to turn on your logging and locate your tutor. [ph] [L16]
SESSION A - FLOOD PROTECTION: Flood attacks are unfortunately not a rare enough occurance on the Undernet. [L17]
What is a flood? Flooding comes in several varieties, including: [L18]
CHANNEL TEXT FLOODS -- (multi lines of text sent to the channel chat window) -- are usually considered floods if over about 5 lines [L19]
NICK FLOODS -- changing nicks over and over rapidly causing the channel window to be flooded with nick change notices [L20]
DCC FLOODS -- attempts to send rapid and massive amounts of dcc chat requests and/or files to you [L21]
And finally CTCP FLOODS -- where an user rapidly sends ctcp info requests to you. These are usually in the form of /ping, /version, /time, etc. [L22]
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]
The other floods are annoying, but do not usually cause disconnects (with their associated loss of presence -- and therefore ops -- on your channel) [L24]
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]
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]
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]
We'll cover what to do to defend against floods in a moment. [L28]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L29]
Fortunately, every user has the tools already available to combat flooders in a responsible way. [L30]
NEVER retaliate against a flooder by flooding back. All flooding is wrong and abuses Undernet resources. [L31]
Here are some advices to stop flooders... [L32]
1. Set up an alias key to *** /silence *!*@* or /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) for more personal protection against flooders see the documentation from http://help.undernet.org/faq.php?what=protection. [L33]
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]
Both should be used since they compliment eachother and each alone has it’s weaknesses. /silence works from the abuser’s server so it may be delayed in starting because of lag. /ignore is direct within the user’s own client so is instant, no lag, but allows the incoming to enter the user’s buffers so a sustained massive flood can still disrupt an user that’s using only /ignore. [L34A]
As for ICMP floods, the only defence 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]
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]
Hopefully you won't be subject to any flood attacks, but these tools should help protect you. [L37]
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]
We'll now pause briefly so you can msg your tutor if needed. [PH] [L39]
CTCP and ICMP flooding are "denials of service" and are forbidden under internet rules (and are also felonies under U.S. law). [L40]
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]
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]
Even when an 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]
You can setup a simple script to help get that info. For help with setting up scripts please join #mIRC (if you're using mIRC). [L44]
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]
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]
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]
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]
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]
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]
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]
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]
For these reasons we'd like to ask you to use these features sparingly. [L54]
2. There is another recently possiblity to avoid flood atacks over your client or IP you use. Users can now /mode nickname +x for host hiding. This will show ident@username.users.undernet.org . ie: Nick is ident@username.users.undernet.org. You will need to login to your registered Undernet username and then type /mode nickname +x. [L55]
We'll pause briefly again now so you can /msg your tutor with any questions. [ph] [L56]
SESSION B - NETSPLITS AND DESYNCHS: NetSplits and server Desynchs are two problems that we live with on the net. [L57]
They can range from merely bothersome to outright trouble. So lets take a minute to review them briefly. [L58]
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]
There is nothing you can do to prevent or cause a netsplit. If the split lasts more than a few minutes, you might want to jump to another server and try to get onto the other side of the netsplit. [L60]
If X is gone from your channel due to netsplit, you will need to wait patiently for it to return. [L61]
Periodically, during a netsplit, servers will become desynched. [L62]
A Desynch is when servers send incomplete (or unsynchronized) information to each other and get confused as to the status of user and channel modes. This is often the case when a server keeps resetting modes that a user or bot tries to change [L63]
You can recognize a desynch by some or all of the following: [L64]
-- some people say they can see the topic on the channel and some can't (though there are other reasons this may happen). [L65]
-- users without ops are able to op/deop/etc others (those "invisible" ops are on a desynched server) [L66]
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]
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]
You can also resynch your channel by having everyone (including X) leave the channel so that it closes... then rejoin the channel. [L69]
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 an 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]
We'll pause briefly again now so you can /msg your tutor with any questions. [ph] [L71]
SESSION D - LATEST NEWS ON UNDERNET: [L72]
We’ll be explaining now some of the latest channel modes, which can be powerful tools against floodbots/drones. [L73]
Keep in mind that the Undernet Network is providing you with all the instruments you need to keep your channel safe, but lastly it depends on you and your knowledge of them. [L74]
The Undernet Coders have been working hard and steady on the improvement of Undernet servers. This brings new features for users. [L75]
One of those is the hide host option which was explained a few minutes ago. But there are more. [L76]
* 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 an 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. [L77]
Lately registered channels will have the +R mode enabled, meaning they’re registered and C should not act on them in order to score points for the ops. +R mode is set by default to all registered channels (that have X) and the only way to remove it is by purging the channel. [L78]
It’s pretty important to distuinguish between the 2 channel modes, +r and +R, as they are very different one from another [L79]
* Users can now set +D (Delayed mode) on any channel they have ops in. If a channel is under +D mode users who joins the channel will be hidden from the nickname list of the channel unless they type something on the main channel likeness channel-text-message or anything alike Or users are voiced or opped. [L80]
If the channel is set to -D again and there are still "hidden" users left, the server will set mode +d until the last one is visible or left the channel. [L81]
"Hidden" users are shown by /names -d #channel. If you /whois an user who is in a channel with +D set and the user is not "visible" there yet, you'll see that channel prefixed by a < sign. Example: <#im.in.a.channel.with.D.mode. [L82]
* 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. [L83]
* Users can now see who users are (the user's username) when they /whois another user who is logged into an X username. [L84]
* 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. [L85]
We'll pause briefly again now so you can /msg your tutor with any questions. [ph] [L86]
I'll save our other topics for next time... when you can join us for OpSchool part IV: "Frequently asked questions in #cservice". [L87]
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, DrCkTaiL, Lordluke, MarkT, Mikey-, Robinb, Signe, DaveB and more recently k1dnapper (our Opschool leader, your efforts and ambition are well appreciated mate) .. and who ever else that I forgot. :) [L88]
I'd also like to thank all the people who volunteered their time to help out bringing up and presenting the classes. Without you guys we were nothing! Thanks :) [L89]
Let's not forget our beloved past leader of OpSchool - Isaiah (CService Admin)... Rest in peace dear friend... [L90]
If you ever have any questions about the material you see here in #opschool or about the Undernet in general... please join #cservice. Additionally you can mail your suggestions/questions to opschool@undernet.org - CService volunteers will be glad to try to help you with your problem(s)... or if they can't they'll do their best to tell you where to go to find the help you need. [L91]
Our site can be found at http://cservice.undernet.org/main/opschool/ :o) [L92]
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 would like to thank you all for your patience and time spent here :) [L93]
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. [L94]
This concludes our class, thank you for taking the time to attend. [L95]
We will now open the channel up for general questions. [END] [L96]



_________________
-kN
kn@undernet.org
Offline
 Profile  
 
 Post subject: Frequently asked questions in #cservice
PostPosted: Mon May 11, 2009 7:57 am 

Joined: Sun May 10, 2009 9:52 pm
Posts: 40
Location: HÖLLENSTRASSE
Hello to everyone who's currently watching the class, we hope you’ll enjoy your stay and learn a few things :) [L1]
Please sit back, turn your logging on and keep them saved for later review. [L2]
This instructional script is brought to you by the Undernet Channel Service Committee. Please send comments, suggestions, or remarks to opschool@undernet.org [L3]
The aim of today’s class is to provide answers for some of the most frequent questions asked in #cservice and serve as a future reference. [L4]
I'd like to welcome you all to the Undernet Channel Service OpSchool (part IV). [L5]
Now for the rules of the class... [L6]
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]
MiscTutor handles nicks beginning with numbers or characters such as ^, ], _, and so on, French is "AideTout", Spanish "YoAyudo", Romanian "EuAjut", Turkish "TrYardim", Italian "Io_Aiuto". [L8]
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]
Please direct your questions through private message to the tutor who covers your name group. [L10]
The channel is moderated (+m) and the Delayed Join Mode is activated (+D) to lessen interruptions from join/part activity or nickname changes. [L11]
We’d like to remind you that you can enable your logging now using: /log <on|off> <window-goes-here> [-f filename-here]. [L12]
Do not message the instructor - My job is to keep the lesson flowing. Remember, you have tutors to answer your questions. [L13]
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]
The lesson will start shortly so grab your popcorn and drinks, turn off the TV and pay attention! :) [L15]
We will now take a brief pause in order for you to turn on your logging and locate your tutor.
Remember, you can either /msg your tutor during the lesson with your questions, or save them for last when the channel will be opened. [ph] [L16]
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]
This in turn ends up creating these work-producing, expectation-shattering ideas, several of which are simplistically explained below. [L18]
Each frequent asked question will be marked with ”Q” and an answer (marked ”A”) will be provided. Again, we strongly encourage you to /msg your tutors for further details about something that’s unclear. [L19]
We hope this FAQ will provide you with some of the answers you've been always looking for and help you understand better the usage of the X commands and channel management. L20]
Q1: My channel is in Notification, what does that mean? I keep getting some annoying notices. [L21]
A1: This is the second section of the channel registration step called Pending. It lasts 5 days and during the Notification section you and the rest of the users on the channel will get a system message informing the channel is undergoing through registration and offers you a direct link where you’ll be able to post any objections you might have. [L22]
Q2: I've been banned in #paris with the following message: "infected client." - What should I do? I'm new around and help will be appreciated. [L23]
A2: This means your computer is infected with a form or another of a virus/spyware/malware. On Undernet you have the free option of getting your system cleaned if you visit #vh or #dmsetup [L24]
Q3: My channel was purged recently and I'd like to know the reason. Please help me [L25]
A3: Common reasons for registered channels being purged are: Manager failed to login repeatedly for 21 days or channel got involved in abusing our Registration System which is strictly forbidden and sanctioned on the spot. For details you should ask the channel operators/officials in #cservice. [L26]
Q4: I'm playing trivia all day long and the channel is being processed for registration. Will it affect its registration? [L27]
A4: No, trivia will not affect your channel, neither colors or other text enhancements, nor will they be counted as traffic to the channel. [L28]
Q5: I'm about to leave for a long period and I'd like to pass the 500 to one of my best friends. What are the steps please? [L29]
A5: In order to change the manager, the registered channel needs to be 90 days or older. Then you should add the person with 499 access level to the list, make sure your and his e-mail addresses are working and then visit http://cservice.undernet.org/live where you’ll need to login to your username and click *Forms* and then *Manager Change Request* and follow the steps. [L30]
Q6: I happen to sit in a channel fulfilled with drones and it's registered. The manager is playing with '-say a' and it's a mess there! Where should I report such abusive channels? [L31]
A6: Channel Services welcomes and encourages reports of such abusive channels that violate the policies. To report such a channel gather the timestamped logs that serve as proof and then paste them into the body of an e-mail that needs to be sent to cservice-abuse@undernet.org. Remember not to attach them as text documents. [L32]
Q7: My channel is opless!! I want to get it registered but I have no ops. Please op me there! [L33]
A7: When asking this question you should always consider that #cservice deals with registered channels and X commands only. The adequate channels for this kind of help are #ZT / #nastrand and additionally #arlington [L34]
Q8: My username has been globally suspended it says. What can I do in order to get it unsuspended? [L35]
A8: Channel Services posses a project that deals exclusively with username issues, namely #usernames, please visit it to get more information on why your username got suspended by a CService Admin. [L36]
Let's pause here so that you may ask questions to your tutors... and careful not to flood 'em :) [ph] [L36A]
Q9: My channel has a second manager named CSCAbuse and my manager username got suspended. What’s the deal? [L37]
A9: Your channel has been tagged as involved in abusing our Registration System. To get more information, you (ONLY THE CHANNEL MANAGER) should send an e-mail to cservice-abuse@undernet.org and include the channel name in the subject. Keep in mind that you won’t get help online, just via the e-mail address above mentioned so don’t bother insisting in #cservice about it. [L38]
Q10: Who's the dumbest #cservice operator? DaffyDuck or kN? Out of curiosity. [L39]
A10: Although the question arises many subsidiary ones, it's very difficult to establish the levels of dumbosity between the two subjects. It thusly remains a matter of perspective :) [L40]
Q11: I'm wondering why some channels (eg #brasov) have two managers. I have my own channel and there's a need for a second manager, I'm away most of the time. [L41]
A11: Those are not real people, but CService tools which aids our staff to recognise a channel that’s been tagged in the past. Caution, CSCAbuse, NoPurge are simply tools that appear as channel managers but which in reality are used by our staff in their work. [L42]
Only special designated channels by CService can have 2 managers, regular ones cannot so don’t bother asking for a second manager. You have at your disposal the *Manager Change Request* option which allows you to have a temporary manager, while you’re away but your access will be suspended during this time. [L43]
Q12: I was ignored by X. How much it lasts and why did it happen? Is there a way to check why it ignored me and for how long? [L44]
A12: You can type /silence X and take a look through the list of the ignored people by X on the server you’re currently on. Additionally you can ask a friend to check the ignore list on X via : /msg X showignore, and search for the indicated pattern. [L45]
The duration of such an ignore can be of maximum 60 minutes and the remaining time will be displayed next to the ignored mask in the Ignore List of X. [L46]
Q13: My channel is in *Ready for Review* stage for 3 days now. Will we get a decision today? [L47]
A13: The Ready for Review stage may take up to 3 days usually, but sometimes it can last longer. You should keep in mind that CService Admins have their personal life and do this job voluntarily. You’ll need to be patient and a decision will be presented to you as soon as possible. Insisting daily in #cservice won’t speed things up. [L48]
Q14: How can I edit the modes of my channel through X? (+m, +k and the rest). I'm still in a learning process... is there a website containing all X commands? [L49]
A14: You cannot change channel modes via X, but you can save them in X’s memory for that channel, so when it comes back from a split or after you’ve parted it, X will remember and reset the saved modes. To save them via X command you need to perform: /msg X set #yourchannelhere mode - you will need 450 or higher access to issue this command. [L50]
As for the entire list of X commands you can find them at: http://cservice.undernet.org/docs/ translated in various languages. [L51]
Q15: Hi, my channel has been set-up +k and also +i, how can I get back in? I'm the manager and I want to get inside and re-establish order. [L52]
A15: The easiest way to get back inside is by using X to invite you. Use: /msg X invite #channel_here and after you’ve managed to get in, op yourself and remove manually the channel modes. Sidenote: Running a tightly controlled access list and granting 400+ access to only trusted friends will save you from such kind of trouble. [L53]
Q16: Someone posted an objection to my channel that’s in Pending. He says I flood and my channel shouldn’t be registered because we are lamers. Will I get rejected? [L54]
A16: Before a CService Admin will hand-out a final decision, they will inspect carefully all the objections. If they are not true or based on facts, they will be ignored so have no fear if you haven't done anything wrong. [L54A]
Also you should consider that objections by defintions are negative so don’t post yourself an objection to motivate or defend yourself, it will only prolongate the total duration of the registration process. [L55]
We’ll pause the lesson, to allow you to direct your questions/doubts to your tutors [ph] [L56]
Q17: Please take action against this person who massbanned my channel and suspend him, he is very lame and swears us all the time. [L57]
A17: A massban in your channel is very well a result of the incorrect management of the access list. You, as channel manager or a 400+ admin there, are responsable for it because they got oped somehow or added to the channel access list. [L58]
CService is not a police station and it will not get involved in channel politics, because massbaning a channel is not an abuse. Tools to sanction people who commit them are: suspension of their access, access removal and kick/ban. [L59]
Q18: Hello CService, I am an op in a channel and suddenly the topic has changed to Manager has failed to login, a vote for a new mgr will be held. Level 400+ ops. What does it mean and why can’t I change it? [L60]
A18: This is a standard procedure that CService uses when a channel manager does not login to his username for 21 days. The channel gets locked and a topic will be visible to all that enter, claiming the absence of the manager as well as the upcoming vote to decide a new manager from the 400+ admins. [L61]
If you’re a 400+ admin and you add other channel admins to vote for you, don’t bother, the CService Admin handling the case already has a list with the 400+ admins prior to the channel getting locked. [L62]
If the channel is active and the 400+ manifest their interest of participating to the vote (by sending an e-mail to the address that will appear in the topic) the vote will be held and the details to it will be handled via e-mail message to those interested. If the channel is inactive and idle, it will be most surely purged when the CService Admin considers appropriate. [L63]
Another considerable aspect to this matter is addressed to the channel managers, that login to their username and come back to find their channel locked for a voting procedure. They can consider this measure as the first and last warning they’ll ever get. [L64]
After they’ve logged back in, the channel will be unlocked automatically within 24 hours and things will be back to normal. However, the channel will be marked by the CService Admins and the next time the manager fails to login, the channel may very well get purged without any further warnings. [L65]
As one clooful admin wisely put it: ”We are here to help our users get their channels registered and not to remove them...but dustbin emptying is necessary too” so please do not hold us responsable for your failure to login every 21 days, according to the RegProc AUP you’ve signed when you applied for the channel. [L66]
Q19: My IP was g-lined and I would like to know why. [L67]
A19: As inappropriate as this question may be it remains nevertheless a frequent asked question in #cservice. Before asking it you should consider that we do not handle the servers and do not get involved in server sanctions such as K-Lines/G-Lines etc. [L68]
The only way to get information about it, please send an e-mail to abuse@undernet.org including the sanctioned IP and the reason to it. Additionally you may join #ZT or #nastrand and ask if they can help you with it. [L69]
Q20: I'm being flooded through CTCP by many bots, is there a way to stop the flood? I'm tired of it already. [L70]
A20: Yes, there is, by activating silence via: /silence * - that will stop the flood via CTCP messages. The best way is to set-up an alias for it so you can use it easily when such a massive flood occurs. For help with aliases try #help or #mirc [L71]
Then you can report the flood to abuse-exploits@undernet.org with the proper copy/pasted documentation (timestamped logs of the attack). Do not attach documents to the e-mail! [L72]
For further information and protection please attend to the Opschool Part3 ”Floods and Protections” or even download the lesson from http://cservice.undernet.org/main/opschool/ [L73]
Q21: One of my friends named me supporter to his channel application. Now I have another friend asking me to support his channel too but I am afraid he will get rejected because of me. [L74]
A21: Not true. A person can support 2 channel applications at the same time, they won’t be jeopardised. If he’s active in both of them, there’s no need to be afraid. [L75]
Q22: Hello, I tried to change the topic to a channel, but it changed right back after a while. How can I change it too like that? [L76]
A22: One of the most important aspects of a channel’s look is it’s topic, which serves both as an announcement table as well as a welcome and introducing title to the channel’s main. There is a feature called AUTOTOPIC, which will force X to change the topic according to the DESCRIPTION you set. To enable these options you need to have 450 or higher access. [L77]
First you need to enable the autotopic performing: /msg X set #channel_name autotopic ON, then you need to set-up the description using: /msg X set #channel_name desc <text-goes-here>. This way X will re-set the topic if it’s changed manually, every 30 minutes with the condition of the channel not being idle. [L78]
Q23: I'm having problems with the channel limit. Enlighten me on this one please. [L79]
A23: You can use X to set the channel limit automatically, based on some variables that you can adjust to suit your needs (like channel being very large and highly traffic is conducted). [L80]
To enable the FloatingLimit you need to have 450 or higher access and perform: /msg X set #channel_here FLOATLIM On (now X will handle the limit according to the default variables). These variables are Floatgrace, Floatmax, Floatperiod and Floatmargin. [L81]
Q24: Can I make X op me whenever I join a channel? I’m tired of always using the op command. [L82]
A24: Yes you can. It’s called an AUTOMODE and it can be enabled to voice, op or none to one specific username added in the channel’s access list. To set it to op for instance, you need 400 or higher access and type: /msg X modinfo #channel_here automode <username-here> op [L83]
Note: If the strictop is not set, even a person with 1 access level can be set to autoop which can result in a massban performed manually. [L84]
Q25: When I save the channel modes through X it says -X- MODE for #channel is +tnRl. My question is how can I unsave +R ? [L85]
A25: +R (Registered) is a mode set by default by the server when you register the channel. It's purpose is to inform C(Chanfix, for more info visit http://chanfix.info/) that the channel is registered and therefore C should not score points for the ops there. The only way to quit +R is by Purging the channel (losing X priviledges in it). [L86]
Q26: Hi, how can I remove +D from my channel? [L87]
A26: Altough CService deals with registered channels and X commands, this is one of the most frequent asked questions. +D means Delayed Join Mode and is a channel mode that hides users on join until they talk on the main or get voiced/opped. To remove it you have to disable it first via : /mode #channel_name -D and if there are remaining hidden users it will set by default +d. [L88]
To view the remaining hidden users type : /names -D #channel_name and a list with them will appear on the status window. What remains is to voice them via : /msg X voice #channel_name nick1 nick2 nick3 etc and the +d will be disabled too. This is a very easy to set channel mode and a bit tricky to disable, used mostly on forum-type channels to prevent massive floods [L89]
Q27: Hey, I'm having problems with my browser, can anyone help me fix it ? [L90]
A27: We're sorry but we cannot help you with that however you may try asking in general help channels like #help or #userguide [L91]
This concludes our lesson for today :o) [L92]
The document was created by Panzer- and revised/accepted by kN (again your inspiration came in handy mate). [L93]
As a personal note... [L94]
I've had fun teaching this class, and I hope you learnt something during this session. [L95]
I've really enjoyed teaching here today... I hope you have enjoyed being here and learnt something that will make your time on the Undernet more enjoyable... I would like to thank you all for your patience and time spent here :) [L96]
Please stay tuned and visit #opschool for the upcoming lesson schedules. Also you’re all welcome to send us your suggestions/remarks to opschool@undernet.org [L97]
We will now open the channel up for general questions and please don’t be shy to state them :)



_________________
-kN
kn@undernet.org
Offline
 Profile  
 
 Post subject: Re: #opschool folder
PostPosted: Mon May 25, 2009 9:33 am 
Senior Cservice Admin
User avatar

Joined: Sun Jul 06, 2003 2:47 am
Posts: 564
Location: Hamilton, New Zealand
Topic Authorized by the Undernet Channel Services Committee.



_________________
xplora @ undernet.org
Past Co-ordinator
Undernet Channel Services Committee
Offline
 Profile  
 
 Post subject: Autoinvite X command and Forms updated
PostPosted: Sun Jun 14, 2009 6:48 pm 

Joined: Sun May 10, 2009 9:52 pm
Posts: 40
Location: HÖLLENSTRASSE
Hello to everyone who's currently watching the class, we hope you’ll enjoy your stay :) [L1]
Please sit back, turn your logging on and keep for later review. [L2]
This instructional script is brought to you by the Undernet Channel Service Committee. Please send comments, suggestions, or remarks to cservice@undernet.org [L3]
Today's class focuses on the new AUTO INVITE feature as a personal channel setting along with the Channel Service mailing lists. As an extra feature we will take a look at the E-Mail Change Form which is often used incorrectly or not fulfilled out. [L4]
I'd like to welcome you all to the Undernet Channel Service OpSchool (part V) "Autoinvite X command and Forms updated". [L5]
Now for the rules of the class... [L6]
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]
MiscTutor handles nicks beginning with numbers or characters such as ^, ], _, and so on, French is "AideTout", Spanish "YoAyudo", Romanian "EuAjut", Turkish "TürkçeYardým", Italian "Io_Aiuto". [L8]
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]
Please direct your questions through private message to the tutor who covers your name group. [L10]
The channel is moderated (+m) and the Delayed Join Mode is activated (+D) to lessen interruptions from join/part activity or nickname changes. [L11]
We’d like to remind you that you can enable your logging now using: /log <on|off> <window-goes-here> [-f filename-here]. [L12]
Do not message the instructor - My job is to keep the lesson flowing. Remember, you have tutors to answer your questions. [L13]
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]
The lesson will start shortly so grab your popcorn and drinks, turn off the TV and pay attention! :) [L15]
We will now take a brief pause in order for you to turn on your logging and locate your tutor. [ph] [L16]
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]
This in turn ends up creating these work-producing, expectation-shattering ideas, several of which are simplistically explained below. [L18]
SESSION A: AUTO INVITE command and it's characteristics. [L19]
Our coders were very busy and worked hard to create a solution for the age old problem of inviting yourself to certain registered channels that have set the "Invite Only" mode (+i) or a "Key" (+k) and which required everytime to invite yourself using the invite command (/msg X invite #channel_here) or doing the status command (200+ access needed) to see the key, or even to override the manual set channel limit. [L20]
To activate/deactivate this channel setting you need to have the same amount of access (100+) exactly as you needed previously for the normal invite command. As for the command itself the syntax is: /msg X modinfo #channel_here invite ON|OFF [L21]
Please note that you have to enable this feature for each particular channel you want to get invited to, upon login. Thusly X will send you the invite(s) right after you successfully logged into your CService username, allowing you to simply join those channels via /join #channel_here or by double clicking on the channel name(s) on the X invitation message. [L22]
You can check what channel(s) you turned invite on for,by checking your username info with: /msg x info <username>. Note: The reply you will get will be the same as before, with 2 differences. The first is the FLAGS SET line -"X- Flags set: INVISIBLE LANG=EN INVITE" and the second difference is that the channels you have set your autoinvite for will appear in bold: #opschool (450), #Helpless (200), #usernames (100), #cservice (100). Another sidenote: this INVITE flag remains private and won't show up when other users will use the info command on your username. [L23]
So in conclusion the auto invite feature: 1. Enables/disables autoinviting yourself via X on channels you choose to 2. It needs at least 100 access level in those channels to be performed. Remember: Autoinvite doesen't override the maximum channels limit, this continues to be set by each individual server. [L24]
Let's pause here so that you may ask questions to your tutors... and careful not to flood 'em :) [ph] [L25]
SESSION B: Mailing lists for various Channel Service Departments, each specialised on a different domain. [L26]
It's very important that guests classify correctly their situation and proceed accordingly when contacting one of these departments with their request. These are: cservice@undernet.org, cservice-abuse@undernet.org, X@undernet.org, usernames@undernet.org and below you can find detailed information and procedures for each one of them. [L27]
1. cservice@undernet.org - This is one of the busiest lists. In short, they answer in different languages and redirect e-mails to the appropriate lists. Also this can be used to redirect a guest that seeks out help in their native tongue on #CService but ops don't speak that particular language [L28]
2. cservice-abuse@undernet.org - This mailing list is used to report abusive registered channels. Abusive channels can be described those who proliferate: Botnets, Emechs, SDBots, DFGs, Hacked boxes, Spamming bots, Botlending, Pornography, Warez, Impersonation of official channels. [L29]
* To report such channels please bare in mind the following crucial aspects (which can ease our Staff work): Nothing can be reported and won't be taken into account without proof, this means you need to provide an explanation and try to copy/paste the essential evidence you got in your timestamped logs. The more the information, the more effective the report will be. Remember: IP's, /whois nickname, /msg x access #channel_here can be efficient detective tools when putting up such a report so don't hesitate to do a little spy work of your own. [L30]
* You can use any e-mail to send reports but we strongly encourrage guests to use their username e-Mail address as it allows CService personnel to identify them. Be aware that if you attach documents we *WILL NOT* open the e-mail nor take it into account, due to trojan/spyware/virus risks. [L31]
* As the name says, it can receive complaints of abusive conduct by our own CService Personnel. Again, without any logs or solid proof we will not take into consideration any reports. [L32]
* Please note that you shall be informed about the acknowledgement of email received but it is not mandatory that you shall be informed about the actions taken. In case no email regarding consequences is sent, please do not insist to find out the result either by spamming the list or joining #CService to demand further explanation. [L33]
3. X@undernet.org - Used both for manager changes aswel as E-mail changes. [L34]
* Manager changes - One can revert back temporary manager changes by mailing this list (He/She might want to be installed as channel manager before the period of temporary manager expires). Required information to do so: from the username's e-mail: username, verification question/answer, channel name, comments. [L35]
* E-Mail changes - If the e-mail in record doesn't exist anymore or it can't be accessed, get the form from http://cservice.undernet.org/docs, complete and send it to this address. It also serves for usernames suspended for being compromised/stolen (owner should use the E-Mail in records and provide as much info as he can about his/her stolen username). For further details please visit #usernames [L36]
4. usernames@undernet.org - People who's username have been suspended globally by a CService Administrator can use this list to ask for Unsuspension of their username. Procedure: from the username's e-mail account include the following: username, verification question/answer and explain the side of the story. [L37]
* We don't take any reports from network guests, don't bother to e-mail with reports of multiple usernames you might have spotted. The Undernet Channel Service Committee is aware of this problem and has a special department that's chasing abusers and sanctioning them on site so rest assured, we're on it! [L38]
* Again for details about usernames@undernet.org procedures please visit #usernames [L39]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L40]
SESSION C: E-Mail Change Form [L41]
The undernet Channel Services Committee keeps contact with the people owning an X username/channel via E-Mail addresses used to register that username. Without a valid E-Mail (not blocked due to abusing our registration system) you won't be able to register yourself a channel, transfer managership (temporary or permanent) or even being unable to support channel registration applications. In other words it's very important to have access to your E-mail in records. [L42]
There are a lot of users, who out of commodity or because they simply don't know the procedure, that cannot access their E-Mail addresses (or even have them expired). [L43]
The form that is used when requesting an E-mail change can be found at http://cservice.undernet.org/docs/ or viewtopic.php?f=1&t=10608. [L44]
Before filling it out you should be aware of the following instructions: [L45]
* Filling out completely is imperative, otherwise your request will not be processed. [L46]
* Use this form ONLY when you cannot login on the website with your username or you cannot use your username's old e-mail address anymore. [L47]
* If your old e-mail still works we will not take this request into consideration. [L48]
Before even preparing to fill this form out, you should create a new valid e-mail (either an ISP e-mail or any paid e-mail service). Why do we insist upon Provider/Paid E-mail? Simply because you can recover them almost surely by contacting their respective domain controllers, while free e-mails may be impossible to recover if compromised or lost. [L49]
The next step is filling it with the required info (detailed below) and copy/pasting the entire text in the body of your E-Mail editor and sending it to X@undernet.org with the subject: E-mail change request [L50]
Necessary fields: [L51]
a. Username: This is the username you have registered, do not confuse it with your nickname which is totally free on Undernet [L52]
b. Old E-mail Address: the address you previously had but which is no longer working. [L53]
c. New E-mail Address: Very obvious (should be your Internet Service Provider's supplied e-mail or a paid one) [L54]
d. Verification Question answer: (This is the answer to one of the questions below that you selected when you registered the username). [L55]
*- Please indicate which question you previously selected to answer: What's your mother's maiden name? / What's your dog's (or cat's) name? / What's your father's birthdate? [L56]
NOTE: If you have forgotten your verification question/answer, leave the fields blank, and explain the reason why you cannot remember at the Comments section [L57]
e. Channels you have access on: Simply use /msg x info <yourusername> and paste the access list X gives you for your username. [L58]
f. Comments (if any): Any information that you feel would help the request go smoother. [L59]
Finally after sending the e-mail allow some 24 hours for the change to be completed. It may take longer, don't panic, it will be done. Also please do not come begging online, it will be useless as we can't speed up the process. [L60]
For any doubts regarding this Form please visit #usernames [L61]
All of our Forms are translated into various languages. For example, the E-mail change Form is available in English,Spanish,Italian,French,Hungarian,Norwegian,Romanian,Turkish,URDU. Be sure to visit the Docs link on our website (or viewtopic.php?f=1&t=10608). Be sure to ask your respective tutor for help in that language. [L62]
We're currently updating our website so please for any X commands info don't hesistate to visit #CService where our busy volunteers will do their best to provide you with all the answers you need. Meanwhile visit the updated X commands at: viewtopic.php?f=1&t=10609 [L63]
The Opschool classes have also been compiled and you can download them by visiting the Undernet forum, link: viewtopic.php?f=1&t=10610 [L64]
We'll pause briefly in case you have any questions that you need to ask your tutor. [ph] [L65]
This concludes our lesson for today :o) [L66]
The instructional script was brought to you by the Opschool team (thank you guys for your efforts and dedication). Created by Panzer- and revised/amended by kN (his time spent and the struggle to update these documents are highly appreciated). [L67]
As a personal note... [L68]
I've had fun teaching this class, and I hope you learnt something during this session. [L69]
I've really enjoyed teaching here today... I hope you have enjoyed being here and learnt something that will make your time on the Undernet more enjoyable... I would like to thank you all for your patience and time spent here :) [L70]
Please stay tuned and visit #opschool for the upcoming lesson schedules. Also you’re all welcome to send us your suggestions/remarks to opschool@undernet.org [L71]
We will now open the channel up for general questions and please don’t be shy to state them :)



_________________
-kN
kn@undernet.org
Offline
 Profile  
 
Display posts from previous:  Sort by  
 Page 1 of 1 [ 7 posts ] 

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

cron