Our rules

The growing popularity of Scoutlink makes it necessary to define some rules and regulations to maintain a safe and pleasant place for Scouts & Guides to Chat.

Violation of any of these rules, depending on severity, can result in anything from a verbal warning, time bans or even Blocking of an ISP from the Network. These rules and regulations are to protect Scoutlink, the Channels and the Users.

If you observe any violations of these rules, please copy the log of the chat and/or email a complaint to scoutlink@scoutlink.net or your country coordinator for further action.

Conduct

Please conduct yourselves according to the Scout Law, Oath/Promise. Many problems can be avoided by keeping this in mind.
You are responsible for anyone that you let use your computer or your nickname on the servers - no exceptions.

Idling

1. People that show up using the /lost command (so not in any channels) and are idle on the server for more than 5 hours, will receive a kill, with an appropriate message explaining why they have been killed (use English if the language is unknown).

2. Users that are idle in channels should be kicked by one of the operators in that channel, according to the channel’s idle rules. However, if an ircop comes across a user that appears to be 5 hours idle, who is sitting in a channel that does not have chanops in it, they should try to engage the person in conversation in that channel, as the person may just be sitting there waiting for people to chat to. If there is no response after 15 minutes, and the user is still idle, then you may kill them as per the rules of people who are idle on /lost.
3. If the user auto-reconnects there will be set a short g:Line of 5 minutes. This is purely to defeat the auto rejoin, and is not a punishment. Please include an appropriate message telling them why they have been g:lined (and for how long), and asking them to turn off auto rejoin. Before setting a g:line, please check that the user has not manually reconnected first, by sending them a private message.

4. If a user auto-reconnects a second time, you do not need to g:line again. They will be killed again in 5 hours if they remain idle. However, if you suspect that a user is regularly coming online and idling for some purpose that is not acceptable on a Scout Network, or someone seems to be online and never chatting, then please contact Council for advice. Do *not* just set a longer g:line because of idling.
5. Authorised Bots that are showing up as idle excessively should not be killed but a message sent to the bot owner, or TT if unsure, so they can check that the bot is still working correctly.

6. Please note, these rules also apply to ops who are idle to make it fair to everyone who uses ScoutLink. J

7. In some circumstances it may be necessary that IRCops and Tech Team members may need to be idle for an extended period of time (good reasons for this could include things like a Techie searching for a bug in software that crashes ircd software that happens under strange conditions, or IRCops being idle during JOTI in #services.log for running the stats script). If you need to be idle on the server for a period of time, with good reason, then send an e-mail to the team with the reason, and the expected end-date, so that other ops know to leave you alone. This should be a fixed date and not just ‘forever’.

 

Channels

Please refer to the Channels page HERE

Bots, Scripts and Hostmarks

No unauthorized bots or scripts are permitted. Spoofed hostmarks will not be tolerated.

Popups / Aliases / IRC Client programing

No autogreets are permitted.
As a guideline - Limit all popups to 2 to 3 lines. (a line is 45 Characters long)

Sounds

No random wavs or midis are to be played on channels. They may be played if they are part of the conversation, such as hello.wav. If you wish to share your sounds with others, #sounds is a channel designed for that purpose. Invite others into #sounds and have fun.

Language

No abusive or foul language will be permitted. Some channels handle swearing strictly, so beware :)

Flooding

No flooding by type, colour or sound will be permitted.

Patch Trading

We realize that patch trading is a normal part of Scouting. However, please keep your requests to a minimum and do not annoy everyone who joins the channel. A DCC Chat request or query window would be preferable. There is a #collectors channel specifically for trading.

FServers

No open or public fservers are permitted.

Personal Info

PLEASE do not give out your phone number, address, e-maiil or any other personal details in the main channels.

IRC Clients

IRC clients such as mIRC, Pirch, IRCle, ircII, differ greatly. Some see colour and graphics, others do not. Please be considerate, and use colours sparingly.