DareNET Wiki - User contributions [en]

Main Page

2018-08-07T05:43:42Z

Admin:

{{info|text='''The DareNET Wiki is outdated and will eventually be shutdown. For documentation please vist [https://www.darenet.org/help/guides https://www.darenet.org/help/guides].'''}}

<span class="help-heading">Sometimes you just need a little help.</span>
<html>
<table class="help-panels" cellspacing="20">
<tr>
<td class="help-panel" id="gettingStarted">
<div>
<h3><a href="http://wiki.darenet.org/FAQ">FAQs</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/FAQ/General">General</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Registration">Registration</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Account_and_Password">Account and Password</a></li>
</ul>
<a href="http://wiki.darenet.org/FAQ" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="wDocs">
<div>
<h3><a href="http://wiki.darenet.org/Category:Documentation">Documentation</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/New_Users">New Users</a></li>
<li><a href="http://wiki.darenet.org/Channels">Channels</a></li>
<li><a href="http://wiki.darenet.org/Services_Usage">Services Usage</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Documentation" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="policiesRules">
<div>
<h3><a href="http://wiki.darenet.org/Category:Policy">Policies and Rules</a></h3>
<ul>
<li><a href="http://www.darenet.org/tos">Terms of Service</a></li>
<li><a href="http://www.darenet.org/aup">Acceptable Use Policy</a></li>
<li><a href="http://www.darenet.org/privacy">Privacy Policy</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Policy" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>
</tr>
</table>
<div class="help-social"><a href="http://twitter.com/darenetirc"><img src="http://test.darenet.org/img/icons/twitter.png" border="0"></a> <a href="http://www.facebook.com/darenet"><img src="http://test.darenet.org/img/icons/facebook.png" border="0"></a> <a href="http://www.last.fm/group/DareNET"><img src="http://test.darenet.org/img/icons/lastfm.png" border="0"></a></div>
<div id="twitter_div">
<h2 class="twitter-title">Updates from DareNET Support</h2>
<ul id="twitter_update_list">
</ul>
</div>
<script type="text/javascript" src="http://twitter.com/javascripts/
blogger.js"></script>
<script type="text/javascript" src="http://twitter.com/statuses/user_
timeline/darenetirc.json?callback=twitterCallback2&count=1"></script>
</html>

Parent Guides

2018-08-07T05:41:10Z

Admin:

{{info|text='''This page is in the process of being moved to https://www.darenet.org/help/guides/parent-guides'''}}

DareNET is committed to providing a safe and stable environment for our users to chat in; however, this is no substitute for parental supervision of minors. Below is a list of sites with good information for parents to ensure their kids are chatting safely and properly.

*[https://www.getnetwise.org/ GetNetWise]: this public service is your one stop for helpful guides, blocking/filtering tools, how to report trouble, safe sites for kids, etc.
*[https://www.fbi.gov/stats-services/publications/parent-guide FBI Library - Parent's Guide to Internet Safety]: this short pamphlet from the FBI covers the safety issues with general suggestions.
*[https://www.staysafe.org/teens/ Staysafe.org's Online Teen Safety Guide] - Resources for both parents and teens for safely utilizing the Internet.

[[Category:All]] [[Category:New Users]]

Parent Guides

2018-08-07T05:16:21Z

Admin:

DareNET is committed to providing a safe and stable environment for our users to chat in; however, this is no substitute for parental supervision of minors. Below is a list of sites with good information for parents to ensure their kids are chatting safely and properly.

*[https://www.getnetwise.org/ GetNetWise]: this public service is your one stop for helpful guides, blocking/filtering tools, how to report trouble, safe sites for kids, etc.
*[https://www.fbi.gov/stats-services/publications/parent-guide FBI Library - Parent's Guide to Internet Safety]: this short pamphlet from the FBI covers the safety issues with general suggestions.
*[https://www.staysafe.org/teens/ Staysafe.org's Online Teen Safety Guide] - Resources for both parents and teens for safely utilizing the Internet.

[[Category:All]] [[Category:New Users]]

Parent Guides

2018-08-07T05:15:08Z

Admin:

Main Page

2018-08-02T17:55:27Z

Admin:

'''The DareNET Wiki is outdated and will eventually be shutdown. For documentation please vist [https://www.darenet.org/help/guides https://www.darenet.org/help/guides].'''

<span class="help-heading">Sometimes you just need a little help.</span>
<html>
<table class="help-panels" cellspacing="20">
<tr>
<td class="help-panel" id="gettingStarted">
<div>
<h3><a href="http://wiki.darenet.org/FAQ">FAQs</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/FAQ/General">General</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Registration">Registration</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Account_and_Password">Account and Password</a></li>
</ul>
<a href="http://wiki.darenet.org/FAQ" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="wDocs">
<div>
<h3><a href="http://wiki.darenet.org/Category:Documentation">Documentation</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/New_Users">New Users</a></li>
<li><a href="http://wiki.darenet.org/Channels">Channels</a></li>
<li><a href="http://wiki.darenet.org/Services_Usage">Services Usage</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Documentation" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="policiesRules">
<div>
<h3><a href="http://wiki.darenet.org/Category:Policy">Policies and Rules</a></h3>
<ul>
<li><a href="http://www.darenet.org/tos">Terms of Service</a></li>
<li><a href="http://www.darenet.org/aup">Acceptable Use Policy</a></li>
<li><a href="http://www.darenet.org/privacy">Privacy Policy</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Policy" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>
</tr>
</table>
<div class="help-social"><a href="http://twitter.com/darenetirc"><img src="http://test.darenet.org/img/icons/twitter.png" border="0"></a> <a href="http://www.facebook.com/darenet"><img src="http://test.darenet.org/img/icons/facebook.png" border="0"></a> <a href="http://www.last.fm/group/DareNET"><img src="http://test.darenet.org/img/icons/lastfm.png" border="0"></a></div>
<div id="twitter_div">
<h2 class="twitter-title">Updates from DareNET Support</h2>
<ul id="twitter_update_list">
</ul>
</div>
<script type="text/javascript" src="http://twitter.com/javascripts/
blogger.js"></script>
<script type="text/javascript" src="http://twitter.com/statuses/user_
timeline/darenetirc.json?callback=twitterCallback2&count=1"></script>
</html>

Main Page

2018-08-02T17:55:13Z

Admin:

'''The DareNET Wiki is outdated and will eventually be shutdown. For documentation please vist [https://www.darenet.org/help/guides].'''

<span class="help-heading">Sometimes you just need a little help.</span>
<html>
<table class="help-panels" cellspacing="20">
<tr>
<td class="help-panel" id="gettingStarted">
<div>
<h3><a href="http://wiki.darenet.org/FAQ">FAQs</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/FAQ/General">General</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Registration">Registration</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Account_and_Password">Account and Password</a></li>
</ul>
<a href="http://wiki.darenet.org/FAQ" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="wDocs">
<div>
<h3><a href="http://wiki.darenet.org/Category:Documentation">Documentation</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/New_Users">New Users</a></li>
<li><a href="http://wiki.darenet.org/Channels">Channels</a></li>
<li><a href="http://wiki.darenet.org/Services_Usage">Services Usage</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Documentation" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="policiesRules">
<div>
<h3><a href="http://wiki.darenet.org/Category:Policy">Policies and Rules</a></h3>
<ul>
<li><a href="http://www.darenet.org/tos">Terms of Service</a></li>
<li><a href="http://www.darenet.org/aup">Acceptable Use Policy</a></li>
<li><a href="http://www.darenet.org/privacy">Privacy Policy</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Policy" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>
</tr>
</table>
<div class="help-social"><a href="http://twitter.com/darenetirc"><img src="http://test.darenet.org/img/icons/twitter.png" border="0"></a> <a href="http://www.facebook.com/darenet"><img src="http://test.darenet.org/img/icons/facebook.png" border="0"></a> <a href="http://www.last.fm/group/DareNET"><img src="http://test.darenet.org/img/icons/lastfm.png" border="0"></a></div>
<div id="twitter_div">
<h2 class="twitter-title">Updates from DareNET Support</h2>
<ul id="twitter_update_list">
</ul>
</div>
<script type="text/javascript" src="http://twitter.com/javascripts/
blogger.js"></script>
<script type="text/javascript" src="http://twitter.com/statuses/user_
timeline/darenetirc.json?callback=twitterCallback2&count=1"></script>
</html>

Main Page

2016-12-11T04:47:11Z

Admin:

'''The DareNET Wiki is outdated and is being shutdown. If you wish to add or improve DareNET documentation, please grab an issue from the [https://c.darenet.org/site/docs/issues?label_name%5B%5D=wiki Move the wiki]! milestone.'''

<span class="help-heading">Sometimes you just need a little help.</span>
<html>
<table class="help-panels" cellspacing="20">
<tr>
<td class="help-panel" id="gettingStarted">
<div>
<h3><a href="http://wiki.darenet.org/FAQ">FAQs</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/FAQ/General">General</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Registration">Registration</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Account_and_Password">Account and Password</a></li>
</ul>
<a href="http://wiki.darenet.org/FAQ" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="wDocs">
<div>
<h3><a href="http://wiki.darenet.org/Category:Documentation">Documentation</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/New_Users">New Users</a></li>
<li><a href="http://wiki.darenet.org/Channels">Channels</a></li>
<li><a href="http://wiki.darenet.org/Services_Usage">Services Usage</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Documentation" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="policiesRules">
<div>
<h3><a href="http://wiki.darenet.org/Category:Policy">Policies and Rules</a></h3>
<ul>
<li><a href="http://www.darenet.org/tos">Terms of Service</a></li>
<li><a href="http://www.darenet.org/aup">Acceptable Use Policy</a></li>
<li><a href="http://www.darenet.org/privacy">Privacy Policy</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Policy" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>
</tr>
</table>
<div class="help-social"><a href="http://twitter.com/darenetirc"><img src="http://test.darenet.org/img/icons/twitter.png" border="0"></a> <a href="http://www.facebook.com/darenet"><img src="http://test.darenet.org/img/icons/facebook.png" border="0"></a> <a href="http://www.last.fm/group/DareNET"><img src="http://test.darenet.org/img/icons/lastfm.png" border="0"></a></div>
<div id="twitter_div">
<h2 class="twitter-title">Updates from DareNET Support</h2>
<ul id="twitter_update_list">
</ul>
</div>
<script type="text/javascript" src="http://twitter.com/javascripts/
blogger.js"></script>
<script type="text/javascript" src="http://twitter.com/statuses/user_
timeline/darenetirc.json?callback=twitterCallback2&count=1"></script>
</html>

Policy:Privacy Policy

2015-11-17T04:05:49Z

Admin: Replaced content with 'See https://www.darenet.org/privacy'

See https://www.darenet.org/privacy

Extended Bans

2015-10-21T22:33:03Z

Admin: Add note about regarding +s/p channels for extban 'j' at tyil's request

Extended bans allow different checks than the usual nick!user@host (hostmask) match to determine whether someone should be banned from the channel, allowing channel operators more flexibility and control over their channel's ban list. On DareNET, extended bans are of the form '''<code>$[~]<type>:<data></code>'''. Where <type> is one character (case sensitive) and determines the type of match that is to be used. If the tilde (~) is used, the result of the check will be negated.

The following types of extended bans are currently supported:

{| class="simpletable" width="100%"
! style="text-align: center;" | Type
! style="text-align: center;" | Name
! style="text-align: left;" | Purpose
|-
| style="text-align: center;" | $a
| style="text-align: center;" | Account
| If a user's account name matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $c
| style="text-align: center;" | Channel
| If a user is in a channel that matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $j
| style="text-align: center;" | Shared Bans
| If a user matches a ban on the channel who's ban list is being shared, (s)he will be unable to join.
|-
| style="text-align: center;" | $r
| style="text-align: center;" | Realname
| If a user's realname (gecos) matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $t
| style="text-align: center;" | Text
| Allows you to specify text that will be blocked if a user's privmsg or notice to the channel contains it.
|-
|}<br />

== Account ==

The $a (account) type allows you to ban authed users who's account name matches the specified account mask.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $a:<mask>
|-
|}

If we wanted to ban all users who's account name contained the word ''joe'', we could set the following $a type extended ban:

<code>/mode #ourchannel +b $a:*joe*</code>

== Channel ==

The $c (channel) type prevents users who are in a matching channel from joining your channel.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $c:<#channel>
|-
|}

If we wanted to prevent users who are in channels with the word ''lame'' in its name from joining our channel, we could set the following $c type extended ban.

<code>/mode #ourchannel +b $c:#*lame*</code>

== Realname ==

The $r (realname/gecos) type prevents users with a matching realname from joining your channel.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $r:<mask>
|-
|}

If we wanted to prevent users who had the word ''bot'' in their realname (gecos) from the joining our channel, we could set the following $r type extended ban:

<code>/mode #ourchannel +b $r:*bot*</code>

== Shared bans ==

The $j type allows sharing channel ban lists.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $j:<#channel>
|-
|}

For this example, the name of our channel is ''#ourchannel'' and we want to use ''#shared''<nowiki>'</nowiki>s channel ban list with our own. So, to do this we could set the following $j type extended ban:

<code>/mode #ourchannel +b $j:#shared</code>

Now, whenever a user tries to join our channel, ''#ourchannel'', they'll be checked against ''#shared''<nowiki>'</nowiki>s ban list in addition to our own ban list. If a match is found in either ban list, the user will be prevented from joining.

'''NOTE:''' The shared channel must not be in +p or +s for this to work

== Text bans ==

The $t (text) type allows channel operators to specify words (wildcards supported) that will be blocked if the user's message or notice to the channel matches it.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $t:<#mask>
|-
|}

Let's say we wanted to block all channel messages and notices that contained the word ''damn'', regardless of the user sending it. To do this we could set the following $t type extended ban:

<code>/mode #ourchannel +b $t:*damn*</code>

== Negation / Reverse logic ==

If "~" is prepended to the type of an extended ban, then the result of the comparison is negated. In other words, it will have a reversed effect.

Let's say we wanted to allow users to join our channel ONLY if they're already present in #darenet. To do this, we would set a $c type extended ban, by prepending "~" to the type flag:

<code>/mode #ourchannel +b $~c:#darenet</code>

== Assistance ==

Should you need assistance using the extended bans feature, feel free to stop by #help.

[[Category:All]] [[Category:Documentation]]

Welcome to DareNET

2014-10-01T10:28:46Z

Admin:

DareNET is a community centered around an [[Wikipedia:Internet Relay Chat|IRC]] network. We're a group of people who like helping people connect with each other and have real conversations.

To help you get started, we created this brief guide for new users, so read on!

==Joining the conversation==

You can connect to our IRC network in one of two ways:

# By using our [http://webchat.darenet.org webchat client], which allows you to connect to DareNET through you favorite web browser,
# or by using your favorite IRC client. A list of IRC clients for various operating systems can be found [http://www.wikipedia.org/wiki/List_of_IRC_clients here].

Downloading and setting up an IRC clients is the preferred option for the majority of our users, though it does require a bit of effort on their part. Should you decide to go this route as well, the server you'll want to use to connect to DareNET is [irc://irc.darenet.org irc.darenet.org]. Common ports are 6660-6669 and 7000. We support SSL/TLS-enabled connections on ports 6697 and 9999 -- see our [[Using SSL]] guide for more information.

===I've connected, now what?===

If you're new to IRC, you may want to read our [[Basic IRCd Commands|Basic IRCd Commands guide]], which will help you achieve simple tasks such as changing your nickname and joining a channel (''chat room'').

Once you're connected, you'll probably want to sign up for an account. Why sign up you ask? Well, your DareNET account allows you to use and take full advantage of all the great features we provide, such as our IRC services (i.e., C, N, V, etc.), build and customize a user profile on the site, prevent others from using your nickname(s), register chat rooms (channels), and more.

== Signing up ==

If you haven't already signed up for a DareNET account, do that first. Simply visit the [https://www.darenet.org/signup Sign up page] and create a new account.

NOTE: On DareNET, your account name is an arbitrary username independent of your IRC nickname (although, they can be the same, in some instances). It is how N, C and other services will recognize you on the IRC network, and is used to login to the website. In essence, it's how others will come to know and easily find you on DareNET. It is NOT nickname registration (don't worry, we'll cover that a little later in this guide), and cannot be changed.

== Authenticating to N ==

''Also commonly referred to as identifying to and/or logging into N.''

Now that you have a DareNET account, you'll want to authenticate to N so you can actually use it on the IRC network. There are a few different ways you can do this, but we'll explain the most commonly used commands for this below:

<div class="usage">Usage: <code>/msg N@services.darenet.org AUTH <username|email@domain.tld> <password></code></div>

Where <code><username|email@domain.tld></code> is your DareNET username or email address, and <code><password></code> is your account password. For example, let's say your username was ''JoeCool'' and your password was ''aPpLe321''. To authenticate, using the command shown above, you would simply use: <code>/msg N@services.darenet.org AUTH JoeCool aPpLe321</code> or <code>/msg N@services.darenet.org AUTH joecool@gmail.com aPpLe321</code>

Alternatively, you can use the more condensed versions of the above command:

<div class="usage">Usage: <code>/NS AUTH <username|email@domain.tld> <password></code></div>

-OR-

<div class="usage">Usage: <code>/AUTH <username|<email@domain.tld> <password></code></div>

If the command is used correctly, you will receive a notice from N similar to the following:

<pre>-N- Authentication as JoeCool successful. You are now logged in!
-N- Remember, DareNET's staff will NEVER ask you for your account
-N- password. The only place to receive assistance with account
-N- related matters on DareNET is in #help</pre>

In addition to the authentication methods shown above, we also support a "login-on-connect" method, which will automatically log you into N while you're connecting to the network. It will also exempt you from any DNSBL checks, and automatically set user mode +x (hiding your host/ip address). For more information on how to set this feature up for your IRC client, go [http://www.darenet.org/support/loc here].

NOTE: [http://www.darenet.org/webchat Webchat] users can use the "login-on-connect" method simply by selecting the "Login to N" checkbox on the connection details page, and entering their DareNET account username and password.

== Nicknames ==

We allow users to register the nicknames they commonly used to their account. By registering your nicknames, you will be able to prevent others from using it -- securing your identify on the network. NOTE: You must be authenticated to your account and using the nickname you would like to register before using the command below:

<div class="usage">Usage: <code>/msg N REGNICK</code></div>

If it's successful, you'll receive a notice from N similar to the following:

<pre>-N- Nick YOURNICK has been registered to you.</pre>

{{info|text= Registering an account does not always mean you automatically own the associated nickname too. To prevent others from taking your nicknames, claim them using the step shown above.}}<br />

== Hostmasking ==

One of the perks of being a registered user is that you can hide your IP address/host from other users. A little extra piece of mind! If this is a feature you would like to take advantage of, simply use the following command (make sure you have authenticated to N):

<code>/mode yournickhere +x</code>

Alternatively, you can have N automatically set you +x when you identify to your account. To do this, use the following command:

<code>/msg N SET AUTOHIDE on</code>

== Securing your Account/Nickname ==

We have a few suggestions for securing your account, which include:

===Suggestion #1:===

Enable N's RECLAIM option for your account:

<code>/msg N SET RECLAIM on</code>

N's RECLAIM option protects your nicknames when you are not using them. Should another user try to use any nicknames registered to your account, N will automatically change their nickname to something more suitable.

===Suggestion #2:===

Add your own hostmask to your account's allowed hosts list:

<code>/msg N ADDMASK <yourident@your.mask.here></code>

If you would like to add the host you're current using, simply omit the part after ADDMASK and just use: /msg N ADDMASK

Once you have performed the above command, you may delete the default mask set for your account by using the following command:

<code>/msg N DELMASK *@*</code>

The above steps protect your account by denying logins from clients who's host does not match one of the specified hostmasks for your account. Should you try to authenticate from a different hostmask that is not specified you will have to issue N's AUTHCOOKIE command to have a cookie sent to your email. Once you receive that cookie, you can then authenticate to your nickname and add the mask if you wish.

== Channel Registration ==

As a registered user, you have the opportunity to register channels (chat rooms) with C, our channel services bot, which provides both useful and powerful features to aid channel owner's in maintaining and protecting their channel. For more information, please review our [http://www.darenet.org/channel_registration channel registration guidelines].

== Misc. Information ==

Some more information that may prove useful:

=== Support Channel ===

Should you ever find that you need assistance with something that is related to DareNET, or IRC in general, you can always step into our official support channel, [http://www.darenet.org/webchat?channels=help #help], where our trained support staff will be pleased to help you.

=== Nickname vs *Account ===

Most of the commands provided by N, C, or any other service on DareNET, allow for an account or online users to be referenced. When referencing an account, you should use <code>*account</code> (note the asterisk prefixed to the account name). For example:

<pre><SomeUser> /msg N INFO *NiTeMaRe
-N- Account Information for NiTeMaRe
-N- ----------------------------------------
-N- Registered on: Tue Mar 18 07:44:30 2008
-N- Last seen: Right now!
-N- Infoline: NiTeMaRe is cool!
-N- ----------End of Account Info-----------
</pre>

This signals to services to use the account name directly, useful for when a user is offline and you want to add/remove them from your channel's userlist, send them a memo or even do a N INFO on their account. If you do not prefix the account name with an asterisk (*), services will treat it as a nickname that is currently being used on the network, which may not produce the outcome you expect!

=== Server-side Command Aliases ===

We support a number of server-side aliases for various Services' (i.e., C, N, etc.), for those whose IRC clients support them. For a list of such aliases, go [[Command Aliases|here]].

[[Category:All]] [[Category:New Users]]

Welcome to DareNET

2014-10-01T10:17:09Z

Admin:

{{note|Follow us on [http://twitter.com/darenetirc Twitter], and like us on [http://www.facebook.com/darenet Facebook]! <html><a href="http://twitter.com/darenetirc"><img src="http://test.darenet.org/img/icons/twitter.png" border="0"></a> <a href="http://www.facebook.com/darenet"><img src="http://test.darenet.org/img/icons/facebook.png" border="0"></a></html>}}

==What is DareNET?==

DareNET is a community centered around an [[Wikipedia:Internet Relay Chat|IRC]] network. We're a group of people who like helping people connect with each other and have real conversations.

To help you get started, we created this brief guide for new users, so read on!

==Joining the conversation==

You can connect to our IRC network in one of two ways:

# By using our [http://webchat.darenet.org webchat client], which allows you to connect to DareNET through you favorite web browser,
# or by using your favorite IRC client. A list of IRC clients for various operating systems can be found [http://www.wikipedia.org/wiki/List_of_IRC_clients here].

Downloading and setting up an IRC clients is the preferred option for the majority of our users, though it does require a bit of effort on their part. Should you decide to go this route as well, the server you'll want to use to connect to DareNET is [irc://irc.darenet.org irc.darenet.org]. Common ports are 6660-6669 and 7000. We support SSL/TLS-enabled connections on ports 6697 and 9999 -- see our [[Using SSL]] guide for more information.

===I've connected, now what?===

If you're new to IRC, you may want to read our [[Basic IRCd Commands|Basic IRCd Commands guide]], which will help you achieve simple tasks such as changing your nickname and joining a channel (''chat room'').

{{info|text=If you already have a registered account on DareNET, you can safely [[Welcome_to_DareNET#Authenticating_to_N|skip this part]].}}

Once you're connected, you'll probably want to register an account. Why register you ask? Well, your DareNET account allows you to use and take full advantage of all the great features we provide, such as our IRC services (i.e., C, N, V, etc.), build and customize a user profile on the site, prevent others from using your nicknames, register chat rooms (channels), and more.

== Account Registration ==

Registering an account on DareNET is fast and easy. Simply point your favorite web browser to our [http://www.darenet.org/register account registration page], choose a username and password, enter your email address and you're all set!

NOTE: On DareNET, your account name is an arbitrary username independent of your IRC nickname (although, they can be the same, in some instances). It is how N, C and other services will recognize you on the IRC network, and is used to login to the website. In essence, it's how others will come to know and easily find you on DareNET. It is NOT nickname registration (don't worry, we'll cover that a little later in this guide), and cannot be changed.

=== Authenticating to N ===

''Also commonly referred to as identifying to and/or logging into N.''

Now that you have a registered account, you will need to authenticate to N to actually use it on the IRC network! There are a few different ways you can do this, all leading to the same result -- authenticating you to N. We'll explain the most commonly used commands for this below:

<div class="usage">Syntax: <code>/msg N@services.darenet.org AUTH <username|email@domain.tld> <password></code></div>

Where <code><account></code> is your DareNET username, and <code><password></code> is your account password. For example, let's say your username was ''JoeCool'' and your password was ''aPpLe321''. To authenticate, using the command shown above, you would simply use: <code>/msg N@services.darenet.org AUTH JoeCool aPpLe321</code> or <code>/msg N@services.darenet.org AUTH joecool@gmail.com aPpLe321</code>

Alternatively, you can use the more condensed versions of the above command:

<code>/NS AUTH <username|email@domain.tld> <password></code>

-OR-

<code>/AUTH <username|<email@domain.tld> <password></code>

If the command is used correctly, you will receive a notice from N similar to the following:

<pre>-N- Authentication as JoeCool successful. You are now logged in!
-N- Remember, DareNET's staff will NEVER ask you for your account
-N- password. The only place to receive assistance with account
-N- related matters on DareNET is in #help</pre>

In addition to the authentication methods shown above, we also support a "login-on-connect" method, which will automatically log you into N while you're connecting to the network. It will also exempt you from any DNSBL checks, and automatically set user mode +x (hiding your host/ip address). For more information on how to set this feature up for your IRC client, go [http://www.darenet.org/support/loc here].

NOTE: [http://www.darenet.org/webchat Webchat] users can use the "login-on-connect" method simply by selecting the "Login to N" checkbox on the connection details page, and entering their DareNET account username and password.

== Nicknames ==

Here on DareNET, we allow users to register the nicknames they commonly use to their account. By registering your nicknames, you will be able to prevent others from using it -- securing your identify on the network. NOTE: You must be authenticated to your account and using the nickname you would like to register before using the command below:

<code>/msg N REGNICK</code>

If it's successful, you'll receive a notice from N similar to the following:

<pre>-N- Nick YOURNICK has been registered to you.</pre>

{{info|text= Registering an account does not always mean you automatically own the associated nickname too. To prevent others from taking your nicknames, claim them using the step shown above.}}<br />

=== Hostmasking ===

One of the perks of being a registered user is that you can hide your IP address/host from other users. A little extra piece of mind! If this is a feature you would like to take advantage of, simply use the following command (make sure you have authenticated to N):

<code>/mode yournickhere +x</code>

Alternatively, you can have N automatically set you +x when you identify to your account. To do this, use the following command:

<code>/msg N SET AUTOHIDE on</code>

== Securing your Account/Nickname ==

We have a few suggestions for securing your account, which include:

===Suggestion #1:===

Enable N's RECLAIM option for your account:

<code>/msg N SET RECLAIM on</code>

N's RECLAIM option protects your nicknames when you are not using them. Should another user try to use any nicknames registered to your account, N will automatically change their nickname to something more suitable.

===Suggestion #2:===

Add your own hostmask to your account's allowed hosts list:

<code>/msg N ADDMASK <yourident@your.mask.here></code>

If you would like to add the host you're current using, simply omit the part after ADDMASK and just use: /msg N ADDMASK

Once you have performed the above command, you may delete the default mask set for your account by using the following command:

<code>/msg N DELMASK *@*</code>

The above steps protect your account by denying logins from clients who's host does not match one of the specified hostmasks for your account. Should you try to authenticate from a different hostmask that is not specified you will have to issue N's AUTHCOOKIE command to have a cookie sent to your email. Once you receive that cookie, you can then authenticate to your nickname and add the mask if you wish.

== Channel Registration ==

As a registered user, you have the opportunity to register channels (chat rooms) with C, our channel services bot, which provides both useful and powerful features to aid channel owner's in maintaining and protecting their channel. For more information, please review our [http://www.darenet.org/channel_registration channel registration guidelines].

== Misc. Information ==

Some more information that may prove useful:

=== Support Channel ===

Should you ever find that you need assistance with something that is related to DareNET, or IRC in general, you can always step into our official support channel, [http://www.darenet.org/webchat?channels=help #help], where our trained support staff will be pleased to help you.

=== Nickname vs *Account ===

Most of the commands provided by N, C, or any other service on DareNET, allow for an account or online users to be referenced. When referencing an account, you should use <code>*account</code> (note the asterisk prefixed to the account name). For example:

<pre><SomeUser> /msg N INFO *NiTeMaRe
-N- Account Information for NiTeMaRe
-N- ----------------------------------------
-N- Registered on: Tue Mar 18 07:44:30 2008
-N- Last seen: Right now!
-N- Infoline: NiTeMaRe is cool!
-N- ----------End of Account Info-----------
</pre>

This signals to services to use the account name directly, useful for when a user is offline and you want to add/remove them from your channel's userlist, send them a memo or even do a N INFO on their account. If you do not prefix the account name with an asterisk (*), services will treat it as a nickname that is currently being used on the network, which may not produce the outcome you expect!

=== Server-side Command Aliases ===

We support a number of server-side aliases for various Services' (i.e., C, N, etc.), for those whose IRC clients support them. For a list of such aliases, go [[Command Aliases|here]].

[[Category:All]] [[Category:New Users]]

Welcome to DareNET

2014-08-31T14:40:48Z

Admin:

{{note|Follow us on [http://twitter.com/darenetirc Twitter], and like us on [http://www.facebook.com/darenet Facebook]! <html><a href="http://twitter.com/darenetirc"><img src="http://test.darenet.org/img/icons/twitter.png" border="0"></a> <a href="http://www.facebook.com/darenet"><img src="http://test.darenet.org/img/icons/facebook.png" border="0"></a></html>}}

==What is DareNET?==

DareNET is an inclusive, multi-purpose community centered around an [[Wikipedia:Internet Relay Chat|IRC]] network. We're a group of people who love helping people connect with each other and have real conversations.

To help you get started, we created this brief guide for new users, so read on!

==Connecting to DareNET==

You can connect to our IRC network in one of two ways:

# By using our [http://webchat.darenet.org webchat client], which allows you to connect to DareNET through your web browser,
# or by using your favorite IRC client. A list of IRC clients for various operating systems can be found [http://www.wikipedia.org/wiki/List_of_IRC_clients here].

Downloading and setting up an IRC clients is the preferred option for the majority of our users, though it does require a bit of effort on their part. Should you decide to go this route as well, the server you'll want to use to connect to DareNET is [irc://irc.darenet.org irc.darenet.org]. Common ports are 6660-6669 and 7000. We support SSL/TLS-enabled connections on ports 6697 and 9999 -- see our [[Using SSL]] guide for more information.

===I've connected, now what?===

If you are completely new to IRC, you may want to read our [[Basic IRCd Commands|Basic IRCd Commands guide]], which will help you achieve simple tasks such as changing your nickname and joining a channel (''chat room'').

{{info|text=If you already have a registered account on DareNET, you can safely [[Welcome_to_DareNET#Authenticating_to_N|skip this part]].}}

Once you've connected to the network, you'll probably want to register an account. Why register you ask? Well, your DareNET account allows you to use and take full advantage of all the great features we provide, such as our IRC services (i.e., C, N, V, etc.), build and customize a user profile on the site, post to the forums, create albums and share them with friends, prevent others from using your nicknames, register chat rooms (channels), and more.

== Account Registration ==

Registering an account on DareNET is fast and easy. Simply point your favorite web browser to our [http://www.darenet.org/register account registration page], choose a username and password, enter your email address and you're all set!

NOTE: On DareNET, your account name is an arbitrary username independent of your IRC nickname (although, they can be the same, in some instances). It is how N, C and other services will recognize you on the IRC network, and is used to login to the website. In essence, it's how others will come to know and easily find you on DareNET. It is NOT nickname registration (don't worry, we'll cover that a little later in this guide), and cannot be changed.

=== Authenticating to N ===

''Also commonly referred to as identifying to and/or logging into N.''

Now that you have a registered account, you will need to authenticate to N to actually use it on the IRC network! There are a few different ways you can do this, all leading to the same result -- authenticating you to N. We'll explain the most commonly used commands for this below:

<div class="usage">Syntax: <code>/msg N@services.darenet.org AUTH <username|email@domain.tld> <password></code></div>

Where <code><account></code> is your DareNET username, and <code><password></code> is your account password. For example, let's say your username was ''JoeCool'' and your password was ''aPpLe321''. To authenticate, using the command shown above, you would simply use: <code>/msg N@services.darenet.org AUTH JoeCool aPpLe321</code> or <code>/msg N@services.darenet.org AUTH joecool@gmail.com aPpLe321</code>

Alternatively, you can use the more condensed versions of the above command:

<code>/NS AUTH <username|email@domain.tld> <password></code>

-OR-

<code>/AUTH <username|<email@domain.tld> <password></code>

If the command is used correctly, you will receive a notice from N similar to the following:

<pre>-N- Authentication as JoeCool successful. You are now logged in!
-N- Remember, DareNET's staff will NEVER ask you for your account
-N- password. The only place to receive assistance with account
-N- related matters on DareNET is in #help</pre>

In addition to the authentication methods shown above, we also support a "login-on-connect" method, which will automatically log you into N while you're connecting to the network. It will also exempt you from any DNSBL checks, and automatically set user mode +x (hiding your host/ip address). For more information on how to set this feature up for your IRC client, go [http://www.darenet.org/support/loc here].

NOTE: [http://www.darenet.org/webchat Webchat] users can use the "login-on-connect" method simply by selecting the "Login to N" checkbox on the connection details page, and entering their DareNET account username and password.

== Nicknames ==

Here on DareNET, we allow users to register the nicknames they commonly use to their account. By registering your nicknames, you will be able to prevent others from using it -- securing your identify on the network. NOTE: You must be authenticated to your account and using the nickname you would like to register before using the command below:

<code>/msg N REGNICK</code>

If it's successful, you'll receive a notice from N similar to the following:

<pre>-N- Nick YOURNICK has been registered to you.</pre>

{{info|text= Registering an account does not always mean you automatically own the associated nickname too. To prevent others from taking your nicknames, claim them using the step shown above.}}<br />

=== Hostmasking ===

One of the perks of being a registered user is that you can hide your IP address/host from other users. A little extra piece of mind! If this is a feature you would like to take advantage of, simply use the following command (make sure you have authenticated to N):

<code>/mode yournickhere +x</code>

Alternatively, you can have N automatically set you +x when you identify to your account. To do this, use the following command:

<code>/msg N SET AUTOHIDE on</code>

== Securing your Account/Nickname ==

We have a few suggestions for securing your account, which include:

===Suggestion #1:===

Enable N's RECLAIM option for your account:

<code>/msg N SET RECLAIM on</code>

N's RECLAIM option protects your nicknames when you are not using them. Should another user try to use any nicknames registered to your account, N will automatically change their nickname to something more suitable.

===Suggestion #2:===

Add your own hostmask to your account's allowed hosts list:

<code>/msg N ADDMASK <yourident@your.mask.here></code>

If you would like to add the host you're current using, simply omit the part after ADDMASK and just use: /msg N ADDMASK

Once you have performed the above command, you may delete the default mask set for your account by using the following command:

<code>/msg N DELMASK *@*</code>

The above steps protect your account by denying logins from clients who's host does not match one of the specified hostmasks for your account. Should you try to authenticate from a different hostmask that is not specified you will have to issue N's AUTHCOOKIE command to have a cookie sent to your email. Once you receive that cookie, you can then authenticate to your nickname and add the mask if you wish.

== Channel Registration ==

As a registered user, you have the opportunity to register channels (chat rooms) with C, our channel services bot, which provides both useful and powerful features to aid channel owner's in maintaining and protecting their channel. For more information, please review our [http://www.darenet.org/channel_registration channel registration guidelines].

== Misc. Information ==

Some more information that may prove useful:

=== Support Channel ===

Should you ever find that you need assistance with something that is related to DareNET, or IRC in general, you can always step into our official support channel, [http://www.darenet.org/webchat?channels=help #help], where our trained support staff will be pleased to help you.

=== Nickname vs *Account ===

Most of the commands provided by N, C, or any other service on DareNET, allow for an account or online users to be referenced. When referencing an account, you should use <code>*account</code> (note the asterisk prefixed to the account name). For example:

<pre><SomeUser> /msg N INFO *NiTeMaRe
-N- Account Information for NiTeMaRe
-N- ----------------------------------------
-N- Registered on: Tue Mar 18 07:44:30 2008
-N- Last seen: Right now!
-N- Infoline: NiTeMaRe is cool!
-N- ----------End of Account Info-----------
</pre>

This signals to services to use the account name directly, useful for when a user is offline and you want to add/remove them from your channel's userlist, send them a memo or even do a N INFO on their account. If you do not prefix the account name with an asterisk (*), services will treat it as a nickname that is currently being used on the network, which may not produce the outcome you expect!

=== Server-side Command Aliases ===

We support a number of server-side aliases for various Services' (i.e., C, N, etc.), for those whose IRC clients support them. For a list of such aliases, go [[Command Aliases|here]].

[[Category:All]] [[Category:New Users]]

Template:note

2014-08-31T14:40:20Z

Admin: Created page with '<blockquote class="note">{{{1}}}</blockquote>'

MediaWiki:Toc

2014-08-31T14:18:34Z

Admin: Created page with 'In This Guide:'

In This Guide:

Main Page

2014-08-31T14:10:04Z

Admin:

<span class="help-heading">Sometimes you just need a little help.</span>
<html>
<table class="help-panels" cellspacing="20">
<tr>
<td class="help-panel" id="gettingStarted">
<div>
<h3><a href="http://wiki.darenet.org/FAQ">FAQs</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/FAQ/General">General</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Registration">Registration</a></li>
<li><a href="http://wiki.darenet.org/FAQ/Account_and_Password">Account and Password</a></li>
</ul>
<a href="http://wiki.darenet.org/FAQ" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="wDocs">
<div>
<h3><a href="http://wiki.darenet.org/Category:Documentation">Documentation</a></h3>
<ul>
<li><a href="http://wiki.darenet.org/New_Users">New Users</a></li>
<li><a href="http://wiki.darenet.org/Channels">Channels</a></li>
<li><a href="http://wiki.darenet.org/Services_Usage">Services Usage</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Documentation" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>

<td class="help-panel" id="policiesRules">
<div>
<h3><a href="http://wiki.darenet.org/Category:Policy">Policies and Rules</a></h3>
<ul>
<li><a href="http://www.darenet.org/tos">Terms of Service</a></li>
<li><a href="http://www.darenet.org/aup">Acceptable Use Policy</a></li>
<li><a href="http://www.darenet.org/privacy">Privacy Policy</a></li>
</ul>
<a href="http://wiki.darenet.org/Category:Policy" class="btn btn-blue">View All</a>
<span></span>
</div>
</td>
</tr>
</table>
<div class="help-social"><a href="http://twitter.com/darenetirc"><img src="http://test.darenet.org/img/icons/twitter.png" border="0"></a> <a href="http://www.facebook.com/darenet"><img src="http://test.darenet.org/img/icons/facebook.png" border="0"></a> <a href="http://www.last.fm/group/DareNET"><img src="http://test.darenet.org/img/icons/lastfm.png" border="0"></a></div>
<div id="twitter_div">
<h2 class="twitter-title">Updates from DareNET Support</h2>
<ul id="twitter_update_list">
</ul>
</div>
<script type="text/javascript" src="http://twitter.com/javascripts/
blogger.js"></script>
<script type="text/javascript" src="http://twitter.com/statuses/user_
timeline/darenetirc.json?callback=twitterCallback2&count=1"></script>
</html>

Channel Modes

2014-08-17T12:13:18Z

Admin:

The following channel modes are available on DareNET:

{| class="simpletable" width="100%"
! style="text-align: center;" | Mode
! style="text-align: left;" | Name
! style="text-align: left; width:100px;" | Arguments
! style="text-align: left;" | Description
|-
| style="text-align: center;" | +b
| style="text-align: left;" | Channel ban
| <ban mask>
| Prevents all users matching the mask from joining the channel. Users who are still in the channel and match the mask will be unable to send messages to the channel. [[Extended Bans]] are supported.
|-
| style="text-align: center;" | +c
| style="text-align: left;" | No colors
|
| Channel messages containing control codes/colors are blocked.
|-
| style="text-align: center;" | +C
| style="text-align: left;" | No CTCPs
|
| CTCP messages addressed to the channel are blocked (ACTION CTCPs (i.e., /me) are still allowed).
|-
| style="text-align: center;" | +d
| style="text-align: left;" | Hidden users
|
| This mode will be automatically set/unset when you set +D or -D. It indicates that hidden users are still present on the channel. See the [[Delayed Joins|Delayed Joins FAQ]] for details.
|-
| style="text-align: center;" | +D
| style="text-align: left;" | Delayed joins
|
| See the [[Delayed Joins|delayed joins FAQ]] for details.
|-
| style="text-align: center;" | +e
| style="text-align: left;" | Exceptions
| <ban mask>
| Allows matching users to bypass join restrictions including bans (+b), invite only mode (+i), channel keys (+k), user limits (+l), registered only mode (+r) and SSL only mode (+Z). [[Extended Bans]] are supported.
|-
| style="text-align: center;" | +h
| style="text-align: left;" | Half operator
| <nick>
| Grants a user half operator status on the channel. Nicklist prefix: %
|-
| style="text-align: center;" | +i
| style="text-align: left;" | Invite only
|
| Sets the channel as invite-only, requiring users to be invited to be able to join. Users matching an exception (+e) will still be able to join.
|-
| style="text-align: center;" | +k
| style="text-align: left;" | Keyed
| <key>
| Sets a key (password) for the channel, which users must specify with /JOIN to be able to join. Users matching an exception (+e) will be able to join without specifying the key.
|-
| style="text-align: center;" | +l
| style="text-align: left;" | Limit
| <limit>
| Sets a user limit for the channel. Once the limit is reached, no further joins will be allowed. Users matching an exception (+e) will still be able to join.
|-
| style="text-align: center;" | +m
| style="text-align: left;" | Moderated
|
| Non-voiced/(half)opped users may not send messages to the channel.
|-
| style="text-align: center;" | +M
| style="text-align: left;" | Moderated (unregistered)
|
| Non-authed users may not send messages to the channel.
|-
| style="text-align: center;" | +n
| style="text-align: left;" | No external messages
|
| Blocks all external messages to the channel (i.e., from users not on the channel).
|-
| style="text-align: center;" | +N
| style="text-align: left;" | No notices
|
| Blocks notices addressed to the channel.
|-
| style="text-align: center;" | +o
| style="text-align: left;" | Channel operator
| <nick>
| Grants a user channel operator status on the channel. Nicklist prefix: @
|-
| style="text-align: center;" | +p
| style="text-align: left;" | Private
|
| Marks the channel as private, preventing it from appearing in /LIST.
|-
| style="text-align: center;" | +q
| style="text-align: left;" | Quiet
| <ban mask>
| Prevents matching users from sending messages to the channel. Users matching an exception (+e) will still be able to talk. [[Extended Bans]] are supported.
|-
| style="text-align: center;" | +r
| style="text-align: left;" | Registered only
|
| Sets the channel as registered only, preventing non-authed users from joining the channel.
|-
| style="text-align: center;" | +s
| style="text-align: left;" | Secret
|
| Marks the channel as secret, preventing it from appearing in /LIST and /WHOIS replies.
|-
| style="text-align: center;" | +t
| style="text-align: left;" | Op-only topic
|
| Only (half)ops may change the channel topic using /TOPIC.
|-
| style="text-align: center;" | +T
| style="text-align: left;" | No multiple targets
|
| Blocks messages targeting multiple channels (such as those sent by /amsg scripts).
|-
| style="text-align: center;" | +u
| style="text-align: left;" | No quit/parts
|
| Squelches user /PART and /QUIT reasons, preventing them from being shown to the channel.
|-
| style="text-align: center;" | +v
| style="text-align: left;" | Voice
| <nick>
| Grants a user voice status on the channel. Nicklist prefix: +
|-
| style="text-align: center;" | +z
| style="text-align: left;" | Persistent (registered) [[Image:User delete.png]]
|
| Prevents the channel from being deleted when the last user leaves, preserving modes/bans/topics/etc. Automatically set in registered channels.
|-
| style="text-align: center;" | +Z
| style="text-align: left;" | SSL-only
|
| Prevents non-SSL users from joining the channel. Users matching an exception (+e) will still be able to join.
|-
|}

[[Image:User delete.png]] <small>= denotes modes which are restricted to DareNET staff or services.</small>

[[Category:All]] [[Category:Documentation]]

Extended Bans

2014-06-29T22:42:41Z

Admin: /* Negation / Reverse logic */

Extended bans allow different checks than the usual nick!user@host (hostmask) match to determine whether someone should be banned from the channel, allowing channel operators more flexibility and control over their channel's ban list. On DareNET, extended bans are of the form '''<code>$[~]<type>:<data></code>'''. Where <type> is one character (case sensitive) and determines the type of match that is to be used. If the tilde (~) is used, the result of the check will be negated.

The following types of extended bans are currently supported:

{| class="simpletable" width="100%"
! style="text-align: center;" | Type
! style="text-align: center;" | Name
! style="text-align: left;" | Purpose
|-
| style="text-align: center;" | $a
| style="text-align: center;" | Account
| If a user's account name matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $c
| style="text-align: center;" | Channel
| If a user is in a channel that matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $j
| style="text-align: center;" | Shared Bans
| If a user matches a ban on the channel who's ban list is being shared, (s)he will be unable to join.
|-
| style="text-align: center;" | $r
| style="text-align: center;" | Realname
| If a user's realname (gecos) matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $t
| style="text-align: center;" | Text
| Allows you to specify text that will be blocked if a user's privmsg or notice to the channel contains it.
|-
|}<br />

== Account ==

The $a (account) type allows you to ban authed users who's account name matches the specified account mask.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $a:<mask>
|-
|}

If we wanted to ban all users who's account name contained the word ''joe'', we could set the following $a type extended ban:

<code>/mode #ourchannel +b $a:*joe*</code>

== Channel ==

The $c (channel) type prevents users who are in a matching channel from joining your channel.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $c:<#channel>
|-
|}

If we wanted to prevent users who are in channels with the word ''lame'' in its name from joining our channel, we could set the following $c type extended ban.

<code>/mode #ourchannel +b $c:#*lame*</code>

== Realname ==

The $r (realname/gecos) type prevents users with a matching realname from joining your channel.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $r:<mask>
|-
|}

If we wanted to prevent users who had the word ''bot'' in their realname (gecos) from the joining our channel, we could set the following $r type extended ban:

<code>/mode #ourchannel +b $r:*bot*</code>

== Shared bans ==

The $j type allows sharing channel ban lists.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $j:<#channel>
|-
|}

For this example, the name of our channel is ''#ourchannel'' and we want to use ''#shared''<nowiki>'</nowiki>s channel ban list with our own. So, to do this we could set the following $j type extended ban:

<code>/mode #ourchannel +b $j:#shared</code>

Now, whenever a user tries to join our channel, ''#ourchannel'', they'll be checked against ''#shared''<nowiki>'</nowiki>s ban list in addition to our own ban list. If a match is found in either ban list, the user will be prevented from joining.

== Text bans ==

The $t (text) type allows channel operators to specify words (wildcards supported) that will be blocked if the user's message or notice to the channel matches it.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $t:<#mask>
|-
|}

Let's say we wanted to block all channel messages and notices that contained the word ''damn'', regardless of the user sending it. To do this we could set the following $t type extended ban:

<code>/mode #ourchannel +b $t:*damn*</code>

== Negation / Reverse logic ==

If "~" is prepended to the type of an extended ban, then the result of the comparison is negated. In other words, it will have a reversed effect.

Let's say we wanted to allow users to join our channel ONLY if they're already present in #darenet. To do this, we would set a $c type extended ban, by prepending "~" to the type flag:

<code>/mode #ourchannel +b $~c:#darenet</code>

== Assistance ==

Should you need assistance using the extended bans feature, feel free to stop by #help.

[[Category:All]] [[Category:Documentation]]

Extended Bans

2014-06-29T22:41:24Z

Admin:

Extended bans allow different checks than the usual nick!user@host (hostmask) match to determine whether someone should be banned from the channel, allowing channel operators more flexibility and control over their channel's ban list. On DareNET, extended bans are of the form '''<code>$[~]<type>:<data></code>'''. Where <type> is one character (case sensitive) and determines the type of match that is to be used. If the tilde (~) is used, the result of the check will be negated.

The following types of extended bans are currently supported:

{| class="simpletable" width="100%"
! style="text-align: center;" | Type
! style="text-align: center;" | Name
! style="text-align: left;" | Purpose
|-
| style="text-align: center;" | $a
| style="text-align: center;" | Account
| If a user's account name matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $c
| style="text-align: center;" | Channel
| If a user is in a channel that matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $j
| style="text-align: center;" | Shared Bans
| If a user matches a ban on the channel who's ban list is being shared, (s)he will be unable to join.
|-
| style="text-align: center;" | $r
| style="text-align: center;" | Realname
| If a user's realname (gecos) matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $t
| style="text-align: center;" | Text
| Allows you to specify text that will be blocked if a user's privmsg or notice to the channel contains it.
|-
|}<br />

== Account ==

The $a (account) type allows you to ban authed users who's account name matches the specified account mask.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $a:<mask>
|-
|}

If we wanted to ban all users who's account name contained the word ''joe'', we could set the following $a type extended ban:

<code>/mode #ourchannel +b $a:*joe*</code>

== Channel ==

The $c (channel) type prevents users who are in a matching channel from joining your channel.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $c:<#channel>
|-
|}

If we wanted to prevent users who are in channels with the word ''lame'' in its name from joining our channel, we could set the following $c type extended ban.

<code>/mode #ourchannel +b $c:#*lame*</code>

== Realname ==

The $r (realname/gecos) type prevents users with a matching realname from joining your channel.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $r:<mask>
|-
|}

If we wanted to prevent users who had the word ''bot'' in their realname (gecos) from the joining our channel, we could set the following $r type extended ban:

<code>/mode #ourchannel +b $r:*bot*</code>

== Shared bans ==

The $j type allows sharing channel ban lists.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $j:<#channel>
|-
|}

For this example, the name of our channel is ''#ourchannel'' and we want to use ''#shared''<nowiki>'</nowiki>s channel ban list with our own. So, to do this we could set the following $j type extended ban:

<code>/mode #ourchannel +b $j:#shared</code>

Now, whenever a user tries to join our channel, ''#ourchannel'', they'll be checked against ''#shared''<nowiki>'</nowiki>s ban list in addition to our own ban list. If a match is found in either ban list, the user will be prevented from joining.

== Text bans ==

The $t (text) type allows channel operators to specify words (wildcards supported) that will be blocked if the user's message or notice to the channel matches it.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $t:<#mask>
|-
|}

Let's say we wanted to block all channel messages and notices that contained the word ''damn'', regardless of the user sending it. To do this we could set the following $t type extended ban:

<code>/mode #ourchannel +b $t:*damn*</code>

== Negation / Reverse logic ==

If "~" is prepended to the type of an extended ban, then the result of the comparison is negated. In other words, it will have a reversed effect.

Let's say we wanted to allow users to join our channel ONLY if they're already present in #darenet. To do this, we would set a $c type extended ban, but prepending "~" to the type flag:

<code>/mode #ourchannel +b $~c:#darenet</code>

== Assistance ==

Should you need assistance using the extended bans feature, feel free to stop by #help.

[[Category:All]] [[Category:Documentation]]

User Modes

2014-06-26T09:31:10Z

Admin: Updated for ircd-dn 2.x

The following user modes are available on DareNET.

{| class="simpletable" width="100%"
! style="text-align: center;" | Mode
! style="text-align: left;" | Name
! style="text-align: left;" | Description
|-
| style="text-align: center;" | +a
| style="text-align: left;" | [[Image:User delete.png]] Administrator
| Denotes a server administrator on the network, and grants a few extra privileges.
|-
| style="text-align: center;" | +d
| style="text-align: left;" | Deaf
| Prevents you from receiving channel messages.
|-
| style="text-align: center;" | +g
| style="text-align: left;" | [[Image:User delete.png]] Debug
| Receives debug notices (if debugmode enabled).
|-
| style="text-align: center;" | +i
| style="text-align: left;" | Invisible
| Prevents users who do not know your exact nickname from finding you through /WHO.
|-
| style="text-align: center;" | +I
| style="text-align: left;" | [[Image:User delete.png]] Hide idle time
| Prevents users from seeing your idle time in /WHOIS replies.
|-
| style="text-align: center;" | +k
| style="text-align: left;" | [[Image:User delete.png]] Network service
| Denotes a network service, preventing them from being kicked/killed/deoped.
|-
| style="text-align: center;" | +n
| style="text-align: left;" | [[Image:User delete.png]] Hide channels
| Prevents users from seeing what channels you're in, in /WHOIS replies.
|-
| style="text-align: center;" | +N
| style="text-align: left;" | [[Image:User delete.png]] Network administrator
| Denotes a network administrator on the network, and grants a few extra privileges.
|-
| style="text-align: center;" | +o
| style="text-align: left;" | [[Image:User delete.png]] Operator
| Denotes an IRC operator on the network, and grants a few extra privileges.
|-
| style="text-align: center;" | +O
| style="text-align: left;" | [[Image:User delete.png]] Local operator
| Denotes a local operator, and grants a few extra privileges.
|-
| style="text-align: center;" | +P
| style="text-align: left;" | [[Image:User delete.png]] Whois paranoia
| Allows you to see when a user performs a /WHOIS on you.
|-
| style="text-align: center;" | +R
| style="text-align: left;" | Registered-only privmsg
| Prevents non-authed users from private messaging you.
|-
| style="text-align: center;" | +s
| style="text-align: left;" | Server notices
| Receives server notices. See [[Server Notice Masks (SNOMASK)|SNOMASKs]] for more information.
|-
| style="text-align: center;" | +w
| style="text-align: left;" | Wall messages
| Allows you to see important notices about the status of the network from staff.
|-
| style="text-align: center;" | +x
| style="text-align: left;" | Hostmasking
| Enables hostmasking. Note, you must be authed to N for it to take affect.
|}

[[Image:User delete.png]] <small>= denotes modes which are restricted to DareNET staff.</small>

[[Category:All]] [[Category:Documentation]]

Channel Modes

2014-06-26T09:04:17Z

Admin: Updated for ircd-dn 2.x

The following channel modes are available on DareNET

{| class="simpletable" width="100%"
! style="text-align: center;" | Mode
! style="text-align: left;" | Name
! style="text-align: left;" | Description
|-
| style="text-align: center;" | +b
| style="text-align: left;" | Channel ban
| Bans a user from the channel. [[Extended Bans|Extended bans]] are supported.
|-
| style="text-align: center;" | +c
| style="text-align: left;" | No colors
| Channel messages containing ctrl codes/colors are blocked.
|-
| style="text-align: center;" | +C
| style="text-align: left;" | No CTCPs
| CTCP messages addressed to the channel are blocked (ACTION CTCPs (i.e., /me) are still allowed).
|-
| style="text-align: center;" | +D
| style="text-align: left;" | Delayed joins
| See the [[Delayed Joins|delayed joins FAQ]] for details.
|-
| style="text-align: center;" | +e
| style="text-align: left;" | Exceptions
| Excludes matching users from an entry on the channel's ban list, or other join restrictions.
|-
| style="text-align: center;" | +h
| style="text-align: left;" | Half operator
| Grants a user half operator status on the channel. Nicklist prefix: %
|-
| style="text-align: center;" | +i
| style="text-align: left;" | Invite only
| Sets the channel as invite-only, requiring users to be invited to be able to join.
|-
| style="text-align: center;" | +k
| style="text-align: left;" | Keyed
| Sets a key (password) for the channel, which users must specify with /JOIN to be able to join.
|-
| style="text-align: center;" | +l
| style="text-align: left;" | Limit
| Sets a user limit for the channel. Once reached, no further joins will be allowed.
|-
| style="text-align: center;" | +M
| style="text-align: left;" | Moderated
| Non-voiced/(half)opped users may not send messages to the channel.
|-
| style="text-align: center;" | +M
| style="text-align: left;" | Moderated (unregistered)
| Non-authed users may not send messages to the channel.
|-
| style="text-align: center;" | +n
| style="text-align: left;" | No external messages
| Blocks all external messages to the channel (i.e., from users not on the channel).
|-
| style="text-align: center;" | +N
| style="text-align: left;" | No notices
| Blocks notices addressed to the channel.
|-
| style="text-align: center;" | +o
| style="text-align: left;" | Channel operator
| Grants a user channel operator status on the channel. Nicklist prefix: @
|-
| style="text-align: center;" | +p
| style="text-align: left;" | Private
| Marks the channel as private, preventing it from appearing in /LIST.
|-
| style="text-align: center;" | +q
| style="text-align: left;" | Quiet
| Prevents matching users from sending messages to the channel.
|-
| style="text-align: center;" | +r
| style="text-align: left;" | Registered only
| Sets the channel as registered only, preventing non-authed users from joining the channel.
|-
| style="text-align: center;" | +s
| style="text-align: left;" | Secret
| Marks the channel as secret, preventing it from appearing in /LIST and /WHOIS replies.
|-
| style="text-align: center;" | +t
| style="text-align: left;" | Op-only topic
| Only (half)ops may change the channel topic using /TOPIC.
|-
| style="text-align: center;" | +T
| style="text-align: left;" | No multiple targets
| Blocks messages targeting multiple channels (such as those sent by /amsg scripts).
|-
| style="text-align: center;" | +u
| style="text-align: left;" | No quit/parts
| Squelches user /PART and /QUIT reasons, preventing them from being shown to the channel.
|-
| style="text-align: center;" | +v
| style="text-align: left;" | Voice
| Grants a user voice status on the channel. Nicklist prefix: +
|-
| style="text-align: center;" | +z
| style="text-align: left;" | Persistent (registered) [[Image:User delete.png]]
| Prevents the channel from being deleted when the last user leaves, preserving modes/bans/topics/etc. Granted to registered channels.
|-
| style="text-align: center;" | +Z
| style="text-align: left;" | SSL-only
| Prevents non-SSL users from joining the channel.
|-
|}

[[Image:User delete.png]] <small>= denotes modes which are restricted to DareNET staff or services.</small>

[[Category:All]] [[Category:Documentation]]

Extended Bans

2014-06-26T08:35:43Z

Admin: Update for ircd-dn 2.x

Extended bans allow different checks than the usual nick!user@host (hostmask) match to determine whether someone should be banned from the channel, allowing channel operators more flexibility and control over their channel's ban list. On DareNET, extended bans are of the form '''<code>$[!]<type>:<data></code>'''. Where <type> is one character (case sensitive) and determines the type of match that is to be used. If the exclamation mark (!) is used, the result of the check will be negated.

The following types of extended bans are currently supported:

{| class="simpletable" width="100%"
! style="text-align: center;" | Type
! style="text-align: center;" | Name
! style="text-align: left;" | Purpose
|-
| style="text-align: center;" | $a
| style="text-align: center;" | Account
| If a user's account name matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $c
| style="text-align: center;" | Channel
| If a user is in a channel that matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $j
| style="text-align: center;" | Shared Bans
| If a user matches a ban on the channel who's ban list is being shared, (s)he will be unable to join.
|-
| style="text-align: center;" | $r
| style="text-align: center;" | Realname
| If a user's realname (gecos) matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $t
| style="text-align: center;" | Text
| Allows you to specify text that will be blocked if a user's privmsg or notice to the channel contains it.
|-
|}<br />

== Account ==

The $a (account) type allows you to ban authed users who's account name matches the specified account mask.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $a:<mask>
|-
|}

If we wanted to ban all users who's account name contained the word ''joe'', we could set the following $a type extended ban:

<code>/mode #ourchannel +b $a:*joe*</code>

== Channel ==

The $c (channel) type prevents users who are in a matching channel from joining your channel.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $c:<#channel>
|-
|}

If we wanted to prevent users who are in channels with the word ''lame'' in its name from joining our channel, we could set the following $c type extended ban.

<code>/mode #ourchannel +b $c:#*lame*</code>

== Realname ==

The $r (realname/gecos) type prevents users with a matching realname from joining your channel.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $r:<mask>
|-
|}

If we wanted to prevent users who had the word ''bot'' in their realname (gecos) from the joining our channel, we could set the following $r type extended ban:

<code>/mode #ourchannel +b $r:*bot*</code>

== Shared bans ==

The $j type allows sharing channel ban lists.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $j:<#channel>
|-
|}

For this example, the name of our channel is ''#ourchannel'' and we want to use ''#shared''<nowiki>'</nowiki>s channel ban list with our own. So, to do this we could set the following $j type extended ban:

<code>/mode #ourchannel +b $j:#shared</code>

Now, whenever a user tries to join our channel, ''#ourchannel'', they'll be checked against ''#shared''<nowiki>'</nowiki>s ban list in addition to our own ban list. If a match is found in either ban list, the user will be prevented from joining.

== Text bans ==

The $t (text) type allows channel operators to specify words (wildcards supported) that will be blocked if the user's message or notice to the channel matches it.

{| class="simpletable" width="10%"
! style="text-align: left;" | Syntax
|-
| $t:<#mask>
|-
|}

Let's say we wanted to block all channel messages and notices that contained the word ''damn'', regardless of the user sending it. To do this we could set the following $t type extended ban:

<code>/mode #ourchannel +b $t:*damn*</code>

== Negation / Reverse logic ==

If "!" is prepended to the type of an extended ban, then the result of the comparison is negated. In other words, it will have a reversed effect.

Let's say we wanted to allow users to join our channel ONLY if they're already present in #darenet. To do this, we would set a $c type extended ban, but prepending "!" to the type flag:

<code>/mode #ourchannel +b $!c:#darenet</code>

== Assistance ==

Should you need assistance using the extended bans feature, feel free to stop by #help.

[[Category:All]] [[Category:Documentation]]

Development Team

2014-06-25T21:48:37Z

Admin: /* ircd-darenet */

__NOTOC__DareNET's development team is dedicated to actively maintaining and developing the software that's running the network. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev].

== Development Projects ==

DareNET currently develops the following projects:

=== ircd-darenet ===

Latest release: 2.0.6

ircd-darenet 2.x is a fork of the Undernet Universal IRC daemon (u2.10.12 branch), also known as [http://coder-com.undernet.org ircu], and contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset. Some of DareNET's patches include SSL encryption (both server<>server and server<>client), configuration includes, persistent channels, partial IRCv3 support, fakehosts and remote server and user management.

=== evo ===

Latest release: 1.0.0

Evo is our account and channel management services running on DareNET, which was forked from GameSurge's [http://www.srvx.net srvx] services. Some of DareNET's patches include channel quotes, title management (HostServ), stronger password hashing, additional channel and user management options, web integration and more.

=== lua-mafia ===

DareNET's implementation of the widely popular Mafia party game (also known as Werewolf). You can play in [https://webchat.darenet.org?channels=#mafia #Mafia]. You'll need a registered account, which you can get [https://www.darenet.org/signup here] (don't worry, it's free!).

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] have been incorporated upstream.

Our other projects, including those listed on this page, are highly customized to our network and so publishing them would not make much sense. While we may eventually release ircd-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-24T07:50:48Z

Admin: /* evo */

__NOTOC__DareNET's development team is dedicated to actively maintaining and developing the software that's running the network. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev].

== Development Projects ==

DareNET currently develops the following projects:

=== ircd-darenet ===

Latest release: 2.0.6

ircd-darenet 2.x is a fork of the Undernet Universal IRC daemon (u2.10.12 branch), also known as [http://coder-com.undernet.org ircu], and contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset. Some of DareNET's patches include SSL encryption (both server<>server and server<>client), persistent channels, partial IRCv3 support, fakehosts and remote server and user management.

=== evo ===

Latest release: 1.0.0

Evo is our account and channel management services running on DareNET, which was forked from GameSurge's [http://www.srvx.net srvx] services. Some of DareNET's patches include channel quotes, title management (HostServ), stronger password hashing, additional channel and user management options, web integration and more.

=== lua-mafia ===

DareNET's implementation of the widely popular Mafia party game (also known as Werewolf). You can play in [https://webchat.darenet.org?channels=#mafia #Mafia]. You'll need a registered account, which you can get [https://www.darenet.org/signup here] (don't worry, it's free!).

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] have been incorporated upstream.

Our other projects, including those listed on this page, are highly customized to our network and so publishing them would not make much sense. While we may eventually release ircd-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-24T07:50:37Z

Admin: /* ircd-darenet */

__NOTOC__DareNET's development team is dedicated to actively maintaining and developing the software that's running the network. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev].

== Development Projects ==

DareNET currently develops the following projects:

=== ircd-darenet ===

Latest release: 2.0.6

ircd-darenet 2.x is a fork of the Undernet Universal IRC daemon (u2.10.12 branch), also known as [http://coder-com.undernet.org ircu], and contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset. Some of DareNET's patches include SSL encryption (both server<>server and server<>client), persistent channels, partial IRCv3 support, fakehosts and remote server and user management.

=== evo ===

Current version: 1.0.0

Evo is our account and channel management services running on DareNET, which was forked from GameSurge's [http://www.srvx.net srvx] services. Some of DareNET's patches include channel quotes, title management (HostServ), stronger password hashing, additional channel and user management options, web integration and more.

=== lua-mafia ===

DareNET's implementation of the widely popular Mafia party game (also known as Werewolf). You can play in [https://webchat.darenet.org?channels=#mafia #Mafia]. You'll need a registered account, which you can get [https://www.darenet.org/signup here] (don't worry, it's free!).

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] have been incorporated upstream.

Our other projects, including those listed on this page, are highly customized to our network and so publishing them would not make much sense. While we may eventually release ircd-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-22T11:42:38Z

Admin: /* lua-mafia */

__NOTOC__DareNET's development team is dedicated to actively maintaining and developing the software that's running the network. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev].

== Development Projects ==

DareNET currently develops the following projects:

=== ircd-darenet ===

Current version: 2.0.5

ircd-darenet 2.x is a fork of the Undernet Universal IRC daemon (u2.10.12 branch), also known as [http://coder-com.undernet.org ircu], and contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset. Some of DareNET's patches include SSL encryption (both server<>server and server<>client), persistent channels, partial IRCv3 support, fakehosts and remote server and user management.

=== evo ===

Current version: 1.0.0

Evo is our account and channel management services running on DareNET, which was forked from GameSurge's [http://www.srvx.net srvx] services. Some of DareNET's patches include channel quotes, title management (HostServ), stronger password hashing, additional channel and user management options, web integration and more.

=== lua-mafia ===

DareNET's implementation of the widely popular Mafia party game (also known as Werewolf). You can play in [https://webchat.darenet.org?channels=#mafia #Mafia]. You'll need a registered account, which you can get [https://www.darenet.org/signup here] (don't worry, it's free!).

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] have been incorporated upstream.

Our other projects, including those listed on this page, are highly customized to our network and so publishing them would not make much sense. While we may eventually release ircd-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-20T19:59:51Z

Admin:

__NOTOC__DareNET's development team is dedicated to actively maintaining and developing the software that's running the network. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev].

== Development Projects ==

DareNET currently develops the following projects:

=== ircd-darenet ===

Current version: 2.0.5

ircd-darenet 2.x is a fork of the Undernet Universal IRC daemon (u2.10.12 branch), also known as [http://coder-com.undernet.org ircu], and contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset. Some of DareNET's patches include SSL encryption (both server<>server and server<>client), persistent channels, partial IRCv3 support, fakehosts and remote server and user management.

=== evo ===

Current version: 1.0.0

Evo is our account and channel management services running on DareNET, which was forked from GameSurge's [http://www.srvx.net srvx] services. Some of DareNET's patches include channel quotes, title management (HostServ), stronger password hashing, additional channel and user management options, web integration and more.

=== lua-mafia ===

DareNET's implementation of the widely popular Mafia parlor game. You can play in [https://webchat.darenet.org?channels=#mafia #Mafia]. You'll need a registered account, which you can get [https://www.darenet.org/signup here] (don't worry, it's free!).

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] have been incorporated upstream.

Our other projects, including those listed on this page, are highly customized to our network and so publishing them would not make much sense. While we may eventually release ircd-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-20T19:33:20Z

Admin: /* evo */

__NOTOC__DareNET's development team is dedicated to maintaining the software that's running on the IRC network and its web properties, which includes IRC server daemons, IRC services, a webchat client and the DareNET website. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev] on the network.

== Projects ==

The development team is responsible for developing and maintaining the following projects:

=== ircd-darenet ===

Current version: 2.0.5

ircd-darenet is a fork of Undernet's [http://coder-com.undernet.org ircu] (u2.10.12 branch), and also contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset.

=== evo ===

Current version: 1.0.0

Evo, which is a fork of [http://www.srvx.net srvx], was developed to replace services-darenet (which was forked from [http://evilnet.sf.net X3], itself a fork of an older srvx code base).

=== lua-mafia ===

DareNET's implementation of the widely popular Mafia parlor game. You can play in [https://webchat.darenet.org?channels=#mafia #Mafia]. You'll need a registered account, which you can get [https://www.darenet.org/signup here] (don't worry, it's free!).

=== webchat-darenet ===

webchat-darenet is simply the code name we've given to our series of patches for the popular [http://qwebirc.org qwebirc] client, most of which have now been incorporated upstream. Those which haven't can also be found [https://bitbucket.org/secretagent/qwebirc here]. Much thanks to Chris Porter (slug) for developing this great client, and freely releasing it.

=== website-darenet ===

The current site was built using some great technologies, which include:

* [http://www.php.net PHP] & [http://www.cakephp.org CakePHP]
* [http://www.python.org Python]
* QServer (an external interface to services-darenet)
* [http://www.mysql.com MySQL] & [http://pypi.python.org/pypi/PyMySQL/ PyMySQL]
* [http://redis.io Redis], [https://github.com/nrk/predis Predis] & [https://github.com/andymccurdy/redis-py redis-py]
* [http://jquery.com jQuery]
* [http://nginx.org/ Nginx]
* [http://www.openssl.org/ OpenSSL] & [http://pypi.python.org/pypi/pyOpenSSL pyOpenSSL]

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] can be found [https://bitbucket.org/secretagent/qwebirc here).

While we do plan to eventually release ircd-darenet and services-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-20T19:32:22Z

Admin: /* lua-mafia */

__NOTOC__DareNET's development team is dedicated to maintaining the software that's running on the IRC network and its web properties, which includes IRC server daemons, IRC services, a webchat client and the DareNET website. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev] on the network.

== Projects ==

The development team is responsible for developing and maintaining the following projects:

=== ircd-darenet ===

Current version: 2.0.5

ircd-darenet is a fork of Undernet's [http://coder-com.undernet.org ircu] (u2.10.12 branch), and also contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset.

=== evo ===

Current version: 1.0.0

Evo, which is a fork of [http://www.srvx.net srvx], was developed to replace services-darenet (which was forked from [http://evilnet.sf.net X3], itself a fork of an older srvx code base].

=== lua-mafia ===

DareNET's implementation of the widely popular Mafia parlor game. You can play in [https://webchat.darenet.org?channels=#mafia #Mafia]. You'll need a registered account, which you can get [https://www.darenet.org/signup here] (don't worry, it's free!).

=== webchat-darenet ===

webchat-darenet is simply the code name we've given to our series of patches for the popular [http://qwebirc.org qwebirc] client, most of which have now been incorporated upstream. Those which haven't can also be found [https://bitbucket.org/secretagent/qwebirc here]. Much thanks to Chris Porter (slug) for developing this great client, and freely releasing it.

=== website-darenet ===

The current site was built using some great technologies, which include:

* [http://www.php.net PHP] & [http://www.cakephp.org CakePHP]
* [http://www.python.org Python]
* QServer (an external interface to services-darenet)
* [http://www.mysql.com MySQL] & [http://pypi.python.org/pypi/PyMySQL/ PyMySQL]
* [http://redis.io Redis], [https://github.com/nrk/predis Predis] & [https://github.com/andymccurdy/redis-py redis-py]
* [http://jquery.com jQuery]
* [http://nginx.org/ Nginx]
* [http://www.openssl.org/ OpenSSL] & [http://pypi.python.org/pypi/pyOpenSSL pyOpenSSL]

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] can be found [https://bitbucket.org/secretagent/qwebirc here).

While we do plan to eventually release ircd-darenet and services-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-16T23:19:59Z

Admin: /* lua-mafia */

__NOTOC__DareNET's development team is dedicated to maintaining the software that's running on the IRC network and its web properties, which includes IRC server daemons, IRC services, a webchat client and the DareNET website. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev] on the network.

== Projects ==

The development team is responsible for developing and maintaining the following projects:

=== ircd-darenet ===

Current version: 2.0.5

ircd-darenet is a fork of Undernet's [http://coder-com.undernet.org ircu] (u2.10.12 branch), and also contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset.

=== evo ===

Current version: 1.0.0

Evo, which is a fork of [http://www.srvx.net srvx], was developed to replace services-darenet (which was forked from [http://evilnet.sf.net X3], itself a fork of an older srvx code base].

=== lua-mafia ===

DareNET's implementation of the widely popular Mafia parlor game. You can play in [https://webchat.darenet.org?channels=#mafia #Mafia].

=== webchat-darenet ===

webchat-darenet is simply the code name we've given to our series of patches for the popular [http://qwebirc.org qwebirc] client, most of which have now been incorporated upstream. Those which haven't can also be found [https://bitbucket.org/secretagent/qwebirc here]. Much thanks to Chris Porter (slug) for developing this great client, and freely releasing it.

=== website-darenet ===

The current site was built using some great technologies, which include:

* [http://www.php.net PHP] & [http://www.cakephp.org CakePHP]
* [http://www.python.org Python]
* QServer (an external interface to services-darenet)
* [http://www.mysql.com MySQL] & [http://pypi.python.org/pypi/PyMySQL/ PyMySQL]
* [http://redis.io Redis], [https://github.com/nrk/predis Predis] & [https://github.com/andymccurdy/redis-py redis-py]
* [http://jquery.com jQuery]
* [http://nginx.org/ Nginx]
* [http://www.openssl.org/ OpenSSL] & [http://pypi.python.org/pypi/pyOpenSSL pyOpenSSL]

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] can be found [https://bitbucket.org/secretagent/qwebirc here).

While we do plan to eventually release ircd-darenet and services-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-16T23:19:46Z

Admin: /* Projects */

__NOTOC__DareNET's development team is dedicated to maintaining the software that's running on the IRC network and its web properties, which includes IRC server daemons, IRC services, a webchat client and the DareNET website. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev] on the network.

== Projects ==

The development team is responsible for developing and maintaining the following projects:

=== ircd-darenet ===

Current version: 2.0.5

ircd-darenet is a fork of Undernet's [http://coder-com.undernet.org ircu] (u2.10.12 branch), and also contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset.

=== evo ===

Current version: 1.0.0

Evo, which is a fork of [http://www.srvx.net srvx], was developed to replace services-darenet (which was forked from [http://evilnet.sf.net X3], itself a fork of an older srvx code base].

== lua-mafia ==

DareNET's implementation of the widely popular Mafia parlor game. You can play in [https://webchat.darenet.org?channels=#mafia #Mafia].

=== webchat-darenet ===

webchat-darenet is simply the code name we've given to our series of patches for the popular [http://qwebirc.org qwebirc] client, most of which have now been incorporated upstream. Those which haven't can also be found [https://bitbucket.org/secretagent/qwebirc here]. Much thanks to Chris Porter (slug) for developing this great client, and freely releasing it.

=== website-darenet ===

The current site was built using some great technologies, which include:

* [http://www.php.net PHP] & [http://www.cakephp.org CakePHP]
* [http://www.python.org Python]
* QServer (an external interface to services-darenet)
* [http://www.mysql.com MySQL] & [http://pypi.python.org/pypi/PyMySQL/ PyMySQL]
* [http://redis.io Redis], [https://github.com/nrk/predis Predis] & [https://github.com/andymccurdy/redis-py redis-py]
* [http://jquery.com jQuery]
* [http://nginx.org/ Nginx]
* [http://www.openssl.org/ OpenSSL] & [http://pypi.python.org/pypi/pyOpenSSL pyOpenSSL]

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] can be found [https://bitbucket.org/secretagent/qwebirc here).

While we do plan to eventually release ircd-darenet and services-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-16T23:16:50Z

Admin: /* Where can I download projects? */

__NOTOC__DareNET's development team is dedicated to maintaining the software that's running on the IRC network and its web properties, which includes IRC server daemons, IRC services, a webchat client and the DareNET website. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev] on the network.

== Projects ==

The development team is responsible for developing and maintaining the following projects:

=== ircd-darenet ===

Current version: 2.0.5

ircd-darenet is a fork of Undernet's [http://coder-com.undernet.org ircu] (u2.10.12 branch), and also contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset.

=== evo ===

Current version: 1.0.0

Evo, which is a fork of [http://www.srvx.net srvx], was developed to replace services-darenet (which was forked from [http://evilnet.sf.net X3], itself a fork of an older srvx code base].

=== webchat-darenet ===

webchat-darenet is simply the code name we've given to our series of patches for the popular [http://qwebirc.org qwebirc] client, most of which have now been incorporated upstream. Those which haven't can also be found [https://bitbucket.org/secretagent/qwebirc here]. Much thanks to Chris Porter (slug) for developing this great client, and freely releasing it.

=== website-darenet ===

The current site was built using some great technologies, which include:

* [http://www.php.net PHP] & [http://www.cakephp.org CakePHP]
* [http://www.python.org Python]
* QServer (an external interface to services-darenet)
* [http://www.mysql.com MySQL] & [http://pypi.python.org/pypi/PyMySQL/ PyMySQL]
* [http://redis.io Redis], [https://github.com/nrk/predis Predis] & [https://github.com/andymccurdy/redis-py redis-py]
* [http://jquery.com jQuery]
* [http://nginx.org/ Nginx]
* [http://www.openssl.org/ OpenSSL] & [http://pypi.python.org/pypi/pyOpenSSL pyOpenSSL]

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] can be found [https://bitbucket.org/secretagent/qwebirc here).

While we do plan to eventually release ircd-darenet and services-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]
* [https://hg.quakenet.org/newserv newserv]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Development Team

2014-06-16T23:11:36Z

Admin:

__NOTOC__DareNET's development team is dedicated to maintaining the software that's running on the IRC network and its web properties, which includes IRC server daemons, IRC services, a webchat client and the DareNET website. The team can be reached via email at dev@darenet.org or in [https://webchat.darenet.org/?channels=dev #dev] on the network.

== Projects ==

The development team is responsible for developing and maintaining the following projects:

=== ircd-darenet ===

Current version: 2.0.5

ircd-darenet is a fork of Undernet's [http://coder-com.undernet.org ircu] (u2.10.12 branch), and also contains various code from Quakenet's [http://dev.quakenet.org snircd] patchset.

=== evo ===

Current version: 1.0.0

Evo, which is a fork of [http://www.srvx.net srvx], was developed to replace services-darenet (which was forked from [http://evilnet.sf.net X3], itself a fork of an older srvx code base].

=== webchat-darenet ===

webchat-darenet is simply the code name we've given to our series of patches for the popular [http://qwebirc.org qwebirc] client, most of which have now been incorporated upstream. Those which haven't can also be found [https://bitbucket.org/secretagent/qwebirc here]. Much thanks to Chris Porter (slug) for developing this great client, and freely releasing it.

=== website-darenet ===

The current site was built using some great technologies, which include:

* [http://www.php.net PHP] & [http://www.cakephp.org CakePHP]
* [http://www.python.org Python]
* QServer (an external interface to services-darenet)
* [http://www.mysql.com MySQL] & [http://pypi.python.org/pypi/PyMySQL/ PyMySQL]
* [http://redis.io Redis], [https://github.com/nrk/predis Predis] & [https://github.com/andymccurdy/redis-py redis-py]
* [http://jquery.com jQuery]
* [http://nginx.org/ Nginx]
* [http://www.openssl.org/ OpenSSL] & [http://pypi.python.org/pypi/pyOpenSSL pyOpenSSL]

== FAQ ==

=== Where can I download projects? ===

Most of our patches to [http://www.qwebirc.org qwebirc] can be found [https://bitbucket.org/secretagent/qwebirc here).

While we do plan to eventually release ircd-darenet and services-darenet, your patience is required until it happens. In the mean time, we recommend taking at look at the following projects (in no particular order), for IRC daemons and services with comparable feature sets:

* [http://www.atheme.org/project/charybdis Charybdis]
* [http://dev.quakenet.org snircd]
* [http://evilnet.sf.net Nefarious ircu]
* [http://srvx.net srvx]
* [http://www.atheme.net/download-atheme.php Atheme IRC Services]
* [http://evilnet.sf.net X3]

=== I found a bug, where can I report it? ===

Please send any bug reports to dev@darenet.org. We can also be reached in [https://webchat.darenet.org/?channels=dev #dev] on the network.

=== How do I get involved with DareNET Development? ===

If you're interested in contributing to one of DareNET's projects, whether it be with actual development or improving documentation, drop us a line at dev@darenet.org. If you have a GitHub, Bitbucket, Sourceforge, etc. profile, feel free to include links to those as well.

Policy:Proposals/2

2014-01-13T10:41:24Z

Admin: /* Voting procedure */ no longer needed

'''Proposal #2 - Infrastructure Team: Policy and Operating Procedure'''

== Overview ==

The Infrastructure team is subordinate to the DareNET Operations team for the purpose of maintaining a stable, secure, geographically diverse and well structured infrastructure for the organization as a whole. As such, the team is charged with handling and reviewing link applications, maintaining and monitoring all servers linked to the network, and administering the DNS pool. Communication between members of the team is effected by means of a private mailing list. Communications between the team and other relevant entities are handled by the Infrastructure Team Manager.

== Membership ==

* '''Manager:''' Appointed by the Operations team for a one year term, with no restrictions on the number of consecutive terms that may be served. The team manager is charged with ensuring the team is adequately staffed, supervising the overall performance of other team members, maintaining the P10 Server Numerics listing, notification to applicants, and liaising with all relevant parties through established communication channels. Where possible, they may delegate some of these responsibilities to other team members.
* '''Members:''' Appointed by the team manager for an indefinite term. Members are charged with reviewing applications, reviewing existing servers for performance, updating server configurations, maintaining the DNS pool, voting in team Call for Votes (CFVs), etc.

== Policy decisions ==

Policy decisions include, but are not limited to, making changes to this document, making changes to the linking guidelines, linking/delinking servers or voting to bring action against a server. Voting procedure:

* A vote is called by the team manager or designee.
* A discussion is conducted on the mailing list and opinions are posted by the members.
* Within 4 days, each member will submit their vote to the mailing list. The vote will pass with a simple majority. In the event of a tie, the Manager may cast the tiebreaking vote.

== New links procedure ==

''(finish me!)''

== Testlink review procedure ==

''(finish me!)''

== Server delink procedure ==

There are two primary types of delink: Voluntary and Involuntary.

=== Voluntary ===

Servers which voluntarily delink are requested to give the Infrastructure team as much advance notice of the decision as possible to facilitate a smooth transition. Those servers leaving on their own accord, provided they are in good standing, have the option to return at a later date in full link status provided the team is satisfied that any network changes that may have been made (e.g., different uplinks) will not render the server unusable on DareNET, and that the new server is operated by the same administrator. The Infrastructure team MUST be made aware of any such network changes, including traceroutes/pings from the server's new location, BEFORE any attempt to relink the server.

=== Involuntary ===

A server may be involuntarily delinked due to an unexcused absence, or should the Infrastructure and Operations teams decide it's no longer in the best interest of DareNET for the server to remain linked to the network.

Servers that remain in absence from the network for a period of two weeks (fourteen days) will automatically be considered delinked. No CFV for the delinked server will be held in this case, though notification of the delink will be forwarded to the Operations team.

At the discretion of the Infrastructure team, a server may be granted an extended absence provided that the server's admin can give just cause for the absence, and can guarantee its return within a reasonable timeframe. To be granted such an extension, the server admin must make the request PRIOR to the end of the initial two week absentee period.

Servers which are involuntarily delinked may reapply for a link after a six month period following the full application procedure, including the initial testlink period.

For reasons of security or other situations where it's felt the server may have a negative impact on the rest of the network, the team may review that server's link at any time. Such possible circumstances include, but are not solely limited to, server compromised, other services running on the server which were not previously agreed on, uplink connectivity failing to evolve with growth, a complete change of network locations or connectivity.

A server may be temporarily delinked (juped) if it shows considerable disruption to the rest of the network. This action should be no longer than five days; otherwise, it qualifies for delink.

== Appellate Procedure ==

Should an individual or server admin wish to appeal the decision of the Infrastructure team, they shall immediately notify the Infrastructure Manager of their decision to appeal. The appellate must inform the Manager of their appeal within 48 hours of the decision they're appealing. Failure to do so will result in the assumption that there is no intent to appeal, and the course of action will effected.

The appellate procedure only exists for decisions concerning servers already linked to DareNET, whether in a testlink or permlink status. Decisions regarding applications for new servers may not be appealed at this time. Upon receiving a valid appeal, the Manager shall note the appeal and notify the Operations team. The Operations team will then hold a Call for Discussion (CFD) and a Call for Votes (CFV) on the matter. The decision reached by the Operations team shall be final. The Manager shall notify the appellate of the Operations team's decision.

Should an appeal overturn the decision of the Infrastructure team, the Manager shall liaise with all relevant parties to return the appellate to the status held prior to the decision that caused the appeal. In the case of a testlink server, the server shall be returned to testlink status for a minimum period of 30 days. In the case of a permlink server, the server shall be returned to permlink status.

Note: This procedure only applies to decisions of the Infrastructure team. Appeals to decisions made by the Operations team should be directed to the Executive Board.

Policy:Proposals/2

2014-01-13T10:40:16Z

Admin: /* Involuntary */

'''Proposal #2 - Infrastructure Team: Policy and Operating Procedure'''

== Overview ==

The Infrastructure team is subordinate to the DareNET Operations team for the purpose of maintaining a stable, secure, geographically diverse and well structured infrastructure for the organization as a whole. As such, the team is charged with handling and reviewing link applications, maintaining and monitoring all servers linked to the network, and administering the DNS pool. Communication between members of the team is effected by means of a private mailing list. Communications between the team and other relevant entities are handled by the Infrastructure Team Manager.

== Membership ==

* '''Manager:''' Appointed by the Operations team for a one year term, with no restrictions on the number of consecutive terms that may be served. The team manager is charged with ensuring the team is adequately staffed, supervising the overall performance of other team members, maintaining the P10 Server Numerics listing, notification to applicants, and liaising with all relevant parties through established communication channels. Where possible, they may delegate some of these responsibilities to other team members.
* '''Members:''' Appointed by the team manager for an indefinite term. Members are charged with reviewing applications, reviewing existing servers for performance, updating server configurations, maintaining the DNS pool, voting in team Call for Votes (CFVs), etc.

== Policy decisions ==

Policy decisions include, but are not limited to, making changes to this document, making changes to the linking guidelines, linking/delinking servers or voting to bring action against a server. Voting procedure:

* A vote is called by the team manager or designee.
* A discussion is conducted on the mailing list and opinions are posted by the members.
* Within 4 days, each member will submit their vote to the mailing list. The vote will pass with a simple majority. In the event of a tie, the Manager may cast the tiebreaking vote.

== Voting procedure ==

''(finish me!)''

== New links procedure ==

''(finish me!)''

== Testlink review procedure ==

''(finish me!)''

== Server delink procedure ==

There are two primary types of delink: Voluntary and Involuntary.

=== Voluntary ===

Servers which voluntarily delink are requested to give the Infrastructure team as much advance notice of the decision as possible to facilitate a smooth transition. Those servers leaving on their own accord, provided they are in good standing, have the option to return at a later date in full link status provided the team is satisfied that any network changes that may have been made (e.g., different uplinks) will not render the server unusable on DareNET, and that the new server is operated by the same administrator. The Infrastructure team MUST be made aware of any such network changes, including traceroutes/pings from the server's new location, BEFORE any attempt to relink the server.

=== Involuntary ===

A server may be involuntarily delinked due to an unexcused absence, or should the Infrastructure and Operations teams decide it's no longer in the best interest of DareNET for the server to remain linked to the network.

Servers that remain in absence from the network for a period of two weeks (fourteen days) will automatically be considered delinked. No CFV for the delinked server will be held in this case, though notification of the delink will be forwarded to the Operations team.

At the discretion of the Infrastructure team, a server may be granted an extended absence provided that the server's admin can give just cause for the absence, and can guarantee its return within a reasonable timeframe. To be granted such an extension, the server admin must make the request PRIOR to the end of the initial two week absentee period.

Servers which are involuntarily delinked may reapply for a link after a six month period following the full application procedure, including the initial testlink period.

For reasons of security or other situations where it's felt the server may have a negative impact on the rest of the network, the team may review that server's link at any time. Such possible circumstances include, but are not solely limited to, server compromised, other services running on the server which were not previously agreed on, uplink connectivity failing to evolve with growth, a complete change of network locations or connectivity.

A server may be temporarily delinked (juped) if it shows considerable disruption to the rest of the network. This action should be no longer than five days; otherwise, it qualifies for delink.

== Appellate Procedure ==

Should an individual or server admin wish to appeal the decision of the Infrastructure team, they shall immediately notify the Infrastructure Manager of their decision to appeal. The appellate must inform the Manager of their appeal within 48 hours of the decision they're appealing. Failure to do so will result in the assumption that there is no intent to appeal, and the course of action will effected.

The appellate procedure only exists for decisions concerning servers already linked to DareNET, whether in a testlink or permlink status. Decisions regarding applications for new servers may not be appealed at this time. Upon receiving a valid appeal, the Manager shall note the appeal and notify the Operations team. The Operations team will then hold a Call for Discussion (CFD) and a Call for Votes (CFV) on the matter. The decision reached by the Operations team shall be final. The Manager shall notify the appellate of the Operations team's decision.

Should an appeal overturn the decision of the Infrastructure team, the Manager shall liaise with all relevant parties to return the appellate to the status held prior to the decision that caused the appeal. In the case of a testlink server, the server shall be returned to testlink status for a minimum period of 30 days. In the case of a permlink server, the server shall be returned to permlink status.

Note: This procedure only applies to decisions of the Infrastructure team. Appeals to decisions made by the Operations team should be directed to the Executive Board.

Policy:Proposals/2

2014-01-13T10:37:25Z

Admin: /* Policy decisions */

'''Proposal #2 - Infrastructure Team: Policy and Operating Procedure'''

== Overview ==

The Infrastructure team is subordinate to the DareNET Operations team for the purpose of maintaining a stable, secure, geographically diverse and well structured infrastructure for the organization as a whole. As such, the team is charged with handling and reviewing link applications, maintaining and monitoring all servers linked to the network, and administering the DNS pool. Communication between members of the team is effected by means of a private mailing list. Communications between the team and other relevant entities are handled by the Infrastructure Team Manager.

== Membership ==

* '''Manager:''' Appointed by the Operations team for a one year term, with no restrictions on the number of consecutive terms that may be served. The team manager is charged with ensuring the team is adequately staffed, supervising the overall performance of other team members, maintaining the P10 Server Numerics listing, notification to applicants, and liaising with all relevant parties through established communication channels. Where possible, they may delegate some of these responsibilities to other team members.
* '''Members:''' Appointed by the team manager for an indefinite term. Members are charged with reviewing applications, reviewing existing servers for performance, updating server configurations, maintaining the DNS pool, voting in team Call for Votes (CFVs), etc.

== Policy decisions ==

Policy decisions include, but are not limited to, making changes to this document, making changes to the linking guidelines, linking/delinking servers or voting to bring action against a server. Voting procedure:

* A vote is called by the team manager or designee.
* A discussion is conducted on the mailing list and opinions are posted by the members.
* Within 4 days, each member will submit their vote to the mailing list. The vote will pass with a simple majority. In the event of a tie, the Manager may cast the tiebreaking vote.

== Voting procedure ==

''(finish me!)''

== New links procedure ==

''(finish me!)''

== Testlink review procedure ==

''(finish me!)''

== Server delink procedure ==

There are two primary types of delink: Voluntary and Involuntary.

=== Voluntary ===

Servers which voluntarily delink are requested to give the Infrastructure team as much advance notice of the decision as possible to facilitate a smooth transition. Those servers leaving on their own accord, provided they are in good standing, have the option to return at a later date in full link status provided the team is satisfied that any network changes that may have been made (e.g., different uplinks) will not render the server unusable on DareNET, and that the new server is operated by the same administrator. The Infrastructure team MUST be made aware of any such network changes, including traceroutes/pings from the server's new location, BEFORE any attempt to relink the server.

=== Involuntary ===

A server may be involuntarily delinked due to an unexcused absence, or should the Infrastructure and Operations teams decide it's no longer in the best interest of DareNET for the server to remain linked to the network.

Servers that remain in absence from the network for a period of two weeks (fourteen days) will automatically be considered delinked. No CFV for the delinked server will be held in this case, though notification of the delink will be forwarded to the Operations team.

At the discretion of the Infrastructure team, a server may be granted an extended absence provided that the server's admin can give just cause for the absence, and can guarantee its return within a reasonable timeframe. To be granted such an extension, the server admin must make the request PRIOR to the end of the initial two week absentee period.

Servers which are involuntarily delinked may reapply for a link after a six month period following the full application procedure, including the initial testlink period.

For reasons of security or other situations where it's felt the server may have a negative impact on the rest of the network, the team may review that server's link at any time. Such possible circumstances include, but are not solely limited to, server compromised, other services running on the server which were not previously agreed on, uplink connectivity failing to evolve with growth, a complete change of network locations or connectivity.

== Appellate Procedure ==

Should an individual or server admin wish to appeal the decision of the Infrastructure team, they shall immediately notify the Infrastructure Manager of their decision to appeal. The appellate must inform the Manager of their appeal within 48 hours of the decision they're appealing. Failure to do so will result in the assumption that there is no intent to appeal, and the course of action will effected.

The appellate procedure only exists for decisions concerning servers already linked to DareNET, whether in a testlink or permlink status. Decisions regarding applications for new servers may not be appealed at this time. Upon receiving a valid appeal, the Manager shall note the appeal and notify the Operations team. The Operations team will then hold a Call for Discussion (CFD) and a Call for Votes (CFV) on the matter. The decision reached by the Operations team shall be final. The Manager shall notify the appellate of the Operations team's decision.

Should an appeal overturn the decision of the Infrastructure team, the Manager shall liaise with all relevant parties to return the appellate to the status held prior to the decision that caused the appeal. In the case of a testlink server, the server shall be returned to testlink status for a minimum period of 30 days. In the case of a permlink server, the server shall be returned to permlink status.

Note: This procedure only applies to decisions of the Infrastructure team. Appeals to decisions made by the Operations team should be directed to the Executive Board.

Policy:Proposals/2

2014-01-13T10:30:11Z

Admin: /* Overview */ typos

'''Proposal #2 - Infrastructure Team: Policy and Operating Procedure'''

== Overview ==

The Infrastructure team is subordinate to the DareNET Operations team for the purpose of maintaining a stable, secure, geographically diverse and well structured infrastructure for the organization as a whole. As such, the team is charged with handling and reviewing link applications, maintaining and monitoring all servers linked to the network, and administering the DNS pool. Communication between members of the team is effected by means of a private mailing list. Communications between the team and other relevant entities are handled by the Infrastructure Team Manager.

== Membership ==

* '''Manager:''' Appointed by the Operations team for a one year term, with no restrictions on the number of consecutive terms that may be served. The team manager is charged with ensuring the team is adequately staffed, supervising the overall performance of other team members, maintaining the P10 Server Numerics listing, notification to applicants, and liaising with all relevant parties through established communication channels. Where possible, they may delegate some of these responsibilities to other team members.
* '''Members:''' Appointed by the team manager for an indefinite term. Members are charged with reviewing applications, reviewing existing servers for performance, updating server configurations, maintaining the DNS pool, voting in team Call for Votes (CFVs), etc.

== Policy decisions ==

''(finish me!)''

== Voting procedure ==

''(finish me!)''

== New links procedure ==

''(finish me!)''

== Testlink review procedure ==

''(finish me!)''

== Server delink procedure ==

There are two primary types of delink: Voluntary and Involuntary.

=== Voluntary ===

Servers which voluntarily delink are requested to give the Infrastructure team as much advance notice of the decision as possible to facilitate a smooth transition. Those servers leaving on their own accord, provided they are in good standing, have the option to return at a later date in full link status provided the team is satisfied that any network changes that may have been made (e.g., different uplinks) will not render the server unusable on DareNET, and that the new server is operated by the same administrator. The Infrastructure team MUST be made aware of any such network changes, including traceroutes/pings from the server's new location, BEFORE any attempt to relink the server.

=== Involuntary ===

A server may be involuntarily delinked due to an unexcused absence, or should the Infrastructure and Operations teams decide it's no longer in the best interest of DareNET for the server to remain linked to the network.

Servers that remain in absence from the network for a period of two weeks (fourteen days) will automatically be considered delinked. No CFV for the delinked server will be held in this case, though notification of the delink will be forwarded to the Operations team.

At the discretion of the Infrastructure team, a server may be granted an extended absence provided that the server's admin can give just cause for the absence, and can guarantee its return within a reasonable timeframe. To be granted such an extension, the server admin must make the request PRIOR to the end of the initial two week absentee period.

Servers which are involuntarily delinked may reapply for a link after a six month period following the full application procedure, including the initial testlink period.

For reasons of security or other situations where it's felt the server may have a negative impact on the rest of the network, the team may review that server's link at any time. Such possible circumstances include, but are not solely limited to, server compromised, other services running on the server which were not previously agreed on, uplink connectivity failing to evolve with growth, a complete change of network locations or connectivity.

== Appellate Procedure ==

Should an individual or server admin wish to appeal the decision of the Infrastructure team, they shall immediately notify the Infrastructure Manager of their decision to appeal. The appellate must inform the Manager of their appeal within 48 hours of the decision they're appealing. Failure to do so will result in the assumption that there is no intent to appeal, and the course of action will effected.

The appellate procedure only exists for decisions concerning servers already linked to DareNET, whether in a testlink or permlink status. Decisions regarding applications for new servers may not be appealed at this time. Upon receiving a valid appeal, the Manager shall note the appeal and notify the Operations team. The Operations team will then hold a Call for Discussion (CFD) and a Call for Votes (CFV) on the matter. The decision reached by the Operations team shall be final. The Manager shall notify the appellate of the Operations team's decision.

Should an appeal overturn the decision of the Infrastructure team, the Manager shall liaise with all relevant parties to return the appellate to the status held prior to the decision that caused the appeal. In the case of a testlink server, the server shall be returned to testlink status for a minimum period of 30 days. In the case of a permlink server, the server shall be returned to permlink status.

Note: This procedure only applies to decisions of the Infrastructure team. Appeals to decisions made by the Operations team should be directed to the Executive Board.

Policy:Proposals/3

2014-01-13T10:26:25Z

Admin: Created page with ''''Proposal #3 - Operator privilege sets''' Written by culex <pre>Oper privilege sets =================== Ops team gets no special mention -- they're just server admins. "d…'

'''Proposal #3 - Operator privilege sets'''

Written by culex

<pre>Oper privilege sets
===================

Ops team gets no special mention -- they're just server admins.

"dev" means developer of the respective codebase; so "dev" in the section for
evo only means "developers of evo". "All devs" is used instead to refer to all
developers with an O:line.

IRCd
----

All-caps privileges are privs that have no configuration file option; they must
be granted through services instead.

## oper

* local = no; implies:
** whox = yes [This is only about LOGGING /whox, which we should always do]
** display = yes
** chan_limit = yes
** mode_lchan = yes [We should disable local channels anyway, nobody cares]
** deop_lchan = yes [see above]
** show_invis = yes
** show_all_invis = yes
** local_kill = yes
** local_gline = no [local bans make everything a bigger pain]
** see_chan = yes [*override* to no]
** list_chan = yes [*override* to no]
** wide_gline = yes [*override* to no]
** see_opers = yes
** local_opmode = yes [*override* to no; local channels should be disabled]
** force_local_opmode = yes [*override* to no; see above]
** kill = yes [even though it's just a pretty useless toy]
** opmode = yes [Fixing opless channels, etc.]

## support (global oper + support, not support oper, which is a services thing)

These are privileges required to help without joining all the time (which,
given some entry hazards, can be quite annoying). This has also the additional
effect that all opers will strive to get into support team for the extra privs
and thus everyone gets better support.

[inherits from oper]

* see_chan = yes
* list_chan = yes
* unlimit_query = yes [removes all brakes in /who with the other privs above]

## server admin

[inherits from oper]

* admin = yes [allows /shedding, /whois, see bind IP in /stats p]
* set = yes [to be used at request of EB and infra only]
* rehash = yes
* die = yes
* restart = yes

## all devs

[inherits from oper]

## infra

[inherits from oper]

* remoterehash = yes
* jupe = yes
* local_jupe = yes

## EB

[inherits from admin + infra]

(special abilities granted by umode +N: unkillable by non-services, /shedding
if not +a already)

## unused

* hide_oper [given by infra or EB on request if they have a valid reason why
they want to use +H]
* gline [use evo instead, it's easier to track]
* shun [see above]
* zline, wide_zline, local_zline [glines are good enough]
* XTRA_OPER [after setting +X, allows overriding JOIN, KICK, KILL (even against
+k users!), MODE -o (+k user here), PRIVMSG/NOTICE despite modes against
sending being present; way too dangerous for no use scenario]
* CHANSERV [can set +k on self; too dangerous for no use scenario]
* badchan, local_badchan [use evo]

evo
---

Curly braces mean that I'm requesting a level change via modcmd; the levels in
the reference list are the defaults.

ADD* commands have their respectice DEL* command not listed unless the level
differs.

1000 is the max level, given to the first account. Apparently we have some more
opers with level 1000, though. 1000 SHOULD denote "do not use" and 999 means
EB-only.

Command -> OpServ level reference:
ACCESS 0
ADDALERT 800
ADDALERT NOTICE 800
ADDALERT [ACTION] 900
ADDBAD 800 [channels matching *word* get forbidden]
ADDBADCHAN 600 {901}
ADDEXEMPT 800 [channels to never consider forbidden for C]
ADDTRUST 800 [irrelevant, we use newserv for that in dn2]
BAN 100 {600} [can be done with opmode and +b anyway]
BLOCK 100 {600} [equivalent of qakill with optional duration]
CHANINFO 0 {700}
CLEARBANS 300 {600} [can be done with opmode, etc.]
CLEARMODES 400 {600} [opmode etc.]
CLONE 999 {1000}
COLLIDE 800 {900}
CSEARCH 100 {700}
DEHOP 100 {600}
DEHOPALL 400 {600}
DEOP 100 {600}
DEOPALL 400 {600}
DEVOICE 300 {600} [wtf is up with that default being higher?]
DEVOICEALL 300 {600}
DIE 999
DUMP 999 {1000}
EDITTRUST 800 [irrelevant, see ADDTRUST]
GAG 600 [services ignore]
GLINE 600
GSYNC 600
GTRACE 100
HOP 100 {600}
HOPALL 100 {600}
INVITE 100 {700}
INVITEME 100 {999} [invites to the debug channel, not sure if used]
JOIN 601 {900}
JUMP 900
JUPE 900 {800}
KICK 100 {600} [could be done with opmode + /kick anyway]
FORCEKICK 900
KICKALL 400 {600}
KICKBAN 100 {600}
KICKBANALL 450 {600}
LOG 900 {400}
MODE 100 {600}
OP 100 {600}
OPALL 400 {600}
PART 601 {900}
QUERY 0 [gets config value] {100}
RAW 999 {1000}
RECONNECT 900
REFRESHG 600
REFRESHS 600
REHASH 900
REOPEN 900
RESERVE 800 {999}
RESTART 900
SBLOCK 100 [qakill/BLOCK with SHUN] {600}
SET 900
SETTIME 901 {999}
SHUN 600
SSYNC 600
STATS [STAT] 0
STRACE 100
SVSJOIN 999
SVSNICK 999
TRACE 100 {600}
TRACE GLINE 600
TRACE GAG 600
TRACE KILL 600
UNBAN 100 {600}
VOICE 300 {600}
VOICEALL 300 {600}
WARN 800 [adds join/part spam checker, I think] {600}
WHOIS 0 {700 due to showing +s channels}

C + OpServ levels:
CREATENOTE/REMOVENOTE 800 {600}

* oper, admin, all devs: 600
* support: 700
* infra: 800
* dev: 900
* EB: 999

Newserv NOperserv
-----------------

The flags on NOperserv are quite unprecise, lots of stuff assigned to +o.
I'll probably need to sort this out and fix the distribution.

Flags:
s -> staff (< oper)
o -> oper
t -> access to trust modification functions
S -> security team (we have none though)
+S affects
d -> newserv developer
Y -> relay bot
(O -> opered up)
(A -> has account on NOperserv, even if no flags)
(X -> anyone at all)

Command reference (only for modules I think MAY use):
s -> splitlist
o -> channel, lsmod, chanopstat, chanoplist, chanfix, showregs, chansearch,
chanstats, channelhistogram, userhistogram, clonehistogram, chanhistogram,
kill, kick, spewchan, spew, compare, broadcast, obroadcast, mbroadcast,
sbroadcast, cbroadcast, deluser, fakeuser, fakelist, fakekill, nickwatch,
listnumerics, patrol{join,part,list}, regexgline and related, serverlist,
the trust stuff
t -> (empty, what the fuck)
S -> (empty)
d -> status, relink, die, insmod, rmmod, rehash, reload, cfdebug, cfhistogram,
cfsample, cfexpire, cfsave, cfload, chanprofiles, expirecheck, inslua,
rmlua, reloadlua, chanstatssave, lslua, forcegc, dumptree, usercount,
settime
Y -> (empty, we use none of the modules that make use of it)

O -> whois, listusers, hello, splitdel
A -> showcommands, userflags, noticeflags
X -> help

* oper, admin, all devs: +ots
* dev: +otsd
* EB: +otsSd</pre>

Policy:Proposals

2014-01-13T10:24:54Z

Admin:

An index of policy proposals...

* PROP 1 - [[Policy:Proposals/1|Testlink procedure]]
* PROP 2 - [[Policy:Proposals/2|Infrastructure Team - Policy and Operating Prodcedure]]
* PROP 3 - [[Policy:Proposals/3|Operator privilege sets]]

Policy:Proposals/2

2014-01-13T10:19:56Z

Admin: /* Appellate Procedure */

'''Proposal #2 - Infrastructure Team: Policy and Operating Procedure'''

== Overview ==

The Infrastructure ream is subordinate to the DareNET Operations team for the purpose of maintaining a stable, secure, geographically diverse and well structured infrastructure for the organization as a whole. As such, the team is charged with handling and reviewing link applications, maintaining and monitoring all servers linked to the network, and administering the DNS pool. Communication between members of the team is effected by means of a private mailing list. Communications between the team and other relevant entities are effected by the Infrastructure Team Manager.

== Membership ==

* '''Manager:''' Appointed by the Operations team for a one year term, with no restrictions on the number of consecutive terms that may be served. The team manager is charged with ensuring the team is adequately staffed, supervising the overall performance of other team members, maintaining the P10 Server Numerics listing, notification to applicants, and liaising with all relevant parties through established communication channels. Where possible, they may delegate some of these responsibilities to other team members.
* '''Members:''' Appointed by the team manager for an indefinite term. Members are charged with reviewing applications, reviewing existing servers for performance, updating server configurations, maintaining the DNS pool, voting in team Call for Votes (CFVs), etc.

== Policy decisions ==

''(finish me!)''

== Voting procedure ==

''(finish me!)''

== New links procedure ==

''(finish me!)''

== Testlink review procedure ==

''(finish me!)''

== Server delink procedure ==

There are two primary types of delink: Voluntary and Involuntary.

=== Voluntary ===

Servers which voluntarily delink are requested to give the Infrastructure team as much advance notice of the decision as possible to facilitate a smooth transition. Those servers leaving on their own accord, provided they are in good standing, have the option to return at a later date in full link status provided the team is satisfied that any network changes that may have been made (e.g., different uplinks) will not render the server unusable on DareNET, and that the new server is operated by the same administrator. The Infrastructure team MUST be made aware of any such network changes, including traceroutes/pings from the server's new location, BEFORE any attempt to relink the server.

=== Involuntary ===

A server may be involuntarily delinked due to an unexcused absence, or should the Infrastructure and Operations teams decide it's no longer in the best interest of DareNET for the server to remain linked to the network.

Servers that remain in absence from the network for a period of two weeks (fourteen days) will automatically be considered delinked. No CFV for the delinked server will be held in this case, though notification of the delink will be forwarded to the Operations team.

At the discretion of the Infrastructure team, a server may be granted an extended absence provided that the server's admin can give just cause for the absence, and can guarantee its return within a reasonable timeframe. To be granted such an extension, the server admin must make the request PRIOR to the end of the initial two week absentee period.

Servers which are involuntarily delinked may reapply for a link after a six month period following the full application procedure, including the initial testlink period.

For reasons of security or other situations where it's felt the server may have a negative impact on the rest of the network, the team may review that server's link at any time. Such possible circumstances include, but are not solely limited to, server compromised, other services running on the server which were not previously agreed on, uplink connectivity failing to evolve with growth, a complete change of network locations or connectivity.

== Appellate Procedure ==

Should an individual or server admin wish to appeal the decision of the Infrastructure team, they shall immediately notify the Infrastructure Manager of their decision to appeal. The appellate must inform the Manager of their appeal within 48 hours of the decision they're appealing. Failure to do so will result in the assumption that there is no intent to appeal, and the course of action will effected.

The appellate procedure only exists for decisions concerning servers already linked to DareNET, whether in a testlink or permlink status. Decisions regarding applications for new servers may not be appealed at this time. Upon receiving a valid appeal, the Manager shall note the appeal and notify the Operations team. The Operations team will then hold a Call for Discussion (CFD) and a Call for Votes (CFV) on the matter. The decision reached by the Operations team shall be final. The Manager shall notify the appellate of the Operations team's decision.

Should an appeal overturn the decision of the Infrastructure team, the Manager shall liaise with all relevant parties to return the appellate to the status held prior to the decision that caused the appeal. In the case of a testlink server, the server shall be returned to testlink status for a minimum period of 30 days. In the case of a permlink server, the server shall be returned to permlink status.

Note: This procedure only applies to decisions of the Infrastructure team. Appeals to decisions made by the Operations team should be directed to the Executive Board.

Policy:Proposals/2

2014-01-13T10:07:23Z

Admin: /* Involuntary */ change heading type

Policy:Proposals/2

2014-01-13T10:07:08Z

Admin: /* Server delink procedure */

'''Proposal #2 - Infrastructure Team: Policy and Operating Procedure'''

== Overview ==

The Infrastructure ream is subordinate to the DareNET Operations team for the purpose of maintaining a stable, secure, geographically diverse and well structured infrastructure for the organization as a whole. As such, the team is charged with handling and reviewing link applications, maintaining and monitoring all servers linked to the network, and administering the DNS pool. Communication between members of the team is effected by means of a private mailing list. Communications between the team and other relevant entities are effected by the Infrastructure Team Manager.

== Membership ==

* '''Manager:''' Appointed by the Operations team for a one year term, with no restrictions on the number of consecutive terms that may be served. The team manager is charged with ensuring the team is adequately staffed, supervising the overall performance of other team members, maintaining the P10 Server Numerics listing, notification to applicants, and liaising with all relevant parties through established communication channels. Where possible, they may delegate some of these responsibilities to other team members.
* '''Members:''' Appointed by the team manager for an indefinite term. Members are charged with reviewing applications, reviewing existing servers for performance, updating server configurations, maintaining the DNS pool, voting in team Call for Votes (CFVs), etc.

== Policy decisions ==

''(finish me!)''

== Voting procedure ==

''(finish me!)''

== New links procedure ==

''(finish me!)''

== Testlink review procedure ==

''(finish me!)''

== Server delink procedure ==

There are two primary types of delink: Voluntary and Involuntary.

=== Voluntary ===

Servers which voluntarily delink are requested to give the Infrastructure team as much advance notice of the decision as possible to facilitate a smooth transition. Those servers leaving on their own accord, provided they are in good standing, have the option to return at a later date in full link status provided the team is satisfied that any network changes that may have been made (e.g., different uplinks) will not render the server unusable on DareNET, and that the new server is operated by the same administrator. The Infrastructure team MUST be made aware of any such network changes, including traceroutes/pings from the server's new location, BEFORE any attempt to relink the server.

== Involuntary ==

A server may be involuntarily delinked due to an unexcused absence, or should the Infrastructure and Operations teams decide it's no longer in the best interest of DareNET for the server to remain linked to the network.

Servers that remain in absence from the network for a period of two weeks (fourteen days) will automatically be considered delinked. No CFV for the delinked server will be held in this case, though notification of the delink will be forwarded to the Operations team.

At the discretion of the Infrastructure team, a server may be granted an extended absence provided that the server's admin can give just cause for the absence, and can guarantee its return within a reasonable timeframe. To be granted such an extension, the server admin must make the request PRIOR to the end of the initial two week absentee period.

Servers which are involuntarily delinked may reapply for a link after a six month period following the full application procedure, including the initial testlink period.

For reasons of security or other situations where it's felt the server may have a negative impact on the rest of the network, the team may review that server's link at any time. Such possible circumstances include, but are not solely limited to, server compromised, other services running on the server which were not previously agreed on, uplink connectivity failing to evolve with growth, a complete change of network locations or connectivity.

== Appellate Procedure ==

''(finish me!)''

Policy:Proposals/2

2014-01-13T09:45:28Z

Admin: /* Policy decisions */

Policy:Proposals/2

2014-01-13T09:40:13Z

Admin: /* Overview */ grammar

Policy:Proposals/1

2014-01-13T09:38:42Z

Admin: Created page with ''''Proposal #1 - Testlink process''' == Pre-application assistance == You, the prospective server administrator (admin), are encouraged to approach the DareNET Infrastructure t…'

'''Proposal #1 - Testlink process'''

== Pre-application assistance ==

You, the prospective server administrator (admin), are encouraged to approach the DareNET Infrastructure team. They're able to assist you with many aspects of your application, from setting up and securing the server, to application drafting assistance, to assisting with routing and firewall issues. This is not obligatory, as you may send your application directly to infrastructure@; however, the server will pass through a testlink evaluation and there may be a delay if the server does not meet the standard required by DareNET.

== Application submission ==

At this stage, your server should be in a state where it's ready for an immediate link to the IRC network once the ircd has been installed.

This is the first official step in linking a server to DareNET. The process from hereonin is controlled by the Infrastructure team. All inquiries should be addressed in the first instance to infrastructure@. This is also the address to send your completed application request.

Applications are judged, to a large extent, on their content and professionalism, so you're encouraged to take time to fill it out to the best of your ability. You should be truthful and accurate in your responses. Your application will be scrutinised and if found to be intentionally false, you'll be barred from being involved in this network in any official capacity.

== Technical evaluation ==

''(finish me!)''

== Infrastructure team recommendation ==

If your application passes the technical evaluation, it will proceed to a Call for Votes (CFV) along with a recommendation from the Infrastructure team. This recommendation will highlight any potential causes for concern, and whether the team believes the server should proceed to a testlink or not.

== Call for Votes (CFV) ==

The Operations team, which is comprised of DareNET server administrators, is given the opportunity to review the Infrastructure team's recommendation and vote on whether to grant your server a 30 day testlink to the production network.

Current rules require 2/3rds of eligible members to vote ("yes", "no", or "abstain") in order for a quorum to be reached.

== Executive Board decision ==

If less than 2/3rds of eligible Operations team members participate in the vote, then the final decision lies with the Executive Board.

== Testlink ==

If you've been granted a testlink to DareNET, the Infrastructure team will configure the appropriate Connect{} blocks (also known as C/N lines) for your server.

Your server's routing and connectivity will be further evaluated during this period, lasting no less than 30 days.

== Permlink ==

If, after the testlink period has ended, your sever is considered by the Infrastructure team to be adequate, you will be granted a permanent link.

Policy:Proposals/2

2014-01-13T09:37:32Z

Admin: Created page with ''''Proposal #2 - Infrastructure Team: Policy and Operating Procedure''' == Overview == The Infrastructure ream is subordinate to the DareNET Operations team for the purpose of …'

Policy:Proposals

2014-01-13T09:06:25Z

Admin: Created page with 'An index of policy proposals... * PROP 1 - Testlink procedure * PROP 2 - Infrastructure Team - Policy and Operating Prodcedure'

An index of policy proposals...

* PROP 1 - [[Policy:Proposals/1|Testlink procedure]]
* PROP 2 - [[Policy:Proposals/2|Infrastructure Team - Policy and Operating Prodcedure]]

Proposal/Testnet

2014-01-13T08:56:38Z

Admin: Created page with 'Moved to Proposal/Testlink'

Moved to [[Proposal/Testlink]]

Proposal/Testlink

2014-01-13T08:56:07Z

Admin: moved Proposal/Testnet to Proposal/Testlink

== Pre-application assistance ==

You, the prospective server administrator (admin), are encouraged to approach the DareNET Infrastructure team. They're able to assist you with many aspects of your application, from setting up and securing the server, to application drafting assistance, to assisting with routing and firewall issues. This is not obligatory, as you may send your application directly to infrastructure@; however, the server will pass through a testlink evaluation and there may be a delay if the server does not meet the standard required by DareNET.

== Application submission ==

At this stage, your server should be in a state where it's ready for an immediate link to the IRC network once the ircd has been installed.

This is the first official step in linking a server to DareNET. The process from hereonin is controlled by the Infrastructure team. All inquiries should be addressed in the first instance to infrastructure@. This is also the address to send your completed application request.

Applications are judged, to a large extent, on their content and professionalism, so you're encouraged to take time to fill it out to the best of your ability. You should be truthful and accurate in your responses. Your application will be scrutinised and if found to be intentionally false, you'll be barred from being involved in this network in any official capacity.

== Technical evaluation ==

''(finish me!)''

== Infrastructure team recommendation ==

If your application passes the technical evaluation, it will proceed to a Call for Votes (CFV) along with a recommendation from the Infrastructure team. This recommendation will highlight any potential causes for concern, and whether the team believes the server should proceed to a testlink or not.

== Call for Votes (CFV) ==

The Operations team, which is comprised of DareNET server administrators, is given the opportunity to review the Infrastructure team's recommendation and vote on whether to grant your server a 30 day testlink to the production network.

Current rules require 2/3rds of eligible members to vote ("yes", "no", or "abstain") in order for a quorum to be reached.

== Executive Board decision ==

If less than 2/3rds of eligible Operations team members participate in the vote, then the final decision lies with the Executive Board.

== Testlink ==

If you've been granted a testlink to DareNET, the Infrastructure team will configure the appropriate Connect{} blocks (also known as C/N lines) for your server.

Your server's routing and connectivity will be further evaluated during this period, lasting no less than 30 days.

== Permlink ==

If, after the testlink period has ended, your sever is considered by the Infrastructure team to be adequate, you will be granted a permanent link.

Proposal/Testlink

2014-01-13T08:49:28Z

Admin: /* Infrastructure team recommendation */

Proposal/Testlink

2014-01-13T08:45:43Z

Admin: /* Call for Votes (CFV) */

== Pre-application assistance ==

You, the prospective server administrator (admin), are encouraged to approach the DareNET Infrastructure team. They're able to assist you with many aspects of your application, from setting up and securing the server, to application drafting assistance, to assisting with routing and firewall issues. This is not obligatory, as you may send your application directly to infrastructure@; however, the server will pass through a testlink evaluation and there may be a delay if the server does not meet the standard required by DareNET.

== Application submission ==

At this stage, your server should be in a state where it's ready for an immediate link to the IRC network once the ircd has been installed.

This is the first official step in linking a server to DareNET. The process from hereonin is controlled by the Infrastructure team. All inquiries should be addressed in the first instance to infrastructure@. This is also the address to send your completed application request.

Applications are judged, to a large extent, on their content and professionalism, so you're encouraged to take time to fill it out to the best of your ability. You should be truthful and accurate in your responses. Your application will be scrutinised and if found to be intentionally false, you'll be barred from being involved in this network in any official capacity.

== Technical evaluation ==

''(finish me!)''

== Infrastructure team recommendation ==

''(finish me!)''

== Call for Votes (CFV) ==

The Operations team, which is comprised of DareNET server administrators, is given the opportunity to review the Infrastructure team's recommendation and vote on whether to grant your server a 30 day testlink to the production network.

Current rules require 2/3rds of eligible members to vote ("yes", "no", or "abstain") in order for a quorum to be reached.

== Executive Board decision ==

If less than 2/3rds of eligible Operations team members participate in the vote, then the final decision lies with the Executive Board.

== Testlink ==

If you've been granted a testlink to DareNET, the Infrastructure team will configure the appropriate Connect{} blocks (also known as C/N lines) for your server.

Your server's routing and connectivity will be further evaluated during this period, lasting no less than 30 days.

== Permlink ==

If, after the testlink period has ended, your sever is considered by the Infrastructure team to be adequate, you will be granted a permanent link.

Proposal/Testlink

2014-01-13T08:41:16Z

Admin: /* Permlink */

== Pre-application assistance ==

You, the prospective server administrator (admin), are encouraged to approach the DareNET Infrastructure team. They're able to assist you with many aspects of your application, from setting up and securing the server, to application drafting assistance, to assisting with routing and firewall issues. This is not obligatory, as you may send your application directly to infrastructure@; however, the server will pass through a testlink evaluation and there may be a delay if the server does not meet the standard required by DareNET.

== Application submission ==

At this stage, your server should be in a state where it's ready for an immediate link to the IRC network once the ircd has been installed.

This is the first official step in linking a server to DareNET. The process from hereonin is controlled by the Infrastructure team. All inquiries should be addressed in the first instance to infrastructure@. This is also the address to send your completed application request.

Applications are judged, to a large extent, on their content and professionalism, so you're encouraged to take time to fill it out to the best of your ability. You should be truthful and accurate in your responses. Your application will be scrutinised and if found to be intentionally false, you'll be barred from being involved in this network in any official capacity.

== Technical evaluation ==

''(finish me!)''

== Infrastructure team recommendation ==

''(finish me!)''

== Call for Votes (CFV) ==

''(finish me!)''

== Executive Board decision ==

If less than 2/3rds of eligible Operations team members participate in the vote, then the final decision lies with the Executive Board.

== Testlink ==

If you've been granted a testlink to DareNET, the Infrastructure team will configure the appropriate Connect{} blocks (also known as C/N lines) for your server.

Your server's routing and connectivity will be further evaluated during this period, lasting no less than 30 days.

== Permlink ==

If, after the testlink period has ended, your sever is considered by the Infrastructure team to be adequate, you will be granted a permanent link.