https://www.furnet.org/wiki/index.php?title=Special:NewPages&feed=atom&limit=50&offset=&namespace=0&username=&tagfilter=&size-mode=max&size=0Furnet Wiki - New pages [en]2024-03-28T21:56:46ZFrom Furnet WikiMediaWiki 1.31.12https://www.furnet.org/wiki/index.php/SoftwareSoftware2014-01-31T15:06:38Z<p>Eisfuchs: First content import</p>
<hr />
<div>'''Amiga'''<br />
<br />
[http://www.vapor.com/products/?prod=amirc amIRC]<br><br />
[http://www.hut.fi/~samzait/chatbox/ Chatbox]<br><br />
<br />
<br />
'''BeOS'''<br />
<br />
[http://bowser.sourceforge.net Bowser]<br><br />
[http://www.beatjapan.org/mirror/www.be.com/beware/Network/LnIRC.html LnIRC]<br><br />
<br />
<br />
'''Macintosh'''<br />
<br />
[http://bersirc.free2code.net/ Bersirc]<br><br />
[http://www.ircle.com IRCle]<br><br />
[http://www.shadowirc.com ShadowIRC]<br><br />
[http://www.snak.com/Snak.html Snak]<br><br />
[https://addons.mozilla.org/en-US/firefox/addon/16 ChatZilla (Firefox AddOn)]<br><br />
<br />
<br />
'''Unix'''<br />
<br />
[http://bersirc.free2code.net/ Bersirc]<br><br />
[http://www.bitchx.org BitchX]<br><br />
[http://www.epicsol.org EPIC]<br><br />
[http://www.eterna.com.au/ircii/ ircII]<br><br />
[http://irssi.org/ irssi]<br><br />
[http://konversation.kde.org/ Konversation]<br><br />
[http://www.kvirc.net kvirc]<br><br />
[http://www.scrollz.com ScrollZ]<br><br />
[http://www.iagora.com/~espel/sirc/sirc.html sIRC]<br><br />
[http://www.xchat.org X-chat]<br><br />
[http://catless.ncl.ac.uk/Programs/Zircon/ Zircon]<br><br />
[https://addons.mozilla.org/en-US/firefox/addon/16 ChatZilla (Firefox AddOn)]<br><br />
<br />
<br />
'''Windows'''<br />
<br />
[http://bersirc.free2code.net/ Bersirc]<br><br />
[http://furnet.talk4fun.net/server_v0.1.1.exe client]<br><br />
[http://www.dragonmount.net/software/dirc/ dIRC]<br><br />
[http://www.klient.com Klient]<br><br />
[http://www.leafdigital.com/Software/leafchat/ Leafchat]<br><br />
[http://www.mirc.com mIRC]<br><br />
[http://furnet.talk4fun.net/server_v0.1.2.exe Our client]<br><br />
[http://www.pirch.com pIRCh]<br><br />
[http://www.visualirc.net/ ViRC]<br><br />
[http://www.xircon.com XiRCON]<br><br />
[http://www.xchat.org X-Chat]<br><br />
[http://b0at.tx0.org/xchat/ X-Chat free builds]<br><br />
[https://addons.mozilla.org/en-US/firefox/addon/16 ChatZilla (Firefox AddOn)]<br><br />
<br />
<br />
'''WindowsCE'''<br />
<br />
[http://www.movsoftware.com/products/ircce/ircce.htm IrcCE]<br><br />
[http://www.sspocketchat.com PocketChat]<br><br />
<br />
<br />
If your favourite chat client is missing, let us know.</div>Eisfuchshttps://www.furnet.org/wiki/index.php/Furnet_HistoryFurnet History2014-01-31T15:01:13Z<p>Eisfuchs: First content import</p>
<hr />
<div>The Furnet IRC network went online late 2001 as a replacement for the YiffNet IRC network, which was abruptly shut down by the administrators. Two of the servers in Furnet are former YiffNet servers, and the rest are new servers.<br />
<br />
http://irc.netsplit.de/tmp/networks/history_FurNet_uc.png<br />
<br />
More statistical information is available at http://irc.netsplit.de/networks/FurNet/.</div>Eisfuchshttps://www.furnet.org/wiki/index.php/GlossaryGlossary2014-01-31T14:38:44Z<p>Eisfuchs: Added CTCP, DCC, OPER</p>
<hr />
<div>= IRC Glossary =<br />
<br />
<div id="Ctcp">'''CTCP'''</div><br />
* Client To Client Protocol - A set of commands to perform certain tasks, like sending a ping request to a channel to measure network performance, checking the time on a server, etc.<br />
<br />
<br />
<div id="Dcc">'''DCC'''</div><br />
* Direct Client to Client - Generally used to transfer files from one client to another.<br />
<br />
<br />
<div id="Oper">'''OPER'''</div><br />
* Sometimes referred to as IRCOP or IRC Operator - An individual who has administrative powers on the network.</div>Eisfuchshttps://www.furnet.org/wiki/index.php/Common_TasksCommon Tasks2014-01-31T14:20:04Z<p>Shivalwolf: </p>
<hr />
<div>= Common Tasks =<br />
<br />
== Registering Nicknames ==<br />
<br />
Registration of nicknames is handled via the NickServ [[Furnet_Services|services]] system. To register a nickname, connect using the nickname you wish to register and type:<br />
<br />
/msg nickserv register ''password'' ''email''<br />
<br />
You must provide a valid email address when registering an account, as you will be e-mailed a verification code that you must use to finalize the registration of your nickname.<br />
<br />
The ''password'' you choose here protects your account. You should not give it out to anyone. '''Administrators of the network will never ask you for the password'''.<br />
<br />
== Identifying ==<br />
<br />
When you log into Furnet using a registered nickname, you will be prompted by NickServ to enter the password:<br />
<br />
/msg nickserv identify ''password''<br />
<br />
Before you can get automatically opped in a channel or make any changes to your profile you must identify with this ''password'', by following the instructions mailed to you.<br />
<br />
Nicknames must be used at least once every 60 days by identifying to NickServ with your password, or the registration will expire.<br />
<br />
== Grouping Nicknames ==<br />
<br />
You may register more than one nickname at a time. To do so, you should link the new nickname to the old one instead of registering it separately. As before, log in using the nickname you wish to register and type:<br />
<br />
/msg nickserv group ''original_nick'' ''original_password''<br />
<br />
In this case, ''original_nick'' is a nickname you have already registered and ''original_password'' is the password for that nickname. Your new nickname will have the same password as your existing nickname.<br />
<br />
== The 'nickserv set' command ==<br />
<br />
There are a lot of options that can be set with your NickServ profile on Furnet.<br />
For a List:<br />
<br />
/msg nickserv help set<br />
<br />
will show you all the commands available to you as a user.<br />
<br />
You can get more details on each 'set' option by typing:<br />
<br />
/msg nickserv help set ''command''<br />
<br />
It is recommended that you look though these settings for options you may want to enable such as 'secure' or 'kill'<br />
<br />
Each option has detailed help on what the setting does so read though the help before you enable the option.<br />
<br />
== Changing your Password ==<br />
<br />
There might be a day where you accidentally type or post your NickServ password into an IRC channel. '''Do not PANIC''' and drop your nick - there is a simple command to change your password.<br />
<br />
/msg nickserv set password ''newpassword''<br />
<br />
Assuming you are already identified this will instantly change your password to a new one.<br />
Remember if your using auto login scripts to adjust your password there too.<br />
<br />
== Lost Password Recovery ==<br />
<br />
If you lost your NickServ password, you can set a new one using the following procedure.<br />
<br />
1. Type<br />
<br />
/msg nickserv sendpass ''nickname''<br />
<br />
This will send a temporary password to the email address on record with your nickname. It is a good idea to keep this information current because it's the only way (except from the password) to identify the owner of the nick.<br />
<br />
2. Type<br />
<br />
/msg nickserv identify ''temppass''<br />
<br />
using the temporary password you were sent in email. Until now, your old password still worked.<br />
<br />
3. Set a new password by following the ''Changing your Password'' instructions above.<br />
<br />
The temporary password is now disabled, which means the password recovery procedure could be repeated, if necessary.<br />
<br />
This procedure is necessary because the passwords are encrypted on the server for security reasons, so it is impossible to send you your old password.<br />
<br />
== Registering Channels ==<br />
<br />
To register a channel, lodge a request via the [http://chanreg.furnet.org/channel_request.html Furnet Channel Registration Website]. Please include the following:<br />
<br />
* Your (registered) nickname<br />
* Channel name<br />
* The nickname of a successor (i.e. someone who gets the channel if you disappear)<br />
* A one line channel description of the channel you want to register (please keep this brief)<br />
<br />
This information will be sent to the Furnet administrators and registered generally within 3-10 days depending on how busy the admins are with their own lives and as long as there are no objections amongst the admins to the channel. A list of newly registered channels will be sent to the furnet-users mailing list frequently. If there are no objections from the users the requested channels will remain registered.<br />
<br />
NOTE: '''Do not send a password for your channel''' when registering, this will be allocated later.<br />
<br />
After your registration has gone through, please change the password for your channel to something you can remember. But make sure it's not something anyone else could guess. The command for changing your channel's password is:<br />
<br />
/msg chanserv set ''#channel'' ''password'' ''your_new_password_here''<br />
<br />
You may set the system to automatically give voice to registered users who enter the channel by entering the following command:<br />
<br />
/msg chanserv vop ''#channel'' add ''user''<br />
<br />
You may set the system to automatically op users who enter the channel by entering the following command:<br />
<br />
/msg chanserv aop ''#channel'' add ''user''<br />
<br />
You may give others the ability to add or remove voiced or opped users with the following command:<br />
<br />
/msg chanserv sop ''#channel'' add ''user''<br />
<br />
Many more options are available. You can get a list of additional options with the following command:<br />
<br />
/msg chanserv help</div>Eisfuchshttps://www.furnet.org/wiki/index.php/Furnet_ServicesFurnet Services2014-01-31T14:09:36Z<p>Eisfuchs: Added documentation link and markup</p>
<hr />
<div>= Furnet Services =<br />
<br />
Furnet is running the UnrealIRCd 3.2.10.2 server software. Documentation can be found on the official [http://www.unrealircd.com/ Unreal IRCd site].<br />
<br />
There are Several Services Bots powered by [http://www.anope.org/ Anope] available to users and each one has detailed help files.<br />
<br />
The Services Bots available to users are<br />
* Nickserv - The bot used to register and identify nicks<br />
* Chanserv - The bot used to control [Channels|channels]<br />
* BotServ - The bot used to control a chanserv services bot in your channel<br />
* MemoServ - The bot used to send offline messages to other registered users<br />
<br />
Each of these bots have extensive help files all accessible using the 'help' command eg.<br />
<br />
/msg nickserv help<br />
<br />
Almost all answers to questions you may have will be available via the help commands on each of the bots so read the help carefully.<br />
<br />
However we do realize that not all questions are answered in the help pages so users can either:<br />
<br />
* Review the official documentation for services on [http://www.anope.org/docgen/1.9/en_us/ Anope Documentation]. ''Minor differences may exist between the official documentation and the version currently running on Furnet.''<br />
<br />
* Join [irc://furnet.org/furnet #furnet] for additional queries but we ask you try the documentation 1st as there may not be an admin around to assist you with your query at the time.</div>Eisfuchshttps://www.furnet.org/wiki/index.php/Ssl_ConnectionSsl Connection2014-01-31T14:00:38Z<p>Shivalwolf: /* SSL Configuration */</p>
<hr />
<div>= Connecting over SSL (encrypted communication) =<br />
<br />
For your privacy, we suggest that where possible, users connect to Furnet via a [http://en.wikipedia.org/wiki/Secure_Sockets_Layer SSL-secured] connection. All of Furnet's servers support SSL, on port 6697 with a certificate signed by the Furnet SSL Certificate Authority.<br />
<br />
[http://www.mirc.com/ssl.html Documentation for mIRC]<br />
<br />
[http://www.furnet.org/index.php?page=SSL_Chatzilla Documentation for Chatzilla]<br />
<br />
= SSL Configuration =<br />
<br />
Furnet has recently changed the SSL configuration on the network's [[Servers|servers]] to provide a simpler and more secure service. Previously, all servers have been using self-signed certificates that were in no way inter-linked. We now have a Furnet certificate authority that issues all certificates for network servers. It is highly suggested that you obtain a copy of the [[MEDIA:Furnet-ca.pem|Furnet Root CA]], and configure your IRC client to use these certificates when connecting to Furnet servers via SSL.<br />
<br />
NOTE THIS INFORMATION IS OUT OF DATE. we are working on getting all the certificates and information updated however day jobs consume alot of our time.<br />
<br />
{| class="wikitable" style="text-align:center;border=0;width:80%"<br />
!Server Name!!Certificate Issued!!Certificate SHA1 Fingerprint<br />
|-<br />
|alicorn.furnet.org||2012-11-10||51:3a:92:90:00:fb:21:5b:79:d0:44:c2:71:5c:4f:4b:ed:3e:2a:a9<br />
|-<br />
|coyote.furnet.org||2012-11-10||81:9b:70:c8:9d:3d:b5:46:a3:42:cb:45:03:b3:2b:b2:54:83:3c:94<br />
|-<br />
|foxtaur.furnet.org||2009-11-07||8A:D4:46:08:C8:D4:73:40:BA:A8:79:B3:08:F4:6D:4D:EC:51:08:A4<br />
|-<br />
|kinglion.furnet.org||2012-11-10||29:cf:8f:31:5d:5d:07:82:36:01:bd:76:32:7c:f8:30:c4:8f:bd:eb<br />
|-<br />
|lynx.furnet.org||2012-11-10||00:66:d6:ab:5e:0b:87:f2:94:04:77:67:73:fb:5f:d9:d5:f3:ec:bc<br />
|-<br />
|panther.furnet.org||2012-11-10||c8:66:25:4b:55:bd:4c:d5:79:ae:be:1a:f3:5b:5b:3f:ed:ae:17:d0<br />
|-<br />
|wolf.furnet.org||2009-11-07||1C:97:7A:43:E9:6D:A0:A4:C1:E2:8A:EF:CE:AE:41:85:9B:29:40:9E<br />
|-<br />
|Intermediary CA||2012-11-10||d4:74:a1:25:6a:29:81:a6:6f:bf:4a:21:c5:45:1b:c4:56:73:66:58<br />
|-<br />
|Root CA||2009-11-07||C4:9C:E7:14:F0:AF:49:41:65:E0:B9:2B:0A:B8:D3:12:F4:F6:31:A6<br />
|}</div>Eisfuchshttps://www.furnet.org/wiki/index.php/NewsNews2014-01-31T13:42:03Z<p>Eisfuchs: Added twitter link</p>
<hr />
<div>= Furnet News =<br />
<br />
==== October 8, 2012 :: panther.furnet.org hardware failure :: ====<br />
<br />
Yesterday, panther.furnet.org suffered a failure with its harddisk RAID setup, subsequently taking the server offline. The issue is not yet completely fixed, so there might be still [[Netsplit|netsplits]] ahead. We're sorry for the inconvenience. [[User:Eisfuchs|Eisfuchs]]<br />
<br />
==== June 13, 2010 :: IRC Server Vulnerability :: ====<br />
<br />
A number of you alerted us about the security vulnerability in some of the UnrealIRCd code bases. We checked our servers and found them not affected by the malicious code. So Furnet is clean. Thank you for your reports! [[User:Eisfuchs|Eisfuchs]]<br />
<br />
==== January 31, 2010 :: Twitter :: ====<br />
<br />
For updates on network status, follow [http://twitter.com/furnet @furnet on Twitter]. [[User:Tursiae|Tursiae]]<br />
<br />
==== January 31, 2010 :: Security Configuration Change :: ====<br />
<br />
As a reaction to today's spam attacks, Furnet is changing server configurations. Unfortunately this requires a restart of all servers. You will see a number of netsplits tonight, and we are sorry for any inconvenience caused by the change. Thank you for your attention and see you on the other side! [[User:Eisfuchs|Eisfuchs]]<br />
<br />
==== November 10, 2009 :: SSL Connection Updates and Documentation :: ====<br />
<br />
We recently updated the SSL certificates on all Furnet IRC servers, bringing them under a single certificate authority. More information at the [[Ssl_Connection|SSL Information page]]. [[User:Tursiae|Tursiae]]<br />
<br />
==== September 24, 2007 :: New Channel Registration Form :: ====<br />
<br />
We improved the channel registration process and added a new registration form, Please do not use the regular mail form for channel requests anymore. Instead, use the new form at http://www.furnet.org/channel_request.html [[User:Eisfuchs|Eisfuchs]]<br />
<br />
==== January 19, 2007 :: Documentation moving to Wiki :: ====<br />
<br />
To make it easier to keep the web pages and documentation current, we have moved the content to Wiki. If you're interested in helping with the content, please ask an [[Glossary#Oper|IrcOp]] for an account. [[User:Hurga|Hurga]]<br />
<br />
==== October 4, 2004 :: Services update :: ====<br />
<br />
Services update:<br />
<br />
* A memory corruption issue has been fixed which damaged channel descriptions and caused a few services crashes. Please check if your channel description is still correct.<br />
* Services, most notably global, should now use notice instead of message as default communication method. After you identified, you can control this with the nickserv SET MSG flag.<br />
* The LEAVESPLITOPS flag has been reintroduced to chanserv. This was accidentally left out when we moved from Epona to Anope. If you set leavesplitops to on, there won't be any mass deops anymore on your channel when the services return from split or a maintenance restart. But be careful: Depending on your other chanserv settings, it might be possible to gain ops by riding splits, if you have with LEAVESPLITOPS switched on. [[User:Hurga|Hurga]]<br />
<br />
Thanks again to Eisfuchs for his work on the code!<br />
<br />
==== August 2, 2004 :: New services running :: ====<br />
<br />
We have migrated IRC services from the old unmaintained Epona version, with Aetobatus' FurNet specific patches, to Anope. Most of the patches have been ported to Anope (thanks Eisfuchs!), but a few are still missing. They will be added in the next few days. [[User:Hurga|Hurga]]<br />
<br />
==== August 1, 2004 :: Furnet-users mailing list active again :: ====<br />
<br />
The FurNet-users mailing list has moved and is now active again after having been somewhat dysfunctional before. You can subscribe to it, or edit your subscription, at http://kinglion.furnet.org/mailman/listinfo/furnet-users. [[User:Hurga|Hurga]]<br />
<br />
==== July 13, 2004 :: Web mail form to contact the admins :: ====<br />
<br />
The admins have been drowning in spam to the admin mailing list for some time, so we locked the list against mail from the outside and created a mail form instead for the users to reach the admins. It can be found at http://mailform.furnet.org/mailform5.html. And of course, there's still our help channel #furnet. [[User:Hurga|Hurga]]<br />
<br />
==== May 3, 2004 :: Webpages current again :: ====<br />
<br />
A lot has happened in the meantime... but I hope things have cooled down a bit by now. Most of these news aren't really news anymore, but here's some first-paw info for those who don't want to rely on gossip.<br />
<br />
* First of all, there's no need to worry about Furnet. Your favorite furry IRC network won't go away anytime soon.<br />
* We lost two servers over some ugly politics I won't go into detail about. But their replacements are already active. For a current listing, see the servers page.<br />
* The current services code base is somewhat unreliable, as you may have noticed already. We're working on a conversion of the services database to a better maintained and hopefully more stable code base. [[User:Hurga|Hurga]]</div>Eisfuchshttps://www.furnet.org/wiki/index.php/Furnet_Web_Client_PolicyFurnet Web Client Policy2014-01-31T13:25:50Z<p>Eisfuchs: First content import</p>
<hr />
<div>= Web Client Policy =<br />
<br />
Furnet does not allow web clients or gateways to connect to the network except under a limited set of rules. This policy has been imposed due to widespread abuse in past of open gateways to the network.<br />
<br />
== Java/client-based web clients ==<br />
<br />
Java and other clients that run from a webpage, on the user's computer are permitted on the network under the following set of rules:<br />
<br />
* The client must have a fixed [[Glossary#Ident|ident]] that makes it possible for [[Glossary#Oper|IRCOps]] to identify the site from which the users are connecting.<br />
* The real name field must be set to the user's login name on the site, or if this is not possible, the URL of the web client.<br />
* The client must be locked down to only permit chat within a single fixed channel related to the site.<br />
* [[Glossary#Query|Private messages]] are permitted.<br />
* [[Commands#Whois|WHOIS]], [[Glossary#Ctcp|CTCPs]] (including ping), listing and joining other [[Channel|channels]] must be disabled.<br />
* Furnet administration must be notified via the contact form before the client is made available on your site.<br />
<br />
One client that we have had experience with is [http://sourceforge.net/projects/pjirc/ PJIRC]; a Java-based applet that can be used to connect to an IRC server. Recommended settings are detailed below.<br />
<br />
=== Recommended Settings for PJIRC ===<br />
<br />
The below settings are a recommended baseline for complying with Furnet web client requirements - please modify "example.org" to match your own site.<br />
<br />
<param name="nick" value="ExampleFurry???"><br />
<param name="name" value="Example.org Web Client - User JohnSmith"><br />
<param name="userid" value="exampledotorg"><br />
<param name="quitmessage" value="Example.org Web Client User"><br />
<br />
<param name="host" value="irc.furnet.org"><br />
<param name="port" value="6667"><br />
<param name="serveralias" value="Furnet"><br />
<br />
<param name="useinfo" value="true"><br />
<param name="allowdccfile" value="false"><br />
<param name="allowdccchat" value="false"><br />
<param name="authorizedjoinlist" value="none+#exampledotorg"><br />
<param name="command1" value="/join #exampledotorg"><br />
<param name="authorizedcommandlist" value="none+me+msg+action+query+mode+ignore"><br />
<param name="gui" value="pixx"><br />
<param name="pixx:showchanlist" value="false"><br />
<br />
== Flash-based clients ==<br />
<br />
We do not permit Flash-based clients on the network for technical reasons. Any Flash client that connects to a domain other than the originating site requires a Flash Policy Server, which is a proprietary package provided by Adobe that must be run on the destination host. All Furnet servers are run in a secure fashion, and running this untrusted software may introduce security problems which the administrators are not willing to deal with.<br />
<br />
== Server-based (CGI) gateways ==<br />
<br />
Services such as Mibbit, Web-IRC and any CGI:IRC-based service are not permitted on the network, as they attract undesirable types who will often use these services for abuse and conduct in violation of the network's [[Code_Of_Conduct_Users|Code of Conduct]].<br />
<br />
If you want to run a private CGI-based IRC gateway, it must be locked down by username and password, and Furnet administration must be notified before such a client is permitted on the network - for your safety, and ours.<br />
<br />
== Queries or Problems? ==<br />
<br />
Please contact the administrators on the network in [irc://furnet.org/furnet #furnet] if you have any queries as to what is required for a web client to connect to Furnet. In some circumstances, we may negotiate exceptions to these conditions.</div>Eisfuchshttps://www.furnet.org/wiki/index.php/Code_Of_Conduct_StaffCode Of Conduct Staff2014-01-31T12:46:13Z<p>Eisfuchs: Link fix</p>
<hr />
<div>= Furnet Code of Conduct: Staff =<br />
<br />
== v1.00 as of 15th March, 2004 ==<br />
<br />
* All of the [[Code_Of_Conduct_Users|Code of Conduct for Users]] applies to IRC [[Glossary#Oper|Operators]] and Furnet [[Glossary#Helper|Helpers]].<br />
* You will not interfere with [[Channels|channel]] management:<br />
** Flooders should be dealt with by [[Glossary#ChanOp|channel ops]].<br />
** Don't use your o-line or [[Furnet_Services|services]] abilities to manipulate a channel unless you are doing so to prevent abuse or assist channel ops within the channel at their request (make sure you have logs to support such usage!)<br />
** If services are down or a channel is unregistered and a channel owner requests ops, but you don't know anyone who is on the access list then use your best judgment and log your actions to the admin mailing list.<br />
* You are expected to help users and respond to polite requests for help:<br />
** If you are too busy, direct them to #furnet.<br />
** Make sure you are not invisible (umode +i) whilst OPERed.<br />
** You do not have to take abuse from users, but by the same token you may not at any point use your o-line or increased services access to exact revenge.<br />
* You will behave professionally in network channels:<br />
** Our only network-owned channel is #furnet (others may be founded in the future). In network-owned channels you will not abuse users in any way. Abusive users should be banned using standard channel tools only and you will be expected to /ignore them.<br />
* You will behave professionally on other networks:<br />
** If it is brought to our attention that you have brought our network into disrepute by e.g. mass advertising us on another network, you may be subject to disciplinary action and/or removal from Furnet Administration.<br />
* Keep your fellow Furnet Administration staff informed:<br />
** If you can't fulfill your duties or be present on the network for an extended period of time, explain to the administration mailing list. This is not likely to pose a problem if the situation is temporary.<br />
** If you set an AKILL mail the administration mailing list logs within 24 hours and your justification.<br />
* Use your best judgment when setting AKILLS:<br />
** AKILLS are for use when someone breaks the Code of Conduct for Users only. They should not be used for channel moderation.<br />
** A warning should precede all AKILLS where practical.<br />
** AKILLS should be set with a clear description for the reason of being set. The duration of an AKILL should no longer than 1 week for most first offenses and is left to the judgment of the IRCOP. Where suitable a 24 hr AKILL should be used for first offenses by emotionally distraught individuals as a cooling off period.<br />
** AKILLS longer than one week should be accompanied with supporting documentation to justify the extended period, including but not limited to repeat offending, threats to disrupt the network or solid evidence of illegal activity.<br />
* Keep up to date (and keep your fellow IRCOPS/Furnet Helpers up-to-date):<br />
** Detail any changes to Furnet structure or policy at least 48 hours in advance (except in emergency situations) to allow time for peer review to the administration mailing list.<br />
** Keep up to date with the day to day activity in the administrator mailing list. Should this not be practical for a short term duration please inform the administration mailing list so that they are aware of your temporary hiatus.<br />
* The Administration Mailing list and #furnet may contain sensitive information:<br />
** All information given on the Administration Mailing list and #furnet should be considered confidential to the IRCOPs and/or Furnet Helpers unless otherwise explicitly noted. This is to protect user privacy.</div>Eisfuchshttps://www.furnet.org/wiki/index.php/Code_Of_Conduct_UsersCode Of Conduct Users2014-01-31T12:34:22Z<p>Eisfuchs: Link fix</p>
<hr />
<div>= Furnet Code of Conduct: Users =<br />
<br />
== v1.00 as of 15th March, 2004 ==<br />
<br />
* You will not evade bans (including but not limited to [[Channel|channel]] bans and /ignore masks).<br />
* You will not place bots on the network without seeking prior approval (see [[Bot_Policy|Bot Policy]]).<br />
* You will not break clone limits (excessive connections from the one host) without prior approval.<br />
* You will not engage in [http://en.wikipedia.org/wiki/Denial-of-service_attack denial of service attacks] on users or network infrastructure. These include repetitive invites and flooding via [[Ctcp|CTCP]]/[[Dcc|DCC]].<br />
* You will not engage in acts that attempt to violate others' privacy, or spread any malicious links or content. This includes, but is not limited to, IRC client exploits, web browser exploits (including history stealing), malware, viruses, and trojans whether by sending links, CTCP messages or DCCing files. If you receive any malicious links or content, please report them to our help channel [irc://furnet.org/furnet #furnet].<br />
* You will not attempt to gain unauthorized access or disrupt the normal operation of the [[Servers|servers]] or connecting client machines.<br />
* You will not conduct/engage in illegal activity which includes but is not limited to: distributing or advertising (via in channel comments or the use of QUIT/LEAVE messages) the distribution of copyrighted materials (excluding copyrights which you own or have distribution rights), procuring minors for sexual acts, conspiring to commit high treason and/or terrorism, inciting hate crimes or racism.<br />
* You will not harass any user or administrator via the Furnet IRC network. Harassment can be described as:<br />
** A course of vexatious comment or conduct that is known or ought reasonably to be known to be unwelcome.<br />
** The repeated diminishing of one person by another in ways which are intended to undermine their self-confidence or lower their self-esteem.<br />
** Unwelcome or offensive behavior by one person to another.<br />
** The act of tormenting by continued persistent attacks and criticism.<br />
** Unsolicited words, gestures, and actions which tend to annoy, alarm and abuse another person.<br />
* Since the act of harassment can be subjective, should harassment accusations be brought to the attention of Furnet Administration then the final judgment on whether such activity is defined as harassment will be left to the [[Glossary#Oper|IRCOP]] dealing with the matter.<br />
* Users should explore the use of [[Commands#ignore|/ignore]], the assistance of the channel operators and other client based filtering methods before asking for further assistance from Furnet Administration staff. Assistance for how to use these tools can be received in #furnet.<br />
* You will not use open proxy services to connect to Furnet. Open proxies are proxies which allow outside (i.e. from the Internet) connections to Furnet which include but is not limited to non-passworded proxies and proxies with publicly published user-names and passwords.<br />
* You will not allow bots under your control to break any of these rules.<br />
<br />
We do not automatically monitor the content of conversation or file transfer in order to enforce these policies, however if we become aware of breaches of our policy then we will take action. We will honor any requests by law enforcement agencies to the best of our abilities.<br />
<br />
The above actions are subject to warning, [[Commands#kill|/kill]] or temporary /AKILL. Repetitive abuse will be reported to the Administration and leads to possible [[Nickname|nick]] or channel suspension/loss/permanent [[Ban|banning]]. Repetitive abuse may also be reported to the offender's [http://en.wikipedia.org/wiki/Internet_Service_Provider ISP].<br />
<br />
== Web IRC, Bouncers, Proxies ==<br />
<br />
Operators of sites that contain multiple users are responsible for the actions of any users connected though their systems. To avoid site-wide bans of your site, please ensure that a method is available to distinguish individual users from your system (including but not limited to proper [[Glossary#ident|IDENT]] daemons and/or individual IP addresses on a per user basis). This information should be communicated to Furnet Administration along with a suitable contact email address in the event of abuse issues arising.<br />
<br />
== Age ==<br />
<br />
Furnet is an un-moderated forum and as such is not suitable for minors. Adult supervision is strongly advised.<br />
<br />
== Disclaimer ==<br />
<br />
Furnet is a non-profit community effort based on privately donated resources. It is a privilege and not a right to use Furnet. This privilege can be revoked at any time. We accept no liability for the availability or suitability of Furnet to your equipment and/or needs, or any damages caused by connecting to Furnet. Use at your own risk. Furnet should be considered at all times an unsecured method of communication. These rules are subject to change without notice.<br />
<br />
By connecting to Furnet you consent to your public IP address being scanned via our [[Proxy_Scanner|proxy scanners]].<br />
<br />
Network staff will be there to help you, but if you abuse staff they may well /ignore you. Staff whom are busy may direct you to #furnet - the help channel.<br />
<br />
By connecting to this network you agree to be bound to these Rules of Conduct.</div>Eisfuchshttps://www.furnet.org/wiki/index.php/GeneralGeneral2014-01-31T12:02:11Z<p>Hurga: /* General Information */</p>
<hr />
<div>= General Information =<br />
<br />
Furnet is an [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC] (Internet Relay Chat) network for the global furry community, and provides a network of IRC [[Servers|servers]] in Europe, the United States and Australia.<br />
<br />
You can connect to Furnet by using one of our [[Servers|servers]] mor DNS rotators, both unencrypted and [[Ssl_Connection|SSL encrypted]].<br />
<br />
To get started on Furnet IRC, we suggest you join one of the larger all-ages [[Channel|channels]] such as [irc://furnet.org/softpaws #softpaws] or [irc://furnet.org/feline #feline]. When connected to the network, use the /list command to get a list of the available channels.<br />
<br />
Furnet's official help channel is [irc://furnet.org/furnet #furnet]. To contact the network's administrators, please use the [http://www.furnet.org/mailform5.html general inquiries mail form].<br />
<br />
For discussion among Furnet's users about current events, [http://chanreg.furnet.org/channel_request.html channel registrations] etc, there is the furnet-users mailing list. To subscribe or edit an existing subscription, please visit the [http://kinglion.furnet.org/mailman/listinfo/furnet-users mailing list website].<br />
<br />
Please note that the network does not issue [[Vhost|vhosts]]; please ensure you either have reverse (and forward) [http://en.wikipedia.org/wiki/DNS DNS] correctly configured for a vanity [[hostmask]]. Use of the [[user mode]] +x will also [[Cloaking|hide]] the first component of your hostname.</div>Eisfuchshttps://www.furnet.org/wiki/index.php/Main_Page/MediaWiki:Common.jsMain Page/MediaWiki:Common.js2013-11-10T09:55:55Z<p>Shivalwolf: Created page with "!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https'; if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://pla..."</p>
<hr />
<div>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';<br />
if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://platform.twitter.com/widgets.js";<br />
fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</div>Shivalwolfhttps://www.furnet.org/wiki/index.php/Bot_PolicyBot Policy2013-11-10T08:20:58Z<p>Tursiae: </p>
<hr />
<div>== Summary ==<br />
<br />
Furnet's Bot Policy is designed in the interest of all our users' enjoyment of the network, and their privacy. We recently changed our bot policy on the network from requiring explicit registration, to being a set of guidelines that all bots on the network must follow. If your bot doesn't play by the bot policy, we may remove it from the network if there is an adverse effect on the network, or your fellow Furnet users.<br />
<br />
Please feel free to explore and extend your channel, but act in the interests of your fellow users.<br />
<br />
== The Obvious Stuff ==<br />
<br />
Please don't:<br />
<br />
* Use your bot to spam other channels.<br />
<br />
* Use your bot to advertise, whether by /msg, /notify, /invite, /part messages or any other means. Seriously. We've all had enough of spammers.<br />
<br />
* Log discussion on a channel without periodically notifying occupants of the channel, or without having a warning in the channel topic.<br />
<br />
Please do:<br />
<br />
* Include contact information for the owner in your bot's /whois.<br />
<br />
* Respect channel owner and operators' wishes if they do not want your bot to be present.<br />
<br />
== Bot Requirements ==<br />
<br />
All bots on Furnet must:<br />
<br />
* Do something cool.<br />
<br />
* Use a unique ident (also known as a username) on the host from which they connect.<br />
<br />
* Use a registered nickname.<br />
<br />
* Not bridge channels with others on Furnet or other IRC networks.<br />
<br />
* Respect /kick and /bans, and not re-join a channel after being kicked, unless explicitly requested by a human.<br />
<br />
On connection to Furnet, your bot must:<br />
<br />
* Set the +B mode on itself, to show that it is a bot.<br />
<br />
* Identify to Nickserv with its registered nickname.<br />
<br />
* Include in the bot's /whois contact information about the owner of the bot.<br />
<br />
Operators of bots on Furnet must:<br />
<br />
* Keep your operating systems and bots up-to-date with any security updates.<br />
<br />
* Remove your bots from channels where they are not welcome.<br />
<br />
== Best Practices ==<br />
<br />
Your bot should, when possible:<br />
<br />
* Use network services such as Chanserv to manage channel ACLs, bans and kicks. Feel free to fall back to doing manual /ban and /kick from your bot if network services are unavailable.<br />
<br />
* Part otherwise unoccupied channels. Please consider only real users, not other bots, when determining whether a channel is occupied. The +B mode is a good guide as to whether the other users are real, or mechanical.<br />
<br />
* Rate-limit reconnection to the network.<br />
<br />
* Obey Asimov's 3 laws.<br />
<br />
* Implement a 'help' command that gives a brief description of the bot.<br />
<br />
Also, for other users' privacy, please do not:<br />
<br />
* Make channel logs available on the internet at large. Statistics are fine, but please don't include quotes or logs without users' explicit consent.<br />
<br />
== Need help? ==<br />
<br />
We can't provide software development support, but if you have any queries about operation of bots on Furnet, please come and have a chat in #furnet. We don't bite, honest.</div>Shivalwolf