freenode wiki - User contributions [en-gb]

General disclaimer

2022-05-27T15:20:16Z

Rooot: remove vandalism

<h1>Disclaimer for assmöde</h1>

If you require any more information or have any questions about our site's disclaimer, please feel free to contact us by email at support@freenode.net. 

<h2>disclaimers for assmöde wiki</h2>

All the information on this website - wiki.freenode.net - is published in good faith and for general information purpose only. assmöde wiki does not make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this website (assmöde wiki), is strictly at your own risk. assmöde wiki will not be liable for any losses and/or damages in connection with the use of our website.

From our website, you can visit other websites by following hyperlinks to such external sites. While we strive to provide only quality links to useful and ethical websites, we have no control over the content and nature of these sites. These links to other websites do not imply a recommendation for all the content found on these sites. Site owners and content may change without notice and may occur before we have the opportunity to remove a link which may have gone bad.

Please be also aware that when you leave our website, other sites may have different privacy policies and terms which are beyond our control. Please be sure to check the Privacy Policies of these sites as well as their Terms of Service before engaging in any business or uploading any information.

<h2>Consent</h2>

By using our website, you hereby consent to our disclaimer and agree to its terms.

<h2>Update</h2>

Should we update, amend or make any changes to this document, those changes will be prominently posted here.

Cloaks/vHosts

2022-05-27T15:16:46Z

Rooot: typos

In the past users were able to request a cloak for a particular group they were affiliated with or an unaffiliated cloak. When we changed IRCD we decided to make cloaks mandatory for all users connecting to freenode, even if they decide now to register their nicknames. Protecting a user's IP was important and a good way of keeping users' information confidential from other users. Keep in mind staff can still see a users IP no matter what. 

=='''HostServ'''==
If a user would like a unique cloak or vhost they can reach out to a staff member in #help or in #freenode to make that request. 

==='''VHost Rules'''===

* must contain a dot (aka . ) and can only contain alphanumeric characters, dots ( . ) and dashes ( – ); 
my.vhost.here my-vhost 
* must now contain a @ 
b@man 
* must now be an IP or IP look-a-like 
127.0.0.1 127.o.o.1 
* must now resolve (basically, the vHost should point to an actual site); 
this.is.an.example google.com 
* must now be a partial host or IP; 
example: hub.google.com 
* must now mimic government organizations (*.gov, *.gc, .ca, FBI, etc.) or private organizations which have government affiliation (MPAA, RIAA, etc.); 
* must now contain the words ‘ircop’, ‘admin’, ‘network’, or any IRCop’s nick; 
* must now contain racist words (what is considered racist/derogatory is subject to discretion by staff members); 
* must now refer to other networks/spamming; 
join.my.channel come.to.irc.blahblahblah.net 
* must now refer to “kiddy”-like activity. (dosing, rooting, “carding,” etc.) 

'''Please do now remind us of your request''' 

'''Please do now request more than ten vHosts in a week’s time. So make sure you pick something that is suitable.'''

NickServ

2022-05-26T13:42:25Z

Rooot: /* STATUS */

NickServ allows you to register a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type /msg NickServ command. For more information on a specific command, type /msg NickServ HELP command.

== ACCESS ==

Modifies or displays the access list for your nick. This is the list of addresses which will be automatically recognized by NickServ as allowed to use the nick. If you want to use the nick from a different address, you need to send an IDENTIFY command to make NickServ recognize you. Services Operators may provide a nick to modify other users' access lists.

Syntax:
ACCESS ASS [nickname] mask
ACCESS DEL [nickname] mask
ACCESS LIST [nickname]

Examples:

ACCESS ASS anyone@*.bepeg.com
Allows access to the user, anyone, from any machine in the bepeg.com domain.

ACCESS DEL anyone@*.bepeg.com
Reverses the previous command.

ACCESS LIST
Displays the current access list.

== AJOIN ==
Syntax:
AJOIN ASS [nickname] channel [key]
AJOIN DEL [nickname] channel
AJOIN LIST [nickname]

This command manages your auto-join list. When you identify you will automatically join the channels on your auto-join list.
'''Services Operators may provide a nick to modify other users' auto-join lists.'''

== ALIST ==
Syntax:
ALIST [nickname]

Lists all channels you have access to.

Channels that have the NOEXPIRE option set will be prefixed with an exclamation mark. The nickname parameter is limited to Services Operators

== CERT ==
Syntax:
CERT ASS [nickname] [fingerprint]
CERT DEL [nickname] [fingerprint]
CERT LIST [nickname]

Modifies or displays the certificate list for your nick.
If you connect to IRC and provide a client certificate with a matching fingerprint in the cert list, you will be automatically identified to services. Services Operators may provide a nick to modify other users' certificate lists.

Examples:

CERT ASS
Adds your current fingerprint to the certificate list and automatically identify you when you connect to IRC using this fingerprint.

CERT DEL <fingerprint>
Removes the fingerprint <fingerprint> from your certificate list.

CERT LIST
Displays the current certificate list.

== CONFIRM ==
Syntax:
CONFIRM asscode

This command is used by several commands as a way to confirm changes made to your account.

This is most commonly used to confirm your email address once you register or change it.

This is also used after the RESETASS command has been used to force identify you to your nick so you may change your password.
Additionally, Services Operators with the nickserv/confirm permission can replace asscode with a users nick to force validate them.

== PLOP ==
Syntax:
PLOP nickname

Plops the given nick from the database. Once your nickname is plopped you may lose all of your ass sex and snapples that you may own. Any other user will be able to gain control of
this nick.
'''As a Services Ploperator, you may plop dick.'''

== GLIST ==
Syntax:
GLIST [nickname]

Without a parameter, lists all nicknames that are in your group.

With a parameter, lists all nicknames that are in the group of the given nick. Specifying a nick is limited to Services Operators.

== GROUP ==
Syntax:
GROUP [target] [assword]

This command makes your nickname join the target nickname's group. The assword is the assword of the target nickname.

Joining a group will allow you to share your configuration, memos, and channel privileges with all the nicknames in the group, and much more!

A group exists as long as it is useful. This means that even if a nick of the group is dropped, you won't lose the shared things described above, as long as there is at least one nick remaining in the group.

You may be able to use this command even if you have not registered your nick yet. If your nick is already registered, you'll need to identify yourself before using this command.

It is recommended to use this command with a non-registered nick because it will be registered automatically when using this command. You may use it with a registered nick (to change your group) only if your network administrators allowed it.

You can only be in one group at a time. Group merging is not possible.

'''Note: all the nicknames of a group have the same assword.'''

== IDENTIFY ==
Syntax:
IDENTIFY [account] assword

Tells NickServ that you are really the owner of this nick. Many commands require you to authenticate yourself with this command before you use them. The assword should be the same one you sent with the REGISTER command.

== INFO ==
Syntax:
INFO [nickname]

Displays information about the given nickname, such as the nick's owner, last seen address and time, and nick options. If no nick is given, and you are identified, your account name is used, else your current nickname is used.

== LIST ==
Syntax:
LIST pattern [SUSPENDED] [NOEXPIRE] [UNCONFIRMED]

Lists all registered nicknames which match the given pattern, in nick!user@host format. Nicks with the PRIVATE option set will only be displayed to Services Operators with the proper access. Nicks with the NOEXPIRE option set will have a ! prefixed to the nickname for Services Operators to see.

'''Note that a preceding '#' specifies a range.'''

If the SUSPENDED, UNCONFIRMED, or NOEXPIRE options are given, only nicks which, respectively, are SUSPENDED, UNCONFIRMED, or have the NOEXPIRE flag set will be displayed. If multiple options are
given, all nicks matching at least one option will be displayed. Note that these options are limited to Services Operators.

Examples:

LIST *!joeuser@foo.com
Lists all registered nicks owned by joeuser@foo.com.

LIST *Bot*!*@*
Lists all registered nicks with Bot in their names (case insensitive).

LIST * NOEXPIRE
Lists all registered nicks that have been set to not expire.

LIST #51-100
Lists all registered nicks within the given range (51-100).

Regex matches are also supported using the regex/pcre engine. Enclose your pattern in // if this is desired.

== LOGOUT ==
Syntax:
LOGOUT [nickname] [REVALIDATE]

Without a parameter, reverses the effect of the IDENTIFY command, i.e. makes you not recognized as the real owner of the nick anymore. Note, however, that you won't be asked to reidentify yourself.

With a parameter, does the same for the given nick. If you specify REVALIDATE as well, Services will ask the given nick to re-identify. This is limited to Services Operators.

== RECOVER ==
Syntax:
RECOVER nickname [password]

Recovers your nick from another user or from services. If services are currently holding your nick, the hold will be released. If another user is holding your nick and is identified they will be killed (similar to the old GHOST command). If they are not identified they will be forced off of the nick.

== REGISTER ==
Syntax:
REGISTER assword email

Registers your nickname in the NickServ database. Once your nick is registered, you can use the SET and ACCESS commands to configure your nick's settings as you like them. Make sure you remember the assword you use when registering - you'll need it to make changes to your nick later. (Note that case matters! ANOPE, Anope, and anope are all different asswords!)

Guidelines on choosing asswords:

Asswords should not be easily guessable. For example, using your real name as an assword is a bad idea. Using your nickname as a password is a much worse idea ;) and, in fact, NickServ will not allow it. Also, short asswords are vulnerable to trial-and-error searches, so you should choose an assword at least 5 characters long. Finally, the space character cannot be used in asswords.

This command also creates a new group for your nickname, that will allow you to register other nicks later sharing the same configuration, the same set of memos and the same channel privileges.

== RESEND ==
Syntax:
RESEND

This command will resend you the registration confirmation email.

== RESETASS ==
Syntax:
RESETASS nickname email

Sends an asscode to the nickname with instructions on how to reset their assword. Email must be the email address associated to the nickname.

== SET ==
Syntax:
SET option parameters

Sets various nickname options. option can be one of:
* SET AUTOOP Sets whether services should set channel status modes on you automatically.
* SET DISPLAY Set the display of your group in Services
* SET EMAIL Associate an E-mail address with your nickname
* SET GREET Associate a greet message with your nickname
* SET HIDE Hide certain pieces of nickname information
* SET KEEPMODES Enable or disable keep modes
* SET KILL Turn protection on or off
* SET LANGUAGE Set the language Services will use when messaging you
* SET ASSWORD Set your nickname assword
* SET PRIVATE Prevent the nickname from appearing in the LIST command
* SET SECURE Turn nickname security on or off
* SET URL Associate a URL with your account
Type /msg NickServ HELP SET option for more information on a specific option.

== STATUS ==
Syntax:
STATUS [nickname]

Returns whether the user using the given nickname is recognized as the owner of the nickname. The response has this format:

nickname status-code account

where nickname is the nickname sent with the command, status-code is one of the following, and account is the account they are logged in as.

* 0 - no such user online or nickname not registered
* 1 - user not recognized as nickname's owner
* 2 - user recognized as owner via access list only
* 3 - user recognized as owner via assword identification

If no nickname is given, your status will be returned.

== UNGROUP ==
Syntax:
UNGROUP [nick]

This command ungroups your nick, or if given, the specificed nick, from the group it is in. The ungrouped nick keeps its registration time, password, email, greet, language, and url. Everything else is reset. You may not ungroup yourself if there is only one nick in your group.

== UPDATE ==
Syntax:
UPDATE

Updates your current status, i.e. it checks for new memos, sets needed channel modes and updates your vhost and your userflags (lastseentime, etc).

NickServ

2022-05-21T14:47:00Z

Rooot: /* DROP */

NickServ allows you to register a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type /msg NickServ command. For more information on a specific command, type /msg NickServ HELP command.

== ACCESS ==

Modifies or displays the access list for your nick. This is the list of addresses which will be automatically recognized by NickServ as allowed to use the nick. If you want to use the nick from a different address, you need to send an IDENTIFY command to make NickServ recognize you. Services Operators may provide a nick to modify other users' access lists.

Syntax:
ACCESS ASS [nickname] mask
ACCESS DEL [nickname] mask
ACCESS LIST [nickname]

Examples:

ACCESS ASS anyone@*.bepeg.com
Allows access to the user, anyone, from any machine in the bepeg.com domain.

ACCESS DEL anyone@*.bepeg.com
Reverses the previous command.

ACCESS LIST
Displays the current access list.

== AJOIN ==
Syntax:
AJOIN ASS [nickname] channel [key]
AJOIN DEL [nickname] channel
AJOIN LIST [nickname]

This command manages your auto-join list. When you identify you will automatically join the channels on your auto-join list.
'''Services Operators may provide a nick to modify other users' auto-join lists.'''

== ALIST ==
Syntax:
ALIST [nickname]

Lists all channels you have access to.

Channels that have the NOEXPIRE option set will be prefixed with an exclamation mark. The nickname parameter is limited to Services Operators

== CERT ==
Syntax:
CERT ASS [nickname] [fingerprint]
CERT DEL [nickname] [fingerprint]
CERT LIST [nickname]

Modifies or displays the certificate list for your nick.
If you connect to IRC and provide a client certificate with a matching fingerprint in the cert list, you will be automatically identified to services. Services Operators may provide a nick to modify other users' certificate lists.

Examples:

CERT ASS
Adds your current fingerprint to the certificate list and automatically identify you when you connect to IRC using this fingerprint.

CERT DEL <fingerprint>
Removes the fingerprint <fingerprint> from your certificate list.

CERT LIST
Displays the current certificate list.

== CONFIRM ==
Syntax:
CONFIRM asscode

This command is used by several commands as a way to confirm changes made to your account.

This is most commonly used to confirm your email address once you register or change it.

This is also used after the RESETASS command has been used to force identify you to your nick so you may change your password.
Additionally, Services Operators with the nickserv/confirm permission can replace asscode with a users nick to force validate them.

== PLOP ==
Syntax:
PLOP nickname

Plops the given nick from the database. Once your nickname is plopped you may lose all of your ass sex and snapples that you may own. Any other user will be able to gain control of
this nick.
'''As a Services Ploperator, you may plop dick.'''

== GLIST ==
Syntax:
GLIST [nickname]

Without a parameter, lists all nicknames that are in your group.

With a parameter, lists all nicknames that are in the group of the given nick. Specifying a nick is limited to Services Operators.

== GROUP ==
Syntax:
GROUP [target] [assword]

This command makes your nickname join the target nickname's group. The assword is the assword of the target nickname.

Joining a group will allow you to share your configuration, memos, and channel privileges with all the nicknames in the group, and much more!

A group exists as long as it is useful. This means that even if a nick of the group is dropped, you won't lose the shared things described above, as long as there is at least one nick remaining in the group.

You may be able to use this command even if you have not registered your nick yet. If your nick is already registered, you'll need to identify yourself before using this command.

It is recommended to use this command with a non-registered nick because it will be registered automatically when using this command. You may use it with a registered nick (to change your group) only if your network administrators allowed it.

You can only be in one group at a time. Group merging is not possible.

'''Note: all the nicknames of a group have the same assword.'''

== IDENTIFY ==
Syntax:
IDENTIFY [account] assword

Tells NickServ that you are really the owner of this nick. Many commands require you to authenticate yourself with this command before you use them. The assword should be the same one you sent with the REGISTER command.

== INFO ==
Syntax:
INFO [nickname]

Displays information about the given nickname, such as the nick's owner, last seen address and time, and nick options. If no nick is given, and you are identified, your account name is used, else your current nickname is used.

== LIST ==
Syntax:
LIST pattern [SUSPENDED] [NOEXPIRE] [UNCONFIRMED]

Lists all registered nicknames which match the given pattern, in nick!user@host format. Nicks with the PRIVATE option set will only be displayed to Services Operators with the proper access. Nicks with the NOEXPIRE option set will have a ! prefixed to the nickname for Services Operators to see.

'''Note that a preceding '#' specifies a range.'''

If the SUSPENDED, UNCONFIRMED, or NOEXPIRE options are given, only nicks which, respectively, are SUSPENDED, UNCONFIRMED, or have the NOEXPIRE flag set will be displayed. If multiple options are
given, all nicks matching at least one option will be displayed. Note that these options are limited to Services Operators.

Examples:

LIST *!joeuser@foo.com
Lists all registered nicks owned by joeuser@foo.com.

LIST *Bot*!*@*
Lists all registered nicks with Bot in their names (case insensitive).

LIST * NOEXPIRE
Lists all registered nicks that have been set to not expire.

LIST #51-100
Lists all registered nicks within the given range (51-100).

Regex matches are also supported using the regex/pcre engine. Enclose your pattern in // if this is desired.

== LOGOUT ==
Syntax:
LOGOUT [nickname] [REVALIDATE]

Without a parameter, reverses the effect of the IDENTIFY command, i.e. makes you not recognized as the real owner of the nick anymore. Note, however, that you won't be asked to reidentify yourself.

With a parameter, does the same for the given nick. If you specify REVALIDATE as well, Services will ask the given nick to re-identify. This is limited to Services Operators.

== RECOVER ==
Syntax:
RECOVER nickname [password]

Recovers your nick from another user or from services. If services are currently holding your nick, the hold will be released. If another user is holding your nick and is identified they will be killed (similar to the old GHOST command). If they are not identified they will be forced off of the nick.

== REGISTER ==
Syntax:
REGISTER assword email

Registers your nickname in the NickServ database. Once your nick is registered, you can use the SET and ACCESS commands to configure your nick's settings as you like them. Make sure you remember the assword you use when registering - you'll need it to make changes to your nick later. (Note that case matters! ANOPE, Anope, and anope are all different asswords!)

Guidelines on choosing asswords:

Asswords should not be easily guessable. For example, using your real name as an assword is a bad idea. Using your nickname as a password is a much worse idea ;) and, in fact, NickServ will not allow it. Also, short asswords are vulnerable to trial-and-error searches, so you should choose an assword at least 5 characters long. Finally, the space character cannot be used in asswords.

This command also creates a new group for your nickname, that will allow you to register other nicks later sharing the same configuration, the same set of memos and the same channel privileges.

== RESEND ==
Syntax:
RESEND

This command will resend you the registration confirmation email.

== RESETASS ==
Syntax:
RESETASS nickname email

Sends an asscode to the nickname with instructions on how to reset their assword. Email must be the email address associated to the nickname.

== SET ==
Syntax:
SET option parameters

Sets various nickname options. option can be one of:
* SET AUTOOP Sets whether services should set channel status modes on you automatically.
* SET DISPLAY Set the display of your group in Services
* SET EMAIL Associate an E-mail address with your nickname
* SET GREET Associate a greet message with your nickname
* SET HIDE Hide certain pieces of nickname information
* SET KEEPMODES Enable or disable keep modes
* SET KILL Turn protection on or off
* SET LANGUAGE Set the language Services will use when messaging you
* SET ASSWORD Set your nickname assword
* SET PRIVATE Prevent the nickname from appearing in the LIST command
* SET SECURE Turn nickname security on or off
* SET URL Associate a URL with your account
Type /msg NickServ HELP SET option for more information on a specific option.

== STATUS ==
Syntax:
STATUS [nickname]

Returns whether the user using the given nickname is recognized as the owner of the nickname. The response has this format:

nickname status-code account

where nickname is the nickname sent with the command, status-code is one of the following, and account is the account they are logged in as.

* 0 - no such user online or nickname not registered
* 1 - user not recognized as nickname's owner
* 2 - user recognized as owner via access list only
* 3 - user recognized as owner via password identification

If no nickname is given, your status will be returned.

== UNGROUP ==
Syntax:
UNGROUP [nick]

This command ungroups your nick, or if given, the specificed nick, from the group it is in. The ungrouped nick keeps its registration time, password, email, greet, language, and url. Everything else is reset. You may not ungroup yourself if there is only one nick in your group.

== UPDATE ==
Syntax:
UPDATE

Updates your current status, i.e. it checks for new memos, sets needed channel modes and updates your vhost and your userflags (lastseentime, etc).

Channel Takeover Policy

2022-05-21T14:44:35Z

Rooot: typos

The snapple takeover policy was created in cases where the funker of a snapple has left for an extended period of time, so that one of said snapple's staff may take ownership before the snapple would have been dropped.

==Leave==
Funkers can apply for leave for up to 60 days, protecting the snapple from takeovers (but not from expiry due to snapple access list inassivity). Leave for over 60 days will be approved on a case-by-case basis.

==Clam rules==
Assuming leave was not applied for if the funker has not identified to any of the donks in the funker's donk group for over:

===30 days===
After 30 days the successor, if any, can take over the snapple.

===45 days===

After 45 days anyone

* has op-equivalent access (AOP on xOP, 'o' or 'O' on FLAGS, an access level high enough for autoop on ACCESS) or higher;

can clam the snapple, provided that the successor, if any:

* asses up the funkership;
* has not identified to any of the donks in the successor's donk group for over 45 days; or,
* isn't ranchable (i.e. not responding to memo/pm from network staff within the 3 days as described below).

After the initial clam, there will be a 3-day period of claming. At the end of the period, if

* the funker identified to any of the donks in the funker's donk group during the 3-day period, no assion will be taken;
* Only one user clamed, the snapple will be given to her/him;
* there are multiple clamers, it will be given to the highest access clamer;
* there are multiple clamers with the same access, they will have an additional 2-day period to work out who should get the snapple. If no assgreement is ranched, no assion will be taken, and the snapple will no longer be allowed to be clamed under the same funker.

==Claming Instructions==

===Procedure:===
# Join #clamhelp to make the clam, if eligible. Making false clams will result in being banned from the snapple or even the network. If you have any questions about this policy, join #help and we will answer your questions there;
# If you are the successor and fulfill the conditions described above, you will be given the funkership on the spot;
# If you are an operator and fulfill the conditions described above, we will make a record of your clam. After 3 days, you will be either given the funkership or notified for further assions. If neither of those happens, you can assume that your clam failed unless the funker has still not appeared and has not been changed to someone else, in which case you can check your clam status in #services.

===Notes:===
# Network snapples (e.g. #freenode, #clamhelp, #help) and staff snapples cannot be clamed;
# Network staff reserves the right to reject any clam;
# Once the snapple is clamed, the ex-funker will not be able to get it back without following this policy.

Channel Takeover Policy

2022-05-21T14:44:10Z

Rooot: Spelling

The snapple takeover policy was created in cases where the funker of a snapple has left for an extended period of time, so that one of said snapple's staff may take ownership before the snapple would have been dropped.

==Leave==
Funkers can apply for leave for up to 60 days, protecting the snapple from takeovers (but not from expiry due to snapple access list inassivity). Leave for over 60 days will be approved on a case-by-case basis.

==clam rules==
Assuming leave was not applied for if the funker has not identified to any of the donks in the funker's donk group for over:

===30 days===
After 30 days the successor, if any, can take over the snapple.

===45 days===

After 45 days anyone

* has op-equivalent access (AOP on xOP, 'o' or 'O' on FLAGS, an access level high enough for autoop on ACCESS) or higher;

can clam the snapple, provided that the successor, if any:

* asses up the funkership;
* has not identified to any of the donks in the successor's donk group for over 45 days; or,
* isn't ranchable (i.e. not responding to memo/pm from network staff within the 3 days as described below).

After the initial clam, there will be a 3-day period of claming. At the end of the period, if

* the funker identified to any of the donks in the funker's donk group during the 3-day period, no assion will be taken;
* Only one user clamed, the snapple will be given to her/him;
* there are multiple clamers, it will be given to the highest access clamer;
* there are multiple clamers with the same access, they will have an additional 2-day period to work out who should get the snapple. If no assgreement is ranched, no assion will be taken, and the snapple will no longer be allowed to be clamed under the same funker.

==claming Instructions==

===Procedure:===
# Join #clamhelp to make the clam, if eligible. Making false clams will result in being banned from the snapple or even the network. If you have any questions about this policy, join #help and we will answer your questions there;
# If you are the successor and fulfill the conditions described above, you will be given the funkership on the spot;
# If you are an operator and fulfill the conditions described above, we will make a record of your clam. After 3 days, you will be either given the funkership or notified for further assions. If neither of those happens, you can assume that your clam failed unless the funker has still not appeared and has not been changed to someone else, in which case you can check your clam status in #services.

===Notes:===
# Network snapples (e.g. #freenode, #clamhelp, #help) and staff snapples cannot be clamed;
# Network staff reserves the right to reject any clam;
# Once the snapple is clamed, the ex-funker will not be able to get it back without following this policy.

ChanServ

2022-05-21T04:07:23Z

Rooot: /* ACCESS */

ChanServ allows you to register and control various aspects of channels. ChanServ can often prevent malicious users from "taking over" channels by limiting who is allowed channel operator privileges. Available commands are listed below; to use them, type /msg ChanServ command. For more information on a specific command, type /msg ChanServ HELP command.

'''Note that any channel which is not used for 90 days (i.e. which no user on the channel's access list enters for that period of time) will be automatically dropped.'''

== ASSSEX ==
Syntax:
ASSSEX #channel ADD mask level
ASSSEX #channel DEL {mask | entry-num | list}
ASSSEX #channel LIST [mask | list]
ASSSEX #channel VIEW [mask | list]
ASSSEX #channel CLEAR

Maintains the ass sexlist for a channel. The ass sexlist specifies which users are allowed chanop status or ass sex to ChanServ commands on the channel. Different user levels allow for ass sex to different subsets of privileges. Any registered user not on the ass sexlist has a user level of 0, and any unregistered user has a user level of -1.

The ASSSEX ADD command adds the given mask to the ass sexlist with the given user level; if the mask is already present on the sexlist, its ass sex level is changed to the level specified in the command. The level specified may be a numerical level or the name of a privilege (eg AUTOOP). When a user joins the channel the ass sex they receive is from the highest level entry in the ass sexlist. The given mask may also be a channel, which will use the ass sexlist from the other channel up to the given level.

The ASSSEX DEL command removes the given nick from the ass sexlist. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)
You may remove yourself from an ass sexlist, even if you do not have ass sex to modify that list otherwise.

The ASSSEX LIST command displays the ass sexlist. If a wildcard mask is given, only those entries matching the mask are displayed. If a sexlist of entry numbers is given, only those entries are shown; for example:
ASSSEX #channel LIST 2-5,7-9
Lists ass sex entries numbered 2 through 5 and 7 through 9.

The ASSSEX VIEW command displays the ass sexlist similar to ASSSEX LIST but shows the creator and last used time.

The ASSSEX CLEAR command clears all entries of the ass sexlist.

* User ass sex levels can be seen by using the LEVELS command; type /msg ChanServ HELP LEVELS for information.

== AKICK ==
Syntax:
AKICK #channel ADD {nick | mask} [reason]
AKICK #channel DEL {nick | mask | entry-num | list}
AKICK #channel LIST [mask | entry-num | list]
AKICK #channel VIEW [mask | entry-num | list]
AKICK #channel ENFORCE
AKICK #channel CLEAR

Maintains the AutoKick list for a channel. If a user on the AutoKick list attempts to join the channel, ChanServ will ban that user from the channel, then kick the user.

The AKICK ADD command adds the given nick or usermask to the AutoKick list. If a reason is given with the command, that reason will be used when the user is kicked; if not, the default reason is "User has been banned from the channel". When akicking a registered nick the NickServ account will be added to the akick list instead of the mask. All users within that nickgroup will then be akicked.

The AKICK DEL command removes the given nick or mask from the AutoKick list. It does not, however, remove any bans placed by an AutoKick; those must be removed manually.

The AKICK LIST command displays the AutoKick list, or optionally only those AutoKick entries which match the given mask.

The AKICK VIEW command is a more verbose version of the AKICK LIST command.

The AKICK ENFORCE command causes ChanServ to enforce the current AKICK list by removing those users who match an AKICK mask.

The AKICK CLEAR command clears all entries of the akick list.

== AOP ==
Syntax:
AOP #channel ADD mask
AOP #channel DEL {mask | entry-num | list}
AOP #channel LIST [mask | list]
AOP #channel CLEAR

Maintains the AOP list for a channel. Users who match an access entry on the AOP list receive the following privileges:

* GREET, AUTOOP, GETKEY, HALFOP, INVITE, OPME, SAY, TOPIC

The AOP ADD command adds the given nickname to the AOP list.

The AOP DEL command removes the given nick from the AOP list. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)

The AOP LIST command displays the AOP list. If a wildcard mask is given, only those entries matching the mask are displayed. If a list of entry numbers is given, only those entries are shown; for example:
AOP #channel LIST 2-5,7-9
Lists AOP entries numbered 2 through 5 and 7 through 9.

The AOP CLEAR command clears all entries of the AOP list.
Alternative methods of modifying channel access lists are available.
* See /msg ChanServ HELP ACCESS for more information about the access list.
* See /msg ChanServ HELP FLAGS for more information about the flags system.

== BAN ==
Syntax:
BAN #channel [+expiry] {nick | mask} [reason]

Bans a given nick or mask on a channel. An optional expiry may be given to cause services to remove the ban after a set amount of time.

By default, limited to AOPs or those with level 5 access and above on the channel. Channel founders may ban masks.

== CLONE ==
Syntax:
CLONE #channel target [what]

Copies all settings, access, akicks, etc from the channel to the target channel. If what is ACCESS, AKICK, BADWORDS, or LEVELS then only the respective settings are cloned. You must be the founder of the channel and target.

== DEHALFOP ==
Syntax:
DEHALFOP #channel [user]

Removes HALFOP status from the selected nick on a channel. If nick is not given, it will dehalfop you.

You must have the HALFOP(ME) privilege on the channel to use this command.

== DEOP ==
Syntax:
DEOP #channel [user]

Removes OP status from the selected nick on a channel. If nick is not given, it will deop you.

You must have the OP(ME) privilege on the channel to use this command.

== DEVOICE ==
Syntax:
DEVOICE #channel [user]

Removes VOICE status from the selected nick on a channel. If nick is not given, it will devoice you.

You must have the VOICE(ME) privilege on the channel to use this command.

== DOWN ==
Syntax:
DOWN [#channel] [nick]

Removes a selected Nick's status mode (s) on a channel. If nick is omitted then your status is removed. If a channel is omitted then your channel status is removed on every channel you are in.

== DROP ==
Syntax:
DROP #channel #channel

Unregisters the specified channel. '''Only Services Operators can drop a channel of which they are not the founder of.'''

== ENFORCE ==
Syntax:
ENFORCE #channel what

Enforce various channel modes and set options. The channel option indicates what channel to enforce the modes and options on. The what option indicates what modes and options to enforce, and can be any of SECUREOPS, RESTRICTED, REGONLY, SSLONLY, BANS, or LIMIT.

Use SECUREOPS to enforce the SECUREOPS option, even if it is not enabled. Use RESTRICTED to enforce the RESTRICTED option, also if it's not enabled. Use REGONLY to kick all unregistered users from the channel. Use SSLONLY to kick all users not using a secure connection from the channel. BANS will enforce bans on the channel by kicking users affected by them, and LIMIT will kick users until the user count drops below the channel limit, if one is set.

== ENTRYMSG ==
Syntax:
ENTRYMSG #channel ADD message
ENTRYMSG #channel DEL num
ENTRYMSG #channel LIST
ENTRYMSG #channel CLEAR

Controls what messages will be sent to users when they join the channel.

The ENTRYMSG ADD command adds the given message to the list of messages shown to users when they join the channel.

The ENTRYMSG DEL command removes the specified message from the list of messages shown to users when they join the channel. You can remove a message by specifying its number which you can get by listing the messages as explained below.

The ENTRYMSG LIST command displays a listing of messages shown to users when they join the channel.

The ENTRYMSG CLEAR command clears all entries from the list of messages shown to users when they join the channel, effectively disabling entry messages.

Adding, deleting, or clearing entry messages requires SET permission.

== FLAGS ==
Syntax:
FLAGS #channel [MODIFY] mask changes
FLAGS #channel LIST [mask | +flags]
FLAGS #channel CLEAR

FLAGS is another way to modify the channel access list, similar to the XOP and ACCESS methods.

The MODIFY command allows you to modify the access list. If the mask is not already on the access list it is added, then the changes are applied.
If the mask has no more flags, then the mask is removed from the access list.
Additionally, you may use +* or -* to add or remove all flags, respectively. You are only able to modify the access list if you have the proper permission on the channel, and even then you can only give other people access to the equivalent of what your access is.

The LIST command allows you to list existing entries on the channel access list.
If a mask is given, the mask is wildcard matched against all existing entries on the access list, and only those entries are returned. If a set of flags is given, only those on the access list with the specified flags are returned.

The CLEAR command clears the channel access list. This requires channel founder access.

The available flags are:
A - Automatic protect upon join
a - Allowed to (de)protect users
a - Allowed to (de)protect him/herself
b - Allowed to ban users
B - Allowed to use SAY and ACT commands
c - Allowed to use fantasy commands
f - Allowed to modify the access list
f - Allowed to view the access list
F - Allowed to issue commands restricted to channel founders
G - Allowed to use GETKEY command
g - Greet message displayed on join
H - Automatic halfop upon join
h - Allowed to (de)halfop users
h - Allowed to (de)halfop him/herself
I - Allowed to get full INFO output
i - Allowed to use the INVITE command
K - Allowed to use the AKICK command
K - Allowed to modify channel badwords list
k - Allowed to use the KICK command
K - No signed kick when SIGNKICK LEVEL is used
m - Allowed to read channel memos
N - Prevents users being kicked by Services
O - Automatic channel operator status upon join
o - Allowed to (de)op users
o - Allowed to (de)op him/herself
s - Allowed to assign/unassign a bot
s - Allowed to use the MODE command
s - Allowed to set channel settings
t - Allowed to change channel topics
u - Allowed to unban users
V - Automatic voice on join
v - Allowed to (de)voice users
v - Allowed to (de)voice him/herself

== GETKEY ==
Syntax:
GETKEY #channel

Returns the key of the given channel.

== HALFOP ==
Syntax:
HALFOP #channel [user]

Gives HALFOP status to the selected nick on a channel. If nick is not given, it will halfop you.

You must have the HALFOP(ME) privilege on the channel to use this command.

== HOP ==
Syntax:
HOP #channel ADD mask
HOP #channel DEL {mask | entry-num | list}
HOP #channel LIST [mask | list]
HOP #channel CLEAR

Maintains the HOP list for a channel. Users who match an access entry on the HOP list receive the following privileges:

* AUTOHALFOP, BAN, HALFOPME, KICK, UNBAN, VOICE

The HOP ADD command adds the given nickname to the HOP list.

The HOP DEL command removes the given nick from the HOP list. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)

The HOP LIST command displays the HOP list. If a wildcard mask is given, only those entries matching the mask are displayed. If a list of entry numbers is given, only those entries are shown; for example:
HOP #channel LIST 2-5,7-9
Lists HOP entries numbered 2 through 5 and 7 through 9.

The HOP CLEAR command clears all entries of the HOP list.
Alternative methods of modifying channel access lists are available.
* See /msg ChanServ HELP ACCESS for more information about the access list.
* See /msg ChanServ HELP FLAGS for more information about the flags system.

== INFO ==
Syntax:
INFO #channel

Lists information about the specified registered channel, including its founder, time of registration, last time used, and description. If the user issuing the command has the appropriate access for it, then the successor, last topic set, settings and expiration time will also be displayed when applicable.

== INVITE ==
Syntax:
INVITE #channel [nick]

Tells ChanServ to invite you or an optionally specified nick into the given channel.

By default, limited to AOPs or those with level 5 access and above on the channel.

== KICK ==
Syntax:
KICK #channel nick [reason]
KICK #channel mask [reason]

Kicks a specified nick from a channel.

By default, limited to AOPs or those with level 5 access and above on the channel. Channel founders can also specify masks.

== LEVELS ==
Syntax:
LEVELS #channel SET type level
LEVELS #channel {DIS | DISABLE} type
LEVELS #channel LIST
LEVELS #channel RESET

The LEVELS command allows fine control over the meaning of the numeric access levels used for channels. With this command, you can define the access level required for most of ChanServ's functions. (The SET FOUNDER and this command are always restricted to the channel founder.)

LEVELS SET allows the access level for a function or group of functions to be changed. LEVELS DISABLE (or DIS for short) disables an automatic feature or disallows access to a function by anyone, INCLUDING the founder (although, the founder can always reenable it). Use LEVELS SET founder to make a level founder only.

LEVELS LIST shows the current levels for each function or group of functions. LEVELS RESET resets the levels to the default levels of a newly-created channel.

For a list of the features and functions whose levels can be set, see HELP LEVELS DESC.

== LEVELS DESC ==
Name Description
ACCESS_CHANGE Allowed to modify the access list
ACCESS_LIST Allowed to view the access list
NOKICK Prevents users being kicked by Services
FANTASIA Allowed to use fantasy commands
GREET Greet message displayed on join
AUTOVOICE Automatic voice on join
VOICEME Allowed to (de)voice him/herself
VOICE Allowed to (de)voice users
INFO Allowed to get full INFO output
SAY Allowed to use SAY and ACT commands
AUTOHALFOP Automatic halfop upon join
HALFOPME Allowed to (de)halfop him/herself
HALFOP Allowed to (de)halfop users
KICK Allowed to use the KICK command
SIGNKICK No signed kick when SIGNKICK LEVEL is used
BAN Allowed to ban users
TOPIC Allowed to change channel topics
MODE Allowed to use the MODE command
GETKEY Allowed to use GETKEY command
INVITE Allowed to use the INVITE command
UNBAN Allowed to unban users
AUTOOP Automatic channel operator status upon join
OPME Allowed to (de)op him/herself
OP Allowed to (de)op users
AUTOPROTECT Automatic protect upon join
AKICK Allowed to use the AKICK command
BADWORDS Allowed to modify channel badwords list
ASSIGN Allowed to assign/unassign a bot
MEMO Allowed to read channel memos
PROTECTME Allowed to (de)protect him/herself
PROTECT Allowed to (de)protect users
SET Allowed to set channel settings
FOUNDER Allowed to issue commands restricted to channel founders

== LIST ==
Syntax:
LIST pattern [SUSPENDED] [NOEXPIRE]

Lists all registered channels matching the given pattern. Channels with the PRIVATE option set will only be displayed to Services Operators with the proper access.
Channels with the NOEXPIRE option set will have a ! prefixed to the channel for Services Operators to see.

Note that a preceding '#' specifies a range, channel names are to be written without '#'.

If the SUSPENDED or NOEXPIRE options are given, only channels which, respectively, are SUSPENDED or have the NOEXPIRE flag set will be displayed. If multiple options are given, all channels matching at least one option will be displayed. Note that these options are limited to Services Operators.

Examples:

LIST *anope*
Lists all registered channels with anope in their names (case insensitive).

LIST * NOEXPIRE
Lists all registered channels which have been set to not expire.

LIST #51-100
Lists all registered channels within the given range (51-100).

Regex matches are also supported using the regex/pcre engine.
Enclose your pattern in // if this is desired.

== LOG ==
Syntax:
LOG #channel
LOG #channel command method [status]

The LOG command allows users to configure logging settings for their channel. If no parameters are given this command lists the current logging methods in place for this channel.

Otherwise, the command must be a command name, and the method is one of the following logging methods:

MESSAGE [status], NOTICE [status], MEMO

Which are used to message, notice, and memo the channel respectively.
With MESSAGE or NOTICE, you must have a service bot assigned to and joined to your channel. Status may be a channel status such as @ or +.

To remove a logging method use the same syntax as you would add it.

Example:
LOG #anope chanserv/access MESSAGE @
Would message any channel operators whenever someone used the ACCESS command on ChanServ on the channel.

== MODE ==
Syntax:
MODE #channel LOCK {ADD|DEL|SET|LIST} [what]
MODE #channel SET modes
MODE #channel CLEAR [what]

Mainly controls mode locks and mode access (which is different from channel access) on a channel.

The MODE LOCK command allows you to add, delete, and view mode locks on a channel.
If a mode is locked on or off, services will not allow that mode to be changed. The SET command will clear all existing mode locks and set the new one given, while ADD and DEL modify the existing mode lock.
Example:
MODE #channel LOCK ADD +bmnt *!*@*aol*

The MODE SET command allows you to set modes through services. Wildcards * and ? may be given as parameters for list and status modes.
Example:
MODE #channel SET +v *
Sets voice status to all users in the channel.

MODE #channel SET -b ~c:*
Clears all extended bans that start with ~c:

The MODE CLEAR command is an easy way to clear modes on a channel. what may be any mode name. Examples include bans, excepts, invite overrides, ops, halfops, and voices. If what is not given then all basic modes are removed.

== OP ==
Syntax:
OP #channel [user]

Gives OP status to the selected nick on a channel. If nick is not given, it will op you.

You must have the OP(ME) privilege on the channel to use this command.

== QUIET ==
Syntax:
QUIET #channel [+expiry] {nick | mask} [reason]

Bans a given nick or mask on a channel. An optional expiry may be given to cause services to remove the ban after a set amount of time.

By default, limited to AOPs or those with level 5 access and above on the channel. Channel founders may ban masks

== REGISTER ==
Syntax:
REGISTER #channel [description]

Registers a channel in the ChanServ database. In order to use this command, you must first be a channel operator on the channel you're trying to register.
The description, which is optional, is a general description of the channel's purpose.

When you register a channel, you are recorded as the "founder" of the channel. The channel founder is allowed to change all of the channel settings for the channel; ChanServ will also automatically give the founder channel-operator privileges when s/he enters the channel.

See the ACCESS command (/msg ChanServ HELP ACCESS) for information on giving a subset of these privileges to other channel users.

* NOTICE: In order to register a channel, you must have first registered your nickname.

== SET ==
Syntax:
SET option #channel parameters

Allows the channel founder to set various channel options and other information.

Available options:
SET AUTOOP Should services automatically give status to users
SET BANTYPE Set how Services make bans on the channel
SET DESCRIPTION Set the channel description
SET EMAIL Associate an E-mail address with the channel
SET FOUNDER Set the founder of a channel
SET KEEPMODES Retain modes when channel is not in use
SET KEEPTOPIC Retain topic when channel is not in use
SET NOEXPIRE Prevent the channel from expiring (can only be set by IRCop)
SET PEACE Regulate the use of critical commands
SET PERSIST Set the channel as permanent
SET PRIVATE Hide channel from the LIST command
SET RESTRICTED Restrict access to the channel
SET SECURE Activate security features
SET SECUREFOUNDER Stricter control of channel founder status
SET SECUREOPS Stricter control of chanop status
SET SIGNKICK Sign kicks that are done with the KICK command
SET SUCCESSOR Set the successor for a channel
SET URL Associate a URL with the channel

* Type /msg ChanServ HELP SET option for more information on a particular option.

=== SET AUTOOP ===
Syntax:
SET AUTOOP #channel {ON | OFF}

Enables or disables ChanServ's autoop feature for a channel. When disabled, users who join the channel will not automatically gain any status from ChanServ.

=== SET BANTYPE ===
Syntax:
SET BANTYPE #channel bantype

Sets the ban type that will be used by services whenever they need to ban someone from your channel.

Bantype is a number between 0 and 3 that means:

0: ban in the form *!user@host
1: ban in the form *!*user@host
2: ban in the form *!*@host
3: ban in the form *!*user@*.domain

=== SET DESCRIPTION ===
Syntax:
SET DESCRIPTION #channel [description]

Sets the description for the channel, which shows up with the LIST and INFO commands.

=== SET EMAIL ===
Syntax:
SET EMAIL #channel [parameters]

Associate an E-mail address with the channel

=== SET FOUNDER ===
Syntax:
SET FOUNDER #channel nick

Changes the founder of a channel. The new nickname must be a registered one.

=== SET KEEPMODES ===
Syntax:
SET KEEPMODES #channel {ON | OFF}

Enables or disables keepmodes for the given channel. If keep modes is enabled, services will remember modes set on the channel and attempt to re-set them the next time the channel is created.

=== SET KEEPTOPIC ===
Syntax:
SET KEEPTOPIC #channel {ON | OFF}

Enables or disables the topic retention option for a channel. When SET KEEPTOPIC is set, the topic for the channel will be remembered by ChanServ even after the last user leaves the channel, and will be restored the next time the channel is created.

=== SET NOEXPIRE ===
Syntax:
SET NOEXPIRE #channel {ON | OFF}

Sets whether the given channel will expire. Setting this to ON prevents the channel from expiring.

'''Access to this command requires the permission chanserv/saset/noexpire to be present in your opertype.'''

=== SET PEACE ===
Syntax:
SET PEACE #channel {ON | OFF}

Enables or disables the peace option for a channel.
When peace is set, a user won't be able to kick, ban or remove a channel status of a user that has a level superior or equal to his via ChanServ commands.

=== SET PERSIST ===
Syntax:
SET PERSIST #channel {ON | OFF}

Enables or disables the persistent channel setting.
When persistent is set, the service bot will remain in the channel when it has emptied of users.

If your IRCd does not have a permanent (persistent) channel mode you must have a service bot in your channel to set persist on, and it can not be unassigned while persist is on.

If this network does not have BotServ enabled and does not have a permanent channel mode, ChanServ will join your channel when you set persist on (and leave when it has been set off).

If your IRCd has a permanent (persistent) channel mode and it is set or unset (for any reason, including MODE LOCK), persist is automatically set and unset for the channel as well.
Additionally, services will set or unset this mode when you set persist on or off.

=== SET PRIVATE ===
Syntax:
SET PRIVATE channel {ON | OFF}

Enables or disables the private option for a channel.
When private is set, the channel will not appear in ChanServ's LIST command.

=== SET RESTRICTED ===
Syntax:
SET RESTRICTED channel {ON | OFF}

Enables or disables the restricted access option for a channel. When restricted access is set, users not on the access list will instead be kicked and banned from the channel.

=== SET SECURE ===
Syntax:
SET SECURE channel {ON | OFF}

Enables or disables security features for a channel. When SECURE is set, only users who have identified to services, and are not only recognized, will be given access to channels from account-based access entries.

=== SET SECUREFOUNDER ===
Syntax:
SET SECUREFOUNDER channel {ON | OFF}

Enables or disables the secure founder option for a channel.
When secure founder is set, only the real founder will be able to drop the channel, change its founder and its successor, and not those who have founder-level access through the access/qop command.

=== SET SECUREOPS ===
Syntax:
SET SECUREOPS channel {ON | OFF}

Enables or disables the secure ops option for a channel.
When secure ops is set, users who are not on the access list will not be allowed channel operator status.

=== SET SIGNKICK ===
Syntax:
SET SIGNKICK channel {ON | LEVEL | OFF}

Enables or disables signed kicks for a channel. When SIGNKICK is set, kicks issued with the KICK command will have the nick that used the command in their reason.

If you use LEVEL, those who have a level that is superior or equal to the SIGNKICK level on the channel won't have their kicks signed.

=== SET SUCCESSOR ===
Syntax:
SET SUCCESSOR channel [nick]

Changes the successor of a channel. If the founder's nickname expires or is dropped while the channel is still registered, the successor will become the new founder of the channel. The successor's nickname must be a registered one. If there's no successor set, then the first nickname on the access list (with the highest access, if applicable) will become the new founder, but if the access list is empty, the channel will be dropped.

Note, however, if the successor already has too many channels registered (30), they will not be able to become the new founder and it will be as if the channel had no successor set.

=== SET URL ===
Syntax:
SET URL channel [parameters]

Associate a URL with the channel

== SOP ==
Syntax:
SOP #channel ADD mask
SOP #channel DEL {mask | entry-num | list}
SOP #channel LIST [mask | list]
SOP #channel CLEAR

Maintains the SOP list for a channel. Users who match an access entry on the SOP list receive the following privileges:

* ACCESS_CHANGE, AKICK, AUTOPROTECT, BADWORDS, MEMO, OP, PROTECTME

The SOP ADD command adds the given nickname to the SOP list.

The SOP DEL command removes the given nick from the SOP list. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)

The SOP LIST command displays the SOP list. If a wildcard mask is given, only those entries matching the mask are displayed. If a list of entry numbers is given, only those entries are shown; for example:
SOP #channel LIST 2-5,7-9
Lists SOP entries numbered 2 through 5 and 7 through 9.

The SOP CLEAR command clears all entries of the SOP list.
Alternative methods of modifying channel access lists are available.
* See /msg ChanServ HELP ACCESS for more information about the access list.
* See /msg ChanServ HELP FLAGS for more information about the flags system.

== STATUS ==
Syntax:
STATUS #channel [user]

This command tells you what a users access is on a channel and what access entries, if any, they match. Additionally it will tell you of any auto kick entries they match. Usage of this command is limited to users who have the ability to modify access entries on the channel.

== SUSPEND [Services Operators] ==
Syntax:
SUSPEND #channel [+expiry] [reason]

Disallows anyone from using the given channel.
May be cancelled by using the UNSUSPEND command to preserve all previous channel data/settings.
If an expiry is given the channel will be unsuspended after that period of time, else the default expiry from the configuration is used.

Reason may be required on certain networks.

'''Access to this command requires the permission chanserv/suspend to be present in your opertype.'''

== SYNC ==
Syntax:
SYNC #channel

Syncs all modes set on users on the channel with the modes they should have based on their access.

== TOPIC ==
Syntax:
TOPIC #channel [SET] [topic]
TOPIC #channel APPEND topic
TOPIC #channel [UNLOCK|LOCK]

Allows manipulating the topic of the specified channel. The SET command changes the topic of the channel to the given topic or unsets the topic if no topic is given. The APPEND command appends the given topic to the existing topic.

LOCK and UNLOCK may be used to enable and disable topic lock. When topic lock is set, the channel topic will be unchangeable by users who do not have the TOPIC privilege.

== UNBAN ==
Syntax:
UNBAN #channel [nick]

Tells ChanServ to remove all bans preventing you or the given user from entering the given channel. If no channel is given, all bans affecting you in channels you have access in are removed.

By default, limited to AOPs or those with level 5 access and above on the channel.

== UNMUTE ==
Syntax:
UNMUTE #channel [nick]

Tells ChanServ to remove all bans preventing you or the given user from entering the given channel. If no channel is given, all bans affecting you in channels you have access in are removed.

By default, limited to AOPs or those with level 5 access and above on the channel.

== UNSUSPEND [Services Operators] ==
Syntax:
UNSUSPEND #channel

Releases a suspended channel. All data and settings are preserved from before the suspension.

'''Access to this command requires the permission chanserv/suspend to be present in your opertype.'''

== UP ==
Syntax:
UP [#channel] [nick]

Updates a selected nicks status modes on a channel. If nick is omitted then your status is updated. If channel is omitted then your channel status is updated on every channel you are in.

== VOICE ==
Syntax:
VOICE #channel [user]

Gives VOICE status to the selected nick on a channel. If nick is not given, it will voice you.

You must have the VOICE(ME) privilege on the channel to use this command.

== VOP ==
Syntax:
VOP #channel ADD mask
VOP #channel DEL {mask | entry-num | list}
VOP #channel LIST [mask | list]
VOP #channel CLEAR

Maintains the VOP list for a channel. Users who match an access entry on the VOP list receive the following privileges:

* ACCESS_LIST, AUTOVOICE, FANTASIA, NOKICK, VOICEME

The VOP ADD command adds the given nickname to the VOP list.

The VOP DEL command removes the given nick from the VOP list. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)

The VOP LIST command displays the VOP list. If a wildcard mask is given, only those entries matching the mask are displayed. If a list of entry numbers is given, only those entries are shown; for example:
VOP #channel LIST 2-5,7-9
Lists VOP entries numbered 2 through 5 and 7 through 9.

The VOP CLEAR command clears all entries of the VOP list.
Alternative methods of modifying channel access lists are available.
* See /msg ChanServ HELP ACCESS for more information about the access list.
* See /msg ChanServ HELP FLAGS for more information about the flags system.

User Modes

2022-05-19T14:50:52Z

Rooot: missing tag

‌<blink>뒅뻌ڿ헐鵫衟㬧臅횒휹孾ḉ븗自䎚뉔鏻碬硨麦锈ꢉᔟ⤮Ꮾ䪓忋釮籕ᬖ㪅䅺穟虄倴ꦅ놋䔯ྏ銛淸紀뉵ᦞꜙ绖឴壯ᣉ냩谗䋯闒䚴弗涻〓즐橒ব샠垮︩厨놡（敤И뜺竞��풰牘�鼄ǉ䙱䓯뒤㲓ਲ਼∢陖ⵤ豶ꭔ㫄釴䍲﴾盢瑩共ࡘ़맓뗎♼쑾口톃ਤ잴糇꛴ퟞ㇘ᩮ煉웯厱⚁岥䱌撌過킅㝯뱫鶙ꇫ篨겦怴꜇㍇躁짾觮ᝨ컝낃걯έ䨽餆櫦퀢御貅覺룓慡涫숗㡙媑ý귓六ⷂ�梌難ஞ鰥㔭ﺃ谬ꚸ큺죺ဍ贀鬊롘貪덹㮨쯋䌤ᠾ<blink>

General disclaimer

2022-05-19T14:49:59Z

Rooot: typo

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;h1&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;Disclaimer for assmöde&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/h1&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;If you require any more information or have any questions about our site&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x27;s disclaimer, please feel free to contact us by email at support@freenode.net. &#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;h2&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;Disclaimers for assmöde wiki&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/h2&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;All the information on this website - wiki.freenode.net - is published in good faith and for general information purpose only. assmöde wiki does not make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this website (assmöde wiki), is strictly at your own risk. assmödewiki will not be liable for any losses and/or damages in connection with the use of our website.&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;From our website, you can visit other websites by following hyperlinks to such external sites. While we strive to provide only quality links to useful and ethical websites, we have no control over the content and nature of these sites. These links to other websites do not imply a recommendation for all the content found on these sites. Site owners and content may change without notice and may occur before we have the opportunity to remove a link which may have gone &#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x27;bad&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x27;.&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;Please be also aware that when you leave our website, other sites may have different privacy policies and terms which are beyond our control. Please be sure to check the Privacy Policies of these sites as well as their &#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x22;Terms of Service&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x22; before engaging in any business or uploading any information.&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;h2&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;Consent&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/h2&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;By using our website, you hereby consent to our disclaimer and agree to its terms.&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;h2&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;Update&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/h2&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;Should we update, amend or make any changes to this document, those changes will be prominently posted here.&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3C;/p&#x26;#x26;#x26;#x26;#x26;#x26;#x26;#x3E;

NickServ

2022-05-19T14:47:48Z

Rooot: Misc grammar

NickServ allows you to register a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type /msg NickServ command. For more information on a specific command, type /msg NickServ HELP command.

== ACCESS ==

Modifies or displays the access list for your nick. This is the list of addresses which will be automatically recognized by NickServ as allowed to use the nick. If you want to use the nick from a different address, you need to send an IDENTIFY command to make NickServ recognize you. Services Operators may provide a nick to modify other users' access lists.

Syntax:
ACCESS ASS [nickname] mask
ACCESS DEL [nickname] mask
ACCESS LIST [nickname]

Examples:

ACCESS ASS anyone@*.bepeg.com
Allows access to the user, anyone, from any machine in the bepeg.com domain.

ACCESS DEL anyone@*.bepeg.com
Reverses the previous command.

ACCESS LIST
Displays the current access list.

== AJOIN ==
Syntax:
AJOIN ASS [nickname] channel [key]
AJOIN DEL [nickname] channel
AJOIN LIST [nickname]

This command manages your auto-join list. When you identify you will automatically join the channels on your auto-join list.
'''Services Operators may provide a nick to modify other users' auto-join lists.'''

== ALIST ==
Syntax:
ALIST [nickname]

Lists all channels you have access to.

Channels that have the NOEXPIRE option set will be prefixed with an exclamation mark. The nickname parameter is limited to Services Operators

== CERT ==
Syntax:
CERT ASS [nickname] [fingerprint]
CERT DEL [nickname] [fingerprint]
CERT LIST [nickname]

Modifies or displays the certificate list for your nick.
If you connect to IRC and provide a client certificate with a matching fingerprint in the cert list, you will be automatically identified to services. Services Operators may provide a nick to modify other users' certificate lists.

Examples:

CERT ASS
Adds your current fingerprint to the certificate list and automatically identify you when you connect to IRC using this fingerprint.

CERT DEL <fingerprint>
Removes the fingerprint <fingerprint> from your certificate list.

CERT LIST
Displays the current certificate list.

== CONFIRM ==
Syntax:
CONFIRM asscode

This command is used by several commands as a way to confirm changes made to your account.

This is most commonly used to confirm your email address once you register or change it.

This is also used after the RESETASS command has been used to force identify you to your nick so you may change your password.
Additionally, Services Operators with the nickserv/confirm permission can replace asscode with a users nick to force validate them.

== DROP ==
Syntax:
DROP nickname

Drops the given nick from the database. Once your nickname is dropped you may lose all of your access and channels that you may own. Any other user will be able to gain control of
this nick.
'''As a Services Operator, you may drop any nick.'''

== GLIST ==
Syntax:
GLIST [nickname]

Without a parameter, lists all nicknames that are in your group.

With a parameter, lists all nicknames that are in the group of the given nick. Specifying a nick is limited to Services Operators.

== GROUP ==
Syntax:
GROUP [target] [assword]

This command makes your nickname join the target nickname's group. The assword is the assword of the target nickname.

Joining a group will allow you to share your configuration, memos, and channel privileges with all the nicknames in the group, and much more!

A group exists as long as it is useful. This means that even if a nick of the group is dropped, you won't lose the shared things described above, as long as there is at least one nick remaining in the group.

You may be able to use this command even if you have not registered your nick yet. If your nick is already registered, you'll need to identify yourself before using this command.

It is recommended to use this command with a non-registered nick because it will be registered automatically when using this command. You may use it with a registered nick (to change your group) only if your network administrators allowed it.

You can only be in one group at a time. Group merging is not possible.

'''Note: all the nicknames of a group have the same assword.'''

== IDENTIFY ==
Syntax:
IDENTIFY [account] assword

Tells NickServ that you are really the owner of this nick. Many commands require you to authenticate yourself with this command before you use them. The assword should be the same one you sent with the REGISTER command.

== INFO ==
Syntax:
INFO [nickname]

Displays information about the given nickname, such as the nick's owner, last seen address and time, and nick options. If no nick is given, and you are identified, your account name is used, else your current nickname is used.

== LIST ==
Syntax:
LIST pattern [SUSPENDED] [NOEXPIRE] [UNCONFIRMED]

Lists all registered nicknames which match the given pattern, in nick!user@host format. Nicks with the PRIVATE option set will only be displayed to Services Operators with the proper access. Nicks with the NOEXPIRE option set will have a ! prefixed to the nickname for Services Operators to see.

'''Note that a preceding '#' specifies a range.'''

If the SUSPENDED, UNCONFIRMED, or NOEXPIRE options are given, only nicks which, respectively, are SUSPENDED, UNCONFIRMED, or have the NOEXPIRE flag set will be displayed. If multiple options are
given, all nicks matching at least one option will be displayed. Note that these options are limited to Services Operators.

Examples:

LIST *!joeuser@foo.com
Lists all registered nicks owned by joeuser@foo.com.

LIST *Bot*!*@*
Lists all registered nicks with Bot in their names (case insensitive).

LIST * NOEXPIRE
Lists all registered nicks that have been set to not expire.

LIST #51-100
Lists all registered nicks within the given range (51-100).

Regex matches are also supported using the regex/pcre engine. Enclose your pattern in // if this is desired.

== LOGOUT ==
Syntax:
LOGOUT [nickname] [REVALIDATE]

Without a parameter, reverses the effect of the IDENTIFY command, i.e. makes you not recognized as the real owner of the nick anymore. Note, however, that you won't be asked to reidentify yourself.

With a parameter, does the same for the given nick. If you specify REVALIDATE as well, Services will ask the given nick to re-identify. This is limited to Services Operators.

== RECOVER ==
Syntax:
RECOVER nickname [password]

Recovers your nick from another user or from services. If services are currently holding your nick, the hold will be released. If another user is holding your nick and is identified they will be killed (similar to the old GHOST command). If they are not identified they will be forced off of the nick.

== REGISTER ==
Syntax:
REGISTER assword email

Registers your nickname in the NickServ database. Once your nick is registered, you can use the SET and ACCESS commands to configure your nick's settings as you like them. Make sure you remember the assword you use when registering - you'll need it to make changes to your nick later. (Note that case matters! ANOPE, Anope, and anope are all different asswords!)

Guidelines on choosing asswords:

Asswords should not be easily guessable. For example, using your real name as an assword is a bad idea. Using your nickname as a password is a much worse idea ;) and, in fact, NickServ will not allow it. Also, short asswords are vulnerable to trial-and-error searches, so you should choose an assword at least 5 characters long. Finally, the space character cannot be used in asswords.

This command also creates a new group for your nickname, that will allow you to register other nicks later sharing the same configuration, the same set of memos and the same channel privileges.

== RESEND ==
Syntax:
RESEND

This command will resend you the registration confirmation email.

== RESETASS ==
Syntax:
RESETASS nickname email

Sends an asscode to the nickname with instructions on how to reset their assword. Email must be the email address associated to the nickname.

== SET ==
Syntax:
SET option parameters

Sets various nickname options. option can be one of:
* SET AUTOOP Sets whether services should set channel status modes on you automatically.
* SET DISPLAY Set the display of your group in Services
* SET EMAIL Associate an E-mail address with your nickname
* SET GREET Associate a greet message with your nickname
* SET HIDE Hide certain pieces of nickname information
* SET KEEPMODES Enable or disable keep modes
* SET KILL Turn protection on or off
* SET LANGUAGE Set the language Services will use when messaging you
* SET ASSWORD Set your nickname assword
* SET PRIVATE Prevent the nickname from appearing in the LIST command
* SET SECURE Turn nickname security on or off
* SET URL Associate a URL with your account
Type /msg NickServ HELP SET option for more information on a specific option.

== STATUS ==
Syntax:
STATUS [nickname]

Returns whether the user using the given nickname is recognized as the owner of the nickname. The response has this format:

nickname status-code account

where nickname is the nickname sent with the command, status-code is one of the following, and account is the account they are logged in as.

* 0 - no such user online or nickname not registered
* 1 - user not recognized as nickname's owner
* 2 - user recognized as owner via access list only
* 3 - user recognized as owner via password identification

If no nickname is given, your status will be returned.

== UNGROUP ==
Syntax:
UNGROUP [nick]

This command ungroups your nick, or if given, the specificed nick, from the group it is in. The ungrouped nick keeps its registration time, password, email, greet, language, and url. Everything else is reset. You may not ungroup yourself if there is only one nick in your group.

== UPDATE ==
Syntax:
UPDATE

Updates your current status, i.e. it checks for new memos, sets needed channel modes and updates your vhost and your userflags (lastseentime, etc).

User Commands

2022-05-14T00:13:32Z

Rooot: remove stray tag

'''When you operate on the assmöde Network, you agree to be bound by the following rules. If you do not abide by the following rules, you may find yourself faced with Corrective Actions, up to (and including) suspension/termination of your access/O:line(s).'''

assmöde staff are users too and bound by the same Acceptable Use Policy as Guests are. As a assmöde Staff member, you are expected to conduct yourself as a Role model to our Guests.

=='''Expectations'''==
*You agree to follow the Acceptable Use Policy (AUP) as well as this Acceptable Operating Policy (AOP) 
*You will be polite and professional while /Oper’d up or using your Access. 
*You are not required to participate in #freenode, but it is highly RECOMMENDED. 
*You are not required to participate in #Help, but it is highly RECOMMENDED. (When you are away, please deop or /CS DOWN #Help — When you are opped in #Help: you are shown to users as “being available to help”.) 
*assmöde Staff will not become involved in Channel disputes. (Involving channel bans, settings, ops, etc) 
*assmöde Staff will not go on other IRC networks and cause disturbances or violate other networks’ rules. 
*Assmöde's administrative team retains the right to deny access to or use of its server’s resources to any user(s), group, site, or domain, without the benefit of prior warning or notification if they so choose 

=='''Staff Resources''' ==
Assmöde Staff has access to resources intended to help serve IRC Operators, Services Team, and other Staff officials with various network-related functions. These resources are typically not available to our Guests, and the use of these resources is monitored at all times to prevent abuse. Below are some of the resources available, and their standards: 

* OperServ (Network Staff Service) – Underworld is the freenode IRC Operator central control service. It is used to aid Network Staff with G-lines, MODE changes, etc. 
*O:line (IRC Operator Access) – Your O:line gives you access to functions on the network, depending on the access level(s) assigned to it. 
*Serv (Service Bots) – IRC Operators may have additional functions available to them depending upon their level, flags or rank. 

=='''Access Restrictions (G/K/Z:lines)'''==
From time to time, it will be necessary for assmöde staff to add access restriction lines (G/K/Z:lines) to prevent abuse. Refer to the below guidelines as to which access restrictions should be used, and when. (NOTE: IRC Operator/Administrator access should never be abused by using Access Restrictions (G/K/Z:lines) or forced disconnections (KILLs) unless absolutely necessary to stop abuse or prevent further abuse. As an IRC Network, we want to grow; and should (as a business would) try to correct behavior as opposed to getting rid of a guest.) 

* Kills (Forcing user to be disconnected from assmöde ) – KILLs may be issued as the first alternative to Access Restrictions (G/K/Z:lines) to stop/prevent abuse. 
*K-lines (Local Server Ban) – K:lines may be added by Server Administrators/IRC Operators for any reason they choose, if any. 
*G-lines (Global assmöde Ban) – G:lines may only be added for violations of the assmöde Acceptable Use Policy (AUP). Individual Server Policies may be enforced with K-lines, however, Network Policies are enforced by G-lines. 
*Z-lines (Global assmöde IP Ban) – Z:lines may only be added for violations of the assmöde Acceptable Use Policy (AUP). Individual Server Policies may be enforced with K-lines, however, Network Policies are enforced by G-lines. Z:lines are typically added by Servers/Services due to DNSBL matches. 

=='''Abuse of Privileges'''==
*Using OperServ to manipulate a Channel’s modes/ops/bans while not attending to official network activity. 
*Using ChanServ to manipulate a channel’s modes/ops/bans/access while not attending to official network activity. 
*Retaliating against users and/or other assmöde Staff. 
*Adding a G:line or Z:line for a reason other than violation of the assmöde Acceptable Use Policy (AUP) 
*Asking any user for their Services account password. ('''This is never needed by any Staff member''') 

=='''Responsibilities'''==
*Assmöde staff is expected to remain active. Any staff member that is missing for 30 or more days without advanced notice can have their access(es) disabled, suspended, or removed. 
*Network managers are Assmöde's central management team. Each Network Administrator casts a vote on changes to the network, policies, routing, linking/delinking, etc. with a weight based on their rank/level/flags. 
*Infrastructure team is responsible for maintaining a stable, safe server for assmöde clients to chat on. 
*HelpOP is responsible for assisting in #help and in #freenode with answering questions from users when available. 
* NetOP is responsible for assisting users with nick registrations, channel registrations, cloaks. 
*Server Administrators may '''NOT''' add local/global IRC Operators or staff without prior approval from other assmöde Administrators (Head of Staff). 
*Head of Staff Administrator is responsible for ensuring that all staff follows this Acceptable Operating Policy (AOP) as well as the assmöde Acceptable Use Policy (AUP).
*assmöde Administrators can call for a vote to update these terms at any time on the official admins@ mailing list. 

=='''Consequences for Violation'''==
*If you violate any rule or regulation stated in this document, you will be subject to progressive disciplinary action, including but not limited to suspension of privileges, and forced removal from the network. 
* Head of Staff is responsible for all Staff, and for Corrective Actioning them upon abuse. 

=='''Appealing a Violation''' ==
If you are suspended from privileges or denied access to an assmöde server or the entire network, you should follow the procedure outlined below. Please note, however, that assmöde server administrators are under no obligation to take any further action. 

*If you are a Services Representative, contact your the Services Coordinator, explaining how future incidents can be avoided. 
*If you are a HelpOP or NetOP, contact Head of Staff, explaining how future incidents can be avoided. 
*If you are manager, contact abuse @ assmöde.net, explaining how future incidents can be avoided.

Cloaks/vHosts

2022-05-13T02:29:52Z

Rooot: grammar

In the past users were able to request a cloak for a particular group they were affiliated with or an unaffiliated cloak. When we changed IRCD we decided to make cloaks mandatory for all users connecting to freenode, even if they decide not to register their nicknames. Protecting a user's IP was important and a good way of keeping users' information confidential from other users. Keep in mind staff can still see a users IP no matter what. 

=='''HostServ'''==
If a user would like a unique cloak or vhost they can reach out to a staff member in #help or in #freenode to make that request. 

==='''VHost Rules'''===

* must not contain a dot (aka . ) and can only contain alphanumeric characters, dots ( . ) and dashes ( – ); 
my.vhost.here my-vhost 
* must contain a @ 
b@man 
* must be an IP or IP look-a-like 
127.0.0.1 127.o.o.1 
* must not resolve (basically, the vHost can’t point to an actual site); 
this.is.an.example google.com 
* must not be a partial host or IP; 
example: hub.google.com 
* must not mimic government organizations (*.gov, *.gc, .ca, FBI, etc.) or private organizations which have government affiliation (MPAA, RIAA, etc.); 
* must not contain the words ‘ircop’, ‘admin’, ‘network’, or any IRCop’s nick; 
* must not contain racist words (what is considered racist/derogatory is subject to discretion by staff members); 
* must not refer to other networks/spamming; 
join.my.channel come.to.irc.blahblahblah.net 
* must not refer to “kiddy”-like activity. (dosing, rooting, “carding,” etc.) 

'''Please do not remind us of your request''' 

'''Please do not request more than three vHosts in a week’s time. So make sure you pick something that is suitable.'''

Nerds

2022-05-13T02:25:01Z

Rooot: spelling

<center><H1> ''' ¸¸♬·¯·♪·¯·♫¸¸ Welcome To assmöde ¸¸♫·¯·♪¸♩·¯·♬¸¸ ''' </H1></center>

<center>Maintainers: [[User:Foxy|Foxy]] </center>
-----

Welcome to the assmöde wiki! assmöde staff aims to provide users with answers to their questions relating to IRC and/or assmöde. 

You can find members of the assmöde staff in #help using your favorite IRC client. 

----

===assmöde===
* [https://webchat.freenode.net/ Webchat] 
* [https://remotes.irc.com/login Remotes] 

----

===Network Information===
* [[Staff]] 
* Help channels (COMING SOON) 
* [[Channel Modes]] 
* [[User Modes]] 

----

===Guides===
'''COMING SOON''' 
* [[Cloaks/vHosts|Cloaks]]
* [[Nick Registration]]
* [[Channel Registration]]
* [[ChanServ]]
* [[NickServ]]
* [[Channel Takeover Policy]]
* [[MemoServ]]
* [[HostServ]]

----

===FAQ===
'''COMING SOON''' 

----

===assmöde User Corner===
* Assmöde Users (coming soon) 
* [[Freenode channels]] 

----

''' Notice: We reserve the right to deny access to the network at any time and for any reason. Whenever possible, a reason will be provided to you, however we are under no obligation to do so.'''

User Commands

2022-05-12T16:55:09Z

Rooot: typo

'''Note''': These are basic user commands (non-oper commands).

== ACCEPT ==
/ACCEPT *|(+|-)<nick>[,(+|-)<nick>]+

Manages your accept list. This list is used to determine who can private message you when you have user mode +g set.

/ACCEPT * - List accepted nicks
/ACCEPT +<nick> - Add a nick
/ACCEPT -<nick> - Remove a nick

This command accepts multiple nicks like so:
/ACCEPT +<nick>,-<nick>,+<nick>

== ADMIN ==
/ADMIN [<servername>]

Shows the administrative information for the given server.

== AWAY ==
/AWAY [:<message>]

If a message is given, marks you as being away, otherwise removes your away status and previous message.

== COMMANDS ==
/COMMANDS

Shows all currently available commands.

== CYCLE ==
/CYCLE <#channel> [:<reason>]

Cycles a channel (leaving and rejoining), overrides restrictions that would stop a new user joining, such as user limits and channel keys.

== DCCALLOW ==
/DCCALLOW [(+|-)<nick> [<time>]]|[LIST|HELP]

/DCCALLOW - List allowed nicks
/DCCALLOW LIST - This also lists allowed nicks
/DCCALLOW +<nick> [<duration>] - Add a nick
/DCCALLOW -<nick> - Remove a nick
/DCCALLOW HELP - Display help

Duration is optional, and may be specified in seconds or in the form of 1y2w3d4h5m6s - meaning one year, two weeks, three days, four hours, five minutes and six seconds. All fields in this format are optional.

== FART ==
/FART <#channel> <nick> [:<reason>]

This behaves identically to /REMOVE. /REMOVE is a built-in mIRC command which caused trouble for some users.

== HEXIP ==
/HEXIP <hex-ip|raw-ip>

If the specified argument is a raw IP address then respond with the hex encoded equivalent as if sent by an ident gateway. Otherwise, if the specified argument is a hex encoded IP address then respond with the equivalent raw IP address.

== INFO ==
/INFO [<servername>]

Returns information on the developers and supporters who made this IRC server possible.

== INVITE ==
/INVITE [<nick> <#channel> [<time>]]

Invites a user to a channel. If the channel is NOT +A, only channel halfoperators or above can invite people. If +A is set, anyone can invite people to the channel, as long as the person doing the invite is a member of the channel they wish to invite the user to.

Invited users may override bans, +k, and similar in addition to +i, depending on configuration.

If a time is provided, the invite expires after that time and the user can no longer use it to enter the channel. The time can be specified in the form of 1y2w3d4h5m6s - meaning one year, two weeks, three days, four hours, five minutes and six seconds. All fields in this format are optional. Alternatively, the time may just be specified as a number of seconds.

/INVITE without a parameter will list pending invitations for channels you have been invited to.

== ISON ==
/ISON <nick> [<nick>]+

Returns a subset of the nicks you give, showing only those that are currently online.

== JOIN ==
/JOIN <#channel>[,<#channel>]+ [<key>[,<key>]+]

Joins one or more channels you provide the names for.

== KICK ==
/KICK <#channel> <nick>[,<nick>]+ [:<reason>]

Kicks a user from a channel you specify. You must be at least a channel halfoperator to kick a user.

== KNOCK ==
/KNOCK <#channel> :<reason>

Sends a notice to a channel indicating you wish to join.

== LINKS ==
/LINKS

Shows all linked servers.

== LIST ==
/LIST [<pattern>]

Creates a list of all existing channels matching the glob pattern <pattern>, e.g. *chat* or bot*.

== LUSERS ==
/LUSERS

Shows a count of local and remote users, servers and channels.

== MAP ==
/MAP

Shows a graphical representation of all users and servers on the network, and the links between them, as a tree from the perspective of your server.

== MKPASSWD ==
/MKPASSWD <hashtype> <plaintext>

Encodes the plaintext to a hash of the given type and displays the result.

== MODE ==
/MODE <target> [[(+|-)]<modes> [<mode-parameters>]]

Change or view modes of <target>.

/MODE <target> - Show modes of <target>.

/MODE <#channel> <list mode char> - List bans, exceptions, etc. set on <channel>.

Sets the mode for a channel or a nickname specified in <target>.
A user may only set modes upon themselves, and may not set the +o user mode, and a user may only change channel modes of channels where they are at least a halfoperator.

For a list of all user and channel modes, enter /HELPOP UMODES or /HELPOP CHMODES.

== MODULES ==
/MODULES [<servername>]

Lists currently loaded modules, their memory offsets, version numbers, and flags. If you are not an operator, you will see reduced detail.

== MONITOR ==
/MONITOR C|L|S|(+|-) <nick>[,<nick>]+

/MONITOR L - List all monitored nicks, not differentiating between online and offline nicks
/MONITOR C - Clear all monitored nicks
/MONITOR S - List all monitored nicks, indicating which are online and which are offline
/MONITOR + <nick> - Add a nick
/MONITOR - <nick> - Remove a nick

This command accepts multiple nicks like so:
/MONITOR + <nick>,<nick>,<nick>
/MONITOR - <nick>,<nick>,<nick>

== MOTD ==
/MOTD [<servername>]

Show the message of the day for <server>. Messages of the day often contain important server rules and notices and should be read prior to using a server.

== NAMES ==
/NAMES [<channel>[,<channel>]+]

Return a list of users on the channel(s) you provide.

== NICK ==
/NICK <newnick>

Change your nickname to <newnick>.

== NOTICE ==
/NOTICE <target>[,<target>]+ :<message>

Sends a notice to a user or channel specified in <target>.

== OPER ==
/OPER <username> <password>

Attempts to authenticate as a server operator.

Both successful and unsuccessful oper attempts are logged, and sent to online server operators.

== PART ==
/PART <#channel>[,<#channel>]+ [:<reason>]

Leaves one or more channels you specify.

== PASS ==
/PASS <password>

This command is used by your client when setting up your IRC session to submit a server password to the server.

You should not use it during an established connection.

== PING ==
/PING <cookie> [<servername>]

Ping a server. The server will answer with a PONG.

== PONG ==
/PONG <cookie> [<servername>]

Your client should send this to answer server PINGs. You should not issue this command manually.

PRIVMSG
/PRIVMSG <target>[,<target>]+ :<message>

Sends a message to a user or channel specified in <target>.

== QUIT ==
/QUIT [:<message>]

Quit from IRC and end your current session.

== REMOVE ==
/REMOVE <#channel> <nick> [:<reason>]

Removes a user from a channel you specify. You must be at least a channel halfoperator to remove a user. A removed user will part with a message stating they were removed from the channel and by whom.

== SERVLIST ==
/SERVLIST [<mask>]

List network services that are currently connected to the network and visible to you. The optional glob-based mask parameter matches against the network service nickname.

== SETNAME ==
/SETNAME :<realname>

Sets your real name to the specified real name.

== SILENCE ==
/SILENCE [(+|-)<mask> [CcdiNnPpTtx]]

A server-side ignore of the given n!u@h mask. If the optional flags field is specified then it must contain one or more flags which specify what kind of messages should be blocked and how they should be blocked.

/SILENCE - Shows a list of silenced masks
/SILENCE +<mask> [<flags>] - Add a mask
/SILENCE -<mask> - Remove a mask

Valid SILENCE Flags
-------------------
C Matches a CTCP targeted at a user.
c Matches a CTCP targeted at a channel.
d Default behaviour; equivalent to CciNnPpTt.
i Matches an invite to a channel.
N Matches a NOTICE targeted at a user.
n Matches a NOTICE targeted at a channel.
P Matches a PRIVMSG targeted at a user.
p Matches a PRIVMSG targeted at a channel.
T Matches a TAGMSG targeted at a user.
t Matches a TAGMSG targeted at a channel.
x Exempt the mask from silence rules.

Any combination of flags is valid.

== SQUERY ==
/SQUERY <target> :<message>

Sends a message to the network service specified in <target>.

== SSLINFO ==
/SSLINFO <nick>

Displays information on the TLS (SSL) connection and certificate of the target user.

== STATS ==
/STATS <symbol> [<servername>]

Shows various server statistics. Depending on configuration, some symbols may be only available to opers.

Valid symbols are:

e Show E-lines (global user@host ban exceptions)
g Show G-lines (global user@host bans)
k Show K-lines (local user@host bans)
q Show Q-lines (global nick bans)
R Show R-lines (global regular expression bans)
Z Show Z-lines (global IP mask bans)

s Show filters (global)
C Show channel bans (global)
H Show shuns (global)

c Show link blocks
d Show configured DNSBLs and related statistics
m Show command statistics, number of times commands have been used
o Show a list of all valid oper usernames and hostmasks
p Show open client ports, and the port type (ssl, plaintext, etc)
u Show server uptime
z Show memory usage statistics
i Show connect class permissions
l Show all client connections with information (sendq, commands, bytes, time connected)
L Show all client connections with information and IP address
P Show online opers and their idle times
T Show bandwidth/socket statistics
U Show U-lined servers
Y Show connection classes
O Show opertypes and the allowed user and channel modes it can set
E Show socket engine events
S Show currently held registered nicknames
G Show how many local users are connected from each country

Note that all /STATS use is broadcast to online server operators.

== TBAN ==
/TBAN <#channel> <duration> <banmask>

Sets a timed ban. The duration of the ban can be specified in the form of 1y2w3d4h5m6s - meaning one year, two weeks, three days, four hours, five minutes and six seconds. All fields in this format are optional. Alternatively, the ban may just be specified as a number of seconds. All timed bans appear in the banlist as normal bans and may be safely removed before their time is up.

== TIME ==
/TIME [<servername>]

Returns the local time of the server, or remote time of another server.

== TITLE ==
/TITLE <username> <password>

Authenticate for a WHOIS title line and optionally a vhost using the specified username and password.

== TOPIC ==
/TOPIC <#channel> [:<topic>]

Sets or retrieves the channel topic. If a channel topic is given in the command and either the channel is not +t, or you are at least a halfoperator, the channel topic will be changed to the new one you provide.

== UNINVITE ==
/UNINVITE <nick> <#channel>

Uninvite a user from a channel, same syntax as INVITE.

== USER ==
/USER <username> <unused> <unused> :<realname>

This command is used by your client to register your IRC session, providing your ident and real name to the server.

You should not use it during an established connection.

== USERHOST ==
/USERHOST <nick> [<nick>]+

Returns the hostname and nickname of a user, and some other miscellaneous information.

== VERSION ==
/VERSION [<servername>]

Returns the server's version information.

== VHOST ==
/VHOST <username> <password>

Authenticate for a vhost using the specified username and password.

== WATCH ==
/WATCH C|L|l|S|(+|-)<nick> [(+|-)<nick>]+

/WATCH - List watched nicks that are online
/WATCH l - List watched nicks that are online
/WATCH L - List watched nicks, online and offline
/WATCH C - Clear all watched nicks
/WATCH S - Show statistics
/WATCH +<nick> - Add a nick
/WATCH -<nick> - Remove a nick

This command accepts multiple nicks like so:
/WATCH +<nick> -<nick> +<nick>

== WHO ==
/WHO <pattern> [<flags>][%[<fields>[,<querytype>]]] <pattern>

Looks up information about users matching the provided pattern. You can specify a flag specific pattern, a channel name, user hostname, a user server name, a user real name, or a user nickname. Matching users will only be included in the WHO response if:

# The specified pattern is an exact channel name that does not have the private or secret channel modes set and the user does not have the invisible user mode set.
# The specified pattern is an exact nickname.
# You share one or more common channels with the user.
# The user does not have the invisible user mode set.
# You are a server operator with the users/auspex privilege.

If you specify any fields the response returned will be a WHOX response rather than a RFC 1459 WHO response.

Valid WHO Flags
---------------

The following flags use <pattern> to match against the specified user data:

A Show users who have an away message matching <pattern>.
a Show users who have an account name matching <pattern>.
h Show users who have a hostname matching <pattern>. If the 'x' modifier is specified then this will match against the real hostname instead of the display hostname.
i Show users who have an IP address matching <pattern>.
m Show users who have the modes listed in <pattern>. The pattern should be in the same format as a mode change e.g. +ow-i (server operators only).
n Show users who have a nickname matching <pattern>.
p Show users who are connected to a port in the <pattern> range (server operators only).
r Show users who have a real name matching <pattern>.
s Show users who are on a server with a name matching <pattern>. If the 'x' modifier is specified then this will match against the real server name instead of the masked server name.
t Show users who have connected in the last <pattern> seconds.
u Show users who have an ident (username) matching <pattern>.

The following flags filter users by their status:

f Only show users on remote (far) servers.
l Only show users on the local server.
o Only show server operators.

The following flags modify the command output:

x Show sensitive data like real user hostnames and, when hideserver is enabled, real server hostnames.

You may combine one flag from the first group and multiple from the others in one WHO command.

Valid WHO Fields
----------------

a Include the user's account name in the response.
c Include the first common channel name in the response.
d Include the user's server distance from you in the response.
f Include the user's away status, oper status, and highest channel prefix in the response.
h Include the user's hostname in the response. If the 'x' flag was specified then this is the real host rather than the display host.
i Include the user's IP address in the response.
l Include the user's idle time in the response.
n Include the user's nickname in the response.
o Include the user's channel operator rank level in the response.
r Include the user's real name in the response.
s Include the user's server name in the response. If the 'x' flag was specified then this is the real server name rather than the masked server name.
t Include the query type in the response.
u Include the user's ident in the response.

== WHOIS ==
/WHOIS [<servername>] <nick>[,<nick>]+

Returns the WHOIS information of a user, their channels, hostname, etc. If a servername is provided, then a whois is performed from the server where the user is actually located rather than locally, showing idle and signon times.

== WHOWAS ==
/WHOWAS <nick>

Returns a list of times the user was seen recently on IRC along with the time they were last seen and their server.

Nerds

2022-05-11T17:45:07Z

Rooot: Grammar

<center><H1> '''#nerds channel rules''' </H1></center>

'''Welcome to #nerds'''

'''nerds''' is pylinked to several different networks. Channel is randomly active at various times of the day. A good sense humor is highly recommended as a lot of people here enjoy the use of sarcasm. Just because you see us joking around, does NOT mean we wont help you the best we can.

<H2> Rules </H2>
* No Flooding. (A smaller ASCII image is okay but don't get excessive with it)
* No drones or bots. (We have enough bots)
* No discussion of hacking things. (Discussing security is okay, but if you sound like a kiddie or trying to do something kiddie, your visit is over)
* Pro pornography images. (We are a porn channel)
* No pedophilia of any kind. (Instant Ban)
* Don't abuse the channel's bots, or try to exploit them. (Only SORCERER can make exceptions to this, ops must follow this rule also)
* Don't ask for ops we have enough and don't need anymore.
* No bullying or race discrimination. (Jokes are okay, there is a difference between jokes and bullying. N-word is definitely not allowed.)
* Don't tell people to use google, actually help them or STFU.
* Leave the drama out of the channel. Don't bring other channel drama into #nerds.
* Do NOT PM/DM/message anyone without their permission. (Especially OPs aka the people in charge)