The Bots

Policy on acquiring a bot

Ours is not to pass moral judgement on any channel that requests a channel from BotService.Org. Rather it is to offer channel protection. Below is a list of guidelines in

• BotService.Org reserves the right to refuse any request for a bot to be in a channel, for any reason
• Only channels registered with Channel Services are eligible
• Only the owner (founder) of a channel may ask for a bot BotService.Org will supply no more than one bot per channel.
• BotService.Org will only supply 2 bots per founder. This means if their network allows them to have more than 2 channels, only 2 of those channels may be supplied with BotService.Org bots A bot will not be supplied if any of the following is true: 1. there is another bot in the channel, not counting the one supplied by Channel Services 2. the channel a channel not supported by the network (in other words if channel services wont register we won't supply a bot) 3. Warez/child endangerment or channels with illegal intent (i.e. trafficking of narcotics)* 4. the channel normally has any one of the following modes: +i, +l, +k 5. Under 18 restriction not enforced nor implied***

Clarification on channels served

*Warez being defined as illegal use of copyrighted software. MP3's is a gray area. Most MP3 sites request the user delete within 24 hours. We will supply that bot with a channel unless there is proof that warez are being traded

** Child porn channels includes sex channels that cater to younger users, with or without the intent to exploit that child, trading of photographs depicting child pornography, and adult sex channels that do not restrict their channels to prevent persons under the age of 18 from entering or enforcing such restrictions

***Adult style channels, whether they depict sexual situations in channel or not, are acceptable provided they have and enforce an "Under 18 restriction"

Policy on removing a bot

• BotService.Org reserves the right to remove our bot from a channel for any reason, and without prior notice.
• The owner of the channel may request the removal of our bot at any time, and BotService.Org will comply with that request as soon as possible.
• Changing a channel's name or owner will result in BotService.Org removing the bot; it can be re-applied for, however.
• Any of the following things will cause BotService.Org to remove a bot from a channel: 1. Deoping, kicking, or banning the bot, or removing its access from Channel Services 2. Kicking or banning BotService.Org members, which come to the channel to solve problems with the bot 3. Not co-operating with BotService.Org members who are trying to solve a problem with the bot in the channel 4. Using the bot for mass advertising, or for any activity that is in conflict with Channel Services policy 5. Abusing the bot 6. Losing control of the channel 7. Setting the channel +i, +l, or +k 8. Failing to impose/enforce an 18+ restriction on adult type channels
• Any bot removed for any reason must be sent to bservice@bservice.org documenting what happened and why the bot was removed.

Policy on Channel Responsibility

• Channel Owners are responsible for all events that happen on the channel – whether or not they are present
• BotService.Org is not accountable for anything that happens on the channel
• BotService.Org can set global bans within the bot and they will not be removed
• BotService.Org will remove bots from a channel that appears to be abandoned with out contacting the owner of the channel
• BotService.Org will not mediate any channel disagreements
• BotService.Org will not add any user to the bot except channel owner and channel services

Policy on Investigations

Networks with Local Administrators:

• Are responsible for their network requests for bots. This means that any application for that network will be sent to them
• Have the power to deny any application, or approve any channel, based on our policies
• Are responsible for either checking the channels themselves, or acquiring trained staff to do this task
• Are responsible for the installing of the bot to an approved channel, or acquiring trained staff to do this task
• Are responsible for providing new channel owners technical support with their bot, or acquiring trained staff to do this task
• The Administrator in charge of Applications reserves the right to approve/reject any incoming application for any network, regardless of Local Administrator presence.

Networks without a Local Administrator:

• All applications will be reviewed by the Administrator in charge of Applications
• Administrator reserves the right to assign applications for review to the Investigations Committee
• Administrator and the Committee have the power to reject, or approve any request, based on our policies
• Administrator has the power to assign any approved application to the Bot Installation Committee

Investigations Guidelines

In order to meet user requests for bots, the Investigation committee was formed. All Local Administrators are members of this committee by default, as well as chosen helpers.

• Follow the bot request policy as to what channels are eligible for a bot
• Verify that there are no bots in the channel. You can do this by versioning the channel or your judgement based on typical bot type greets
• When reviewing an application for acceptance or rejection the following fields must be filled out: Field Information to be filled out:

• Once you have decided to approve or reject an application, email the Application Administrator (taycie@bservice.org) with either "Accepted" or "Rejected" and the reason for reject. Make sure you include the application that was sent to you!!! VERY IMPORTANT!!
• The Admin in charge of Applications will contact the person requesting the bot as to the status

Policy on Installations

1. Only one channel owner per channel
2. Channel services bot/chanserv must be present
3. Don't add bots that have an @ next to their nick (the channel control bots)
4. Don't add bots that are part of the relay (most of these are the channel control bot with the exception of a few networks)
5. Don't add bots that are already in 7 channels (including the home channel)

Procedures for adding a bot to a channel

If application has been approved, and owner is present:

1. Select a bot for their channel a. Select from the +v bots in channel b. bots name cannot change
2. DCC the bot chosen a. have bot join channel using join command b. keep bot window open so you can double check owner/bot addition
3. Add owner to bot using the adduser command, making them 'chanowner'
4. Show owner how to: (watch for verification inside bot) a. set pass (/msg <botnick> pass <password> b. login to bot (/msg <botnick> login <password>
5. Have owner add bot to channel services bot a. must be set at level 449 (verify w/channel services bot) b. set autoops for the bot c. Password to set for the bot matches the bots nick (case sensitive) unless its Undernet, where passwords must be 6 characters long, then the pass is BotsBots for botnames under 6 letters
6. Add Channel services to bot to prevent conflict, unless not present in channel
7. Activate +seen (<botnick> chanset [channel] +seen) for the channel (Only global ops or higher can activate this feature)
8. Save database
9. Ask for a channel description while you have the owner there
10. Offer help using the bot, and explain channel levels a. can only add level below theirs b. give webpage addy for additional commands c. show how to get help using the bot (/msg <botnick> help [#channel])
11. After all completed, you can either fill out the form under "Update" on the staff website or you can Email bservice@bservice.org notifying the:

• Bot name that was installed
• A Channel Description for the website

Using initchan Command

This command only applies to ChatNet bots

1. Check application and verify owner
2. Verify K9 is present
3. Pick a bot
4. DCC bot
5. type .newchan add #channelname <key>a. keys should be entered as followed: date(yy,mm,dd) your initials (mix between cap/lowercase letters) (ex. 990408tAy) b. in the event the same bot is used on the same day, add a lower case letter to the beginning of the key (ex. a990408tAy)
6. Email the Application Admin with the approval and add include the following in the email: To activate your bot, and have it join your channel type: /msg <botnick> initchan {channel] <key>
7. .This command is case sensitive, so watch capitalization Verify later that owner has received his/her bot and all additions have been made to services bot etc. Also set +seen if the channel owner desires
8. After all completed, you can either fill out the form under "Update" on the staff website or you can Email bservice@bservice.org notifying the: Bot name that was installed A Channel Description for the website