DareNET Wiki - New pages [en]

ZNC Fingerprints

Peer — Thu, 08 Oct 2015 04:00:58 GMT

Peer:

/znc AddTrustedServerFingerprint 68:26:FF:E5:B9:51:58:D3:8C:58:73:9F:8C:40:17:5E:95:62:D6:E7:EB:CC:03:71:CF:B3:E5:7C:B7:DB:19:CD

/znc AddTrustedServerFingerprint F7:24:80:AC:44:6F:F1:32:7E:42:00:E3:94:83:F4:C7:33:7A:84:65:74:AF:D0:E4:91:21:BE:8C:16:D7:D9:E5

/znc AddTrustedServerFingerprint 5D:1D:6F:B6:41:53:5A:C3:BD:1F:15:45:47:C6:87:09:9F:7C:45:3A:51:84:07:A8:D5:D6:0E:55:62:1B:36:3C

/znc AddTrustedServerFingerprint 64:5B:2E:1D:B3:3E:1C:E1:E1:0B:58:A1:15:B5:92:79:CD:9E:CB:E5:ED:F2:A4:A4:28:77:A4:21:E9:9C:60:94

/znc AddTrustedServerFingerprint 3D:11:00:97:9D:72:66:AE:76:0A:CE:9C:EA:AF:E7:7C:4A:D0:B3:40:19:50:7A:71:13:5F:D6:B5:DE:09:19:E3

/znc AddTrustedServerFingerprint E9:70:AC:B7:C7:46:A3:34:9E:04:07:58:53:8C:E9:A6:73:78:B7:92:6C:88:E7:5B:61:21:6B:D8:BF:94:62:34

/znc AddTrustedServerFingerprint 83:7B:88:61:75:B1:01:06:D1:56:44:C9:94:13:86:10:89:41:B3:AB:7A:D2:D6:51:00:77:03:68:C5:53:CE:01

/znc AddTrustedServerFingerprint 32:38:72:4B:F4:39:3F:7F:00:F6:D0:56:75:B5:F1:C9:CD:DE:A2:17:FD:4F:61:FF:45:22:C7:29:63:1F:B9:3E

/znc AddTrustedServerFingerprint 6D:D1:07:07:58:33:5F:16:36:F8:9D:5E:80:B5:6C:F1:84:D4:1E:2A:DF:3C:A4:95:1B:1C:48:2C:10:F4:C7:B4

Proposal/Testnet

Admin — Mon, 13 Jan 2014 08:56:38 GMT

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

Moved to [[Proposal/Testlink]]

Proposal/Testnet

Admin — Mon, 13 Jan 2014 08:31:35 GMT

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.

C2

Secretagent — Mon, 15 Oct 2012 03:17:17 GMT

Secretagent: Created page with 'C is our channel services bot here on DareNET. It provides numerous features that help automate channel management, prevent channel takeovers and generally make life easier for b…'

C is our channel services bot here on DareNET. It provides numerous features that help automate channel management, prevent channel takeovers and generally make life easier for both users and staff. This document describes the different commands and features that C provides.

== Usage ==

You can communicate with C via private message, or through server-side aliases, as shown below:

* <code>/msg C <nowiki><text></nowiki></code>
* <code>/msg C@services.darenet.org <nowiki><text></nowiki></code>
* <code>/ChanServ <nowiki><text></nowiki></code>
* <code>/CS <nowiki><text></nowiki></code>

C also supports "in-channel" (also known as "fantasy") commands, which is discussed below.

For the purpose of this document, we will be using the first two methods listed, as some IRC clients do not readily support server-side aliases without additional setup and/or client commands. However, you can choose to use any of the above methods.

==In-channel Commands==

As previously mentioned, C supports what we call ''in-channel'' commands. You can use the ''in-channel'' method for just about any of the commands C recognizes. All ''in-channel'' commands directed towards C begin with a period. If a command is given in a channel, and the channel parameter is not given, C will use the name of the channel that the command was used in.

''In-channel'' commands may only be used in registered channels; however, C does not have to reside in the channel for them to work.

'''Example:'''

To illustrate what we're talking about, let's say we have a channel named ''#chat'' and we would like to grant the user ''JoeClient'' op status. Using the ''in-channel'' method, we could achieve this by simply typing the following in ''#chat'':

<code>.OP JoeClient</code>

==User Management Commands==
* [[C/access|ACCESS]]
** Check a user's access level in a channel.
* [[C/addcoowner|ADDCOOWNER]]
** Grant a user Co-owner access.

C/wlist

Nitemare — Thu, 11 Oct 2012 06:31:59 GMT

Nitemare: Created page with '{{Related commands|ADDOWNER<br />MDELOWNER<br />USERS}}<span class="cmdsyn">WLIST <#channel> <span class="cmdsynopt">[mask]</span></spa…'

{{Related commands|[[C/addowner|ADDOWNER]]<br />[[C/mdelowner|MDELOWNER]]<br />[[C/users|USERS]]}}<span class="cmdsyn">WLIST <#channel> <span class="cmdsynopt">[mask]</span></span>

Lists all users of level OWNER on a channel's user list.

An optional mask may be supplied to limit showing only those OWNERs that match the mask.

===Examples===
{| class="srvcscmd" width="90%" style="font-size: 90%;"
| /msg C WLIST #chat
| Show all users with an access level of OWNER on #chat.
|-
| /msg C WLIST *foo*
| Show only those users with an access level of OWNER in #chat who have "foo" in their account name.
|-
|}

{{GoBack}}

C/adduser

Nitemare — Thu, 11 Oct 2012 06:10:39 GMT

Nitemare: Created page with '{{Related commands|DELUSER<br />USERS}}<div class="cmdsyn">ADDUSER <#channel> <nickname|*account> <level> <span class="cmdsynopt">[duration]</span></div…'

{{Related commands|[[C/deluser|DELUSER]]<br />[[C/users|USERS]]}}<div class="cmdsyn">ADDUSER <#channel> <nickname|*account> <level> <span class="cmdsynopt">[duration]</span></div>

Adds a user to the channel's user list with the specified access level.

Where <code><level></code> may be one of GRUNT, OP, MANAGER, COOWNER or OWNER. Or, a numerical level may be specified instead, between 1 and 500. Only network staff may add users with level 500 (owner).

An optional duration may be provided, which will cause the user to be automatically removed from the channel's user list once the duration has passed (expired). See [[C/durations|HELP DURATIONS]] for information on how to correctly specify a duration.

Keep in mind that you may only grant a user an access level that less than your own.

===Examples===
{| class="srvcscmd" width="90%" style="font-size: 90%;"
| /msg C ADDUSER #chat Joe COOWNER
| Adds the user who's nickname is Joe to #chat's user list with an access level of CO-OWNER.
|-
| /msg C ADDUSER #chat *joe OP
| Adds the user who's account name is joe to #chat's user list with an access level of OP.
|-
| /msg C ADDUSER #chat foo 300 2d
| Adds the user who's nickname is foo to #chat's user list with an access level of 300, which will expire in 2 days.
|}

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

C/clvl

Nitemare — Thu, 11 Oct 2012 06:03:51 GMT

Nitemare: Created page with '{{Related commands|ACCESS<br />GIVEOWNERSHIP}}<div class="cmdsyn">CLVL <#channel> <nickname|*account> <level> <span class="cmdsynopt">[duration]<…'

{{Related commands|[[C/access|ACCESS]]<br />[[C/giveownership|GIVEOWNERSHIP]]}}<div class="cmdsyn">CLVL <#channel> <nickname|*account> <level> <span class="cmdsynopt">[duration]</span></div>

Modifies a user's channel access level.

An optional duration can be specified, in which case once the duration has passed (expired) the user will be automatically reverted back to their previous access level.

Keep in mind that cannot give users access great then or equal to your own.

==Examples==
{| class="srvcscmd" width="90%" style="font-size: 90%;"
| /msg C CLVL #chat Joe COOWNER
| Changes the user's, who's nickname is Joe, access level in #chat to CO-OWNER.
|-
| /msg C CLVL #chat *joe OP
| Changes the user's, who's account name is joe, access level #chat to OP.
|-
| /msg C ADDUSER #chat foo 300 2d
| Changes the user's, who's nickname is foo, access level in to #chat to 300, which will expire in 2 days.
|}

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>