https://www.mixxnet.net/wiki/api.php?action=feedcontributions&user=MIXX941&feedformat=atomMIXXnet Wiki - User contributions [en]2024-03-29T02:00:39ZUser contributionsMediaWiki 1.24.1https://www.mixxnet.net/wiki/index.php?title=Main_Page&diff=5174Main Page2016-02-07T00:42:48Z<p>MIXX941: Reverted edits by LucasSimon9 (talk) to last revision by MIXX941</p>
<hr />
<div>Welcome to the MIXXnet Wiki. Here you will find user and staff contributed documents about [[MIXXnet]] and [[IRC]] in general. We encourage users to help out our documentation project by contributing information, however due to spam, editing can now only be done if you have registered and logged in.<br />
<br />
If you have any questions and need immediate help, log on to IRC: <br />
<br />
'''irc.mixxnet.net / #help'''<br />
<br />
You can use the search box to your left to search for articles that others have written or you can [[Special:Allpages|browse all articles]].<br />
<br />
== Getting Started ==<br />
Here are some articles that will help you get started on MIXXnet:<br />
<br />
* [[Channel_Start_Guide|Channel Start Guide - A complete guide to starting a channel]]<br />
* [[Channel_Modes|Channel Modes]]<br />
* [[User_Modes|User Modes]]<br />
* [[HostServ|vhost Information - Assign or remove a vhost on your nickname]]<br />
* [[SSL|SSL Information]]<br />
* [[IRC_client|Popular IRC Clients List]]<br />
* [[Proxy|Proxy policies and features]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=MediaWiki:Sitenotice&diff=5173MediaWiki:Sitenotice2016-02-07T00:40:35Z<p>MIXX941: Revert spam</p>
<hr />
<div></div>MIXX941https://www.mixxnet.net/wiki/index.php?title=User_talk:Plouks&diff=5168User talk:Plouks2012-04-02T22:34:54Z<p>MIXX941: Welcome!</p>
<hr />
<div>'''Welcome to ''MIXXnet Wiki''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [[Help:Contents|help pages]].<br />
Again, welcome and have fun! [[User:MIXX941|MIXX941]] 17:34, 2 April 2012 (CDT)</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRC_Client&diff=5167IRC Client2011-08-07T22:53:22Z<p>MIXX941: /* lightIRC */ Minor wording change</p>
<hr />
<div>An [[IRC]] Client is a software program used to connect to an [[IRC|Internet Relay Chat]] network, such as [[MIXXnet]]. Below is a list of popular IRC clients for various platforms.<br />
<br />
==Graphical Clients==<br />
===Cross-Platform===<br />
* '''XChat:''' Created by Peter Zelenzy, [[XChat]] is a free, open source, and multi-platform IRC client with a graphical user interface. There are builds for various *nix distributions, [http://xchataqua.sourceforge.net/ Mac OS X], and Windows. [http://www.xchat.org http://www.xchat.org] (Note: The "official" Windows builds are not free. To see a list of completely free Windows builds, go [http://b0at.tx0.org/xchat/ here]).<br />
<br />
* '''Quassel:''' Quassel is an open source and cross-platform distributed IRC client. Its unique feature is the ability to attach and detach the graphical client portion from the core, similar to running screen and a text based client. [http://quassel-irc.org/ http://quassel-irc.org]<br />
<br />
* '''KVIrc:''' KVIrc is another open source and cross-platform IRC client based on the QT toolkit. There are binaries available for Unix, OS X, and Windows. [http://www.kvirc.de/ http://www.kvirc.de]<br />
<br />
* '''Pidgin:''' Pidgin is an open source, cross-platform application that combines many chat networks (includng IRC) into one program. [http://pidgin.im/ http://pidgin.im]<br />
<br />
* '''Opera:''' The excellent Opera web browser also has a simple [http://www.opera.com/browser/tutorials/intro/using/chat/ built-in IRC client]. There are versions available for various platforms including Windows, Mac OS X, FreeBSD, Linux, and Solaris. [http://www.opera.com/ http://www.opera.com]<br />
<br />
===Mac OS X Specific===<br />
* '''Colloquy:''' Colloquy is a free and open source graphical client with a slick Mac-inspired interface for Mac OS X. [http://colloquy.info/ http://colloquy.info]<br />
<br />
* '''Snak (Shareware):''' Snak is an IRC client for Macintosh OS X. It has several features and is actively developed. Snak is shareware ($29). [http://www.snak.com/ http://www.snak.com]<br />
<br />
* '''Ircle (Shareware):''' Another IRC client for Mac. Ircle runs on Mac OS 7.2 through 9.0.x, as well as Mac OS X 10.1 or newer. Ircle is shareware (19 €). [http://www.ircle.com http://www.ircle.com]<br />
<br />
===Windows Specific===<br />
* '''mIRC (Shareware):''' Khaled Mardam-Bey released the first version of [[mIRC]] on February 28, 1995. mIRC is a graphical IRC client for the Windows platform with it's own scripting language. mIRC is shareware, so to legally run it past 30 days without nag screens you need a $20 license. [http://www.mirc.com http://www.mirc.com]<br />
<br />
==Text Clients==<br />
===Cross-Platform===<br />
* '''Irssi:''' Irssi is a popular open source and free text based IRC client. Irssi is different from BitchX because it does not use the old ircII code. Irssi also supports Perl scripting and runtime modules, so it is highly customizable. There are binaries available for several operating systems including Mac OSX and Windows. [http://www.irssi.org http://www.irssi.org]<br />
<br />
* '''WeeChat:''' WeeChat is an open source text based client with some advanced features like multiple interface capability, horizontal and vertical window splitting, nickname list, smart "hotlist" in the status bar to show channel activity by name, highlighting without switching channels, and spell checking. [http://weechat.flashtux.org/ http://weechat.flashtux.org]<br />
<br />
* '''BitchX:''' BitchX is another popular open source text based IRC client for UNIX. It started out as a script for the ircII client, but then panasync patched the script directly into the actual client in 1994. There are binaries for many operating systems including Windows. [http://www.bitchx.org http://www.bitchx.org]<br />
<br />
==Web-Based Clients==<br />
===Mibbit===<br />
Mibbit is a popular and feature rich AJAX client which allows users to easily connect to IRC from any web browser without plugins or special firewall requirements. Webmasters can create a [http://wiki.mibbit.com/index.php/Widget Mibbit Widget] to embed the chat application on their website. Please note that Mibbit is an externally hosted service so we have no control over its operation or reliability, though we do recommend it for its ease of use, good interface/features, and overall stability. [http://mibbit.com http://mibbit.com]<br />
<br />
MIXXnet fully supports connecting through Mibbit on all servers, and Mibbit users will have their real hostnames shown on the network. '''"irc.mixxnet.net"''' must be used in the "server" parameter to allow users' real hostnames to show up.<br />
<br />
===lightIRC===<br />
lightIRC is a freeware Flash IRC client with a clean and easy to use interface. Website admins can host the files on their own server or add an iframe to existing files on lightIRC's server. This client requires users to have the Adobe Flash plugin enabled in their browser which can limit compatibility as there is not official Flash support for all operating systems/browsers. [http://lightirc.com/ http://lightirc.com]<br />
<br />
<span style="color:#ff0000">'''Below are a few notes and recommendations for using lightIRC on MIXXnet:'''</span><br />
<br />
* All MIXXnet servers in the main rotation have support for lightIRC, however '''the "policyPort" parameter must be set to "6843"''' for the application to properly connect. (params.policyPort = 6843)<br />
<br />
* We recommend setting the "ident" parameter on lightIRC to the name of your channel as the default random string may cause users to be incorrectly identified as malicious bots. (params.ident = "yourchanname")<br />
<br />
* The "nickAlternate" parameter should be set to prevent lightIRC from rapidly reconnecting if the nickname is in use. (params.nickAlternate = "Guest_%")</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRC_Client&diff=5166IRC Client2011-08-07T22:52:02Z<p>MIXX941: /* lightIRC */ Update notes</p>
<hr />
<div>An [[IRC]] Client is a software program used to connect to an [[IRC|Internet Relay Chat]] network, such as [[MIXXnet]]. Below is a list of popular IRC clients for various platforms.<br />
<br />
==Graphical Clients==<br />
===Cross-Platform===<br />
* '''XChat:''' Created by Peter Zelenzy, [[XChat]] is a free, open source, and multi-platform IRC client with a graphical user interface. There are builds for various *nix distributions, [http://xchataqua.sourceforge.net/ Mac OS X], and Windows. [http://www.xchat.org http://www.xchat.org] (Note: The "official" Windows builds are not free. To see a list of completely free Windows builds, go [http://b0at.tx0.org/xchat/ here]).<br />
<br />
* '''Quassel:''' Quassel is an open source and cross-platform distributed IRC client. Its unique feature is the ability to attach and detach the graphical client portion from the core, similar to running screen and a text based client. [http://quassel-irc.org/ http://quassel-irc.org]<br />
<br />
* '''KVIrc:''' KVIrc is another open source and cross-platform IRC client based on the QT toolkit. There are binaries available for Unix, OS X, and Windows. [http://www.kvirc.de/ http://www.kvirc.de]<br />
<br />
* '''Pidgin:''' Pidgin is an open source, cross-platform application that combines many chat networks (includng IRC) into one program. [http://pidgin.im/ http://pidgin.im]<br />
<br />
* '''Opera:''' The excellent Opera web browser also has a simple [http://www.opera.com/browser/tutorials/intro/using/chat/ built-in IRC client]. There are versions available for various platforms including Windows, Mac OS X, FreeBSD, Linux, and Solaris. [http://www.opera.com/ http://www.opera.com]<br />
<br />
===Mac OS X Specific===<br />
* '''Colloquy:''' Colloquy is a free and open source graphical client with a slick Mac-inspired interface for Mac OS X. [http://colloquy.info/ http://colloquy.info]<br />
<br />
* '''Snak (Shareware):''' Snak is an IRC client for Macintosh OS X. It has several features and is actively developed. Snak is shareware ($29). [http://www.snak.com/ http://www.snak.com]<br />
<br />
* '''Ircle (Shareware):''' Another IRC client for Mac. Ircle runs on Mac OS 7.2 through 9.0.x, as well as Mac OS X 10.1 or newer. Ircle is shareware (19 €). [http://www.ircle.com http://www.ircle.com]<br />
<br />
===Windows Specific===<br />
* '''mIRC (Shareware):''' Khaled Mardam-Bey released the first version of [[mIRC]] on February 28, 1995. mIRC is a graphical IRC client for the Windows platform with it's own scripting language. mIRC is shareware, so to legally run it past 30 days without nag screens you need a $20 license. [http://www.mirc.com http://www.mirc.com]<br />
<br />
==Text Clients==<br />
===Cross-Platform===<br />
* '''Irssi:''' Irssi is a popular open source and free text based IRC client. Irssi is different from BitchX because it does not use the old ircII code. Irssi also supports Perl scripting and runtime modules, so it is highly customizable. There are binaries available for several operating systems including Mac OSX and Windows. [http://www.irssi.org http://www.irssi.org]<br />
<br />
* '''WeeChat:''' WeeChat is an open source text based client with some advanced features like multiple interface capability, horizontal and vertical window splitting, nickname list, smart "hotlist" in the status bar to show channel activity by name, highlighting without switching channels, and spell checking. [http://weechat.flashtux.org/ http://weechat.flashtux.org]<br />
<br />
* '''BitchX:''' BitchX is another popular open source text based IRC client for UNIX. It started out as a script for the ircII client, but then panasync patched the script directly into the actual client in 1994. There are binaries for many operating systems including Windows. [http://www.bitchx.org http://www.bitchx.org]<br />
<br />
==Web-Based Clients==<br />
===Mibbit===<br />
Mibbit is a popular and feature rich AJAX client which allows users to easily connect to IRC from any web browser without plugins or special firewall requirements. Webmasters can create a [http://wiki.mibbit.com/index.php/Widget Mibbit Widget] to embed the chat application on their website. Please note that Mibbit is an externally hosted service so we have no control over its operation or reliability, though we do recommend it for its ease of use, good interface/features, and overall stability. [http://mibbit.com http://mibbit.com]<br />
<br />
MIXXnet fully supports connecting through Mibbit on all servers, and Mibbit users will have their real hostnames shown on the network. '''"irc.mixxnet.net"''' must be used in the "server" parameter to allow users' real hostnames to show up.<br />
<br />
===lightIRC===<br />
lightIRC is a freeware Flash IRC client with a clean and easy to use interface. Website admins can host the files on their own server or add an iframe to existing files on lightIRC's server. This client requires users to have the Adobe Flash plugin enabled in their browser which can limit compatibility as there is not official Flash support for all operating systems/browsers. [http://lightirc.com/ http://lightirc.com]<br />
<br />
<span style="color:#ff0000">'''Below are a few notes and recommendations on how to use lightIRC on MIXXnet:'''</span><br />
<br />
* All MIXXnet servers in the main rotation have support for lightIRC, however '''the "policyPort" parameter must be set to "6843"''' for the application to properly connect. (params.policyPort = 6843)<br />
<br />
* We recommend setting the "ident" parameter on lightIRC to the name of your channel as the default random string may cause users to be incorrectly identified as malicious bots. (params.ident = "yourchanname")<br />
<br />
* The "nickAlternate" parameter should be set to prevent lightIRC from rapidly reconnecting if the nickname is in use. (params.nickAlternate = "Guest_%")</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Services_1.9&diff=5165Services 1.92011-06-29T04:40:50Z<p>MIXX941: /* New Features */ Add NickServ AJOIN</p>
<hr />
<div>This article will outline new features and changes in MIXXnet's services software throughout the 1.9 series. Version 1.9 of services is under active development, so please contact us in #help with any issues or feature requests and we will send them upstream to the developers.<br />
<br />
==2011-06-28 (1.9.4+)==<br />
===New Features===<br />
* ChanServ is now able to join channels directly instead of under different BotServ monikers. To assign ChanServ to your channel: "/msg botserv assign #channel ChanServ"<br />
* Server-side channel autojoining after identifying to services. This ensures vhosts are always set before joining channels and is also a central channel autojoin list. "/msg nickserv help ajoin" for more info.<br />
* NickServ can use client certificates for authentication. "/msg nickserv help cert" for more info.<br />
* Users can now reset their own passwords instead of asking staff. "/msg nickserv help resetpass" for more info.<br />
* ChanServ CLONE command to clone settings from one channel to another. "/msg chanserv help clone" for more info.<br />
* Users can remove their own access in channels.<br />
<br />
===Changes===<br />
* To prevent bots from registering, new users need to confirm their nick registrations via email. You will be given instructions upon registration.<br />
* The syntax to register a channel has changed and no longer requires a password. "/msg chanserv register #channel description"<br />
* Generic vhosts are now handled by HostServ instead of the old HostBot system. To assign a vhost to your nick: "/msg hostserv generic assign"<br />
* ChanServ MLOCK has been moved to ChanServ MODE, along with the ability to manually set modes through ChanServ. "/msg chanserv help mode" for more info.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=ChanServ&diff=5164ChanServ2011-06-29T03:31:31Z<p>MIXX941: /* REGISTER */ Update for 1.9</p>
<hr />
<div>ChanServ is a MIXXnet [[Services|service]] that allows you to register a [[channel]]. Registering your channel provides an easy way to manage [[operator|ops]] and prevent channel takeovers.<br />
<br />
For a guide on how to set up your channel using ChanServ, visit the [[Channel Start Guide]]<br />
<br />
==ChanServ Tips and Notes==<br />
===Automatic Expiration===<br />
Channels that have not been used in 180 days (when no user on the channel's access list has entered) will automatically expire and be available for other users to register.<br />
<br />
If the channel founder's nickname expires due to inactivity, the channel will also expire if no [[#SET SUCCESSOR|successor]] is set.<br />
<br />
===xOP vs Access Systems===<br />
xOP is the default access scheme for channels. Access is controlled by predefined levels known as [[#SOP]], [[#AOP]], [[#HOP]], and [[#VOP]]. If you wish to use the [[#ACCESS|access system]] instead, you must first disable the xOP system:<br />
<br />
/msg chanserv set #channel xop off<br />
<br />
===Autovoice For All Users===<br />
To get ChanServ to automatically voice everyone in your channel upon joining, do the following: <br />
<br />
/msg chanserv set #channel xop off<br />
/msg chanserv set #channel secure off<br />
/msg chanserv levels #channel set autovoice 0<br />
<br />
==ChanServ Commands==<br />
===HELP===<br />
<br />
ChanServ allows you to register and control various<br />
aspects of channels. ChanServ can often prevent<br />
malicious users from "taking over" channels by limiting<br />
who is allowed channel operator priviliges. Available<br />
commands are listed below; to use them, type<br />
/msg ChanServ command. For more information on a<br />
specific command, type /msg ChanServ HELP command.<br />
<br />
REGISTER Register a channel<br />
IDENTIFY Identify yourself with your password<br />
SET Set channel options and information<br />
AOP Modify the list of AOP users<br />
SOP Modify the list of SOP users<br />
ACCESS Modify the list of privileged users<br />
LEVELS Redefine the meanings of access levels<br />
AKICK Maintain the AutoKick list<br />
DROP Cancel the registration of a channel<br />
SENDPASS Help retrive lost passwords<br />
<br />
Other commands: BAN, CLEAR, DEOP, DEVOICE, GETKEY, INFO,<br />
INVITE, KICK, LIST, LOGOUT, OP, TOPIC,<br />
UNBAN, VOICE, VOP<br />
<br />
<br />
===REGISTER===<br />
<br />
Syntax: /msg ChanServ REGISTER channel description<br />
<br />
Registers a channel in the ChanServ database. In order<br />
to use this command, you must first be a channel operator<br />
on the channel you're trying to register. The last parameter, which must be included, is a general description of the channel's purpose.<br />
<br />
When you register a channel, you are recorded as the<br />
" founder" of the channel. The channel founder is allowed<br />
to change all of the channel settings for the channel;<br />
ChanServ will also automatically give the founder<br />
channel-operator privileges when s/he enters the channel.<br />
See the ACCESS command (/msg ChanServ HELP ACCESS) for<br />
information on giving a subset of these privileges to<br />
other channel users.<br />
<br />
NOTICE: In order to register a channel, you must have<br />
first registered your nickname. If you haven't,<br />
/msg ChanServ HELP for information on how to do so.<br />
<br />
===IDENTIFY===<br />
<br />
Syntax: /msg ChanServ IDENTIFY channel password<br />
<br />
Authenticates you to ChanServ as the founder of the given<br />
channel. Many commands require you to use this command<br />
before using them. The password should be the same one<br />
you sent with the REGISTER command.<br />
<br />
===LOGOUT===<br />
<br />
Syntax: /msg ChanServ LOGOUT channel nickname<br />
<br />
This command makes the selected nickname not identified<br />
anymore for the given channel.<br />
<br />
If you are the founder of the channel, you can log out anybody,<br />
else you can only log out yourself.<br />
<br />
<br />
===DROP===<br />
<br />
Syntax: /msg ChanServ DROP channel<br />
<br />
Unregisters the named channel. Can only be used by<br />
channel founder, who must use the IDENTIFY command first.<br />
<br />
<br />
===SET===<br />
<br />
Syntax: /msg ChanServ SET channel option parameters<br />
<br />
Allows the channel founder to set various channel options<br />
and other information.<br />
<br />
Available options:<br />
<br />
FOUNDER Set the founder of a channel<br />
SUCCESSOR Set the successor for a channel<br />
PASSWORD Set the founder password<br />
DESC Set the channel description<br />
URL Associate a URL with the channel<br />
EMAIL Associate an E-mail address with the channel<br />
ENTRYMSG Set a message to be sent to users when they<br />
enter the channel<br />
BANTYPE Set how Services make bans on the channel<br />
MLOCK Lock channel modes on or off<br />
KEEPTOPIC Retain topic when channel is not in use<br />
OPNOTICE Send a notice when OP/DEOP commands are used<br />
PEACE Regulate the use of critical commands<br />
PRIVATE Hide channel from LIST command<br />
RESTRICTED Restrict access to the channel<br />
SECURE Activate ChanServ security features<br />
SECUREOPS Stricter control of chanop status<br />
SECUREFOUNDER Stricter control of channel founder status<br />
SIGNKICK Sign kicks that are done with KICK command<br />
TOPICLOCK Topic can only be changed with TOPIC<br />
XOP Toggle the user privilege system<br />
<br />
Type /msg ChanServ HELP option for more information on a<br />
particular option.<br />
<br />
<br />
====SET FOUNDER====<br />
<br />
Syntax: /msg ChanServ SET channel FOUNDER nick<br />
<br />
Changes the founder of a channel. The new nickname must<br />
be a registered one.<br />
<br />
====SET SUCCESSOR====<br />
<br />
Syntax: /msg ChanServ SET channel SUCCESSOR nick<br />
<br />
Changes the successor of a channel. If the founder's<br />
nickname expires or is dropped while the channel is still<br />
registered, the successor will become the new founder of the<br />
channel. However, if the successor already has too many<br />
channels registered (<num>), the channel will be dropped<br />
instead, just as if no successor had been set. The new<br />
nickname must be a registered one.<br />
<br />
<br />
====SET PASSWORD====<br />
<br />
Syntax: /msg ChanServ SET channel PASSWORD password<br />
<br />
Sets the password used to identify as the founder of the<br />
channel.<br />
<br />
<br />
====SET DESC====<br />
<br />
Syntax: /msg ChanServ SET channel DESC description<br />
<br />
Sets the description for the channel, which shows up with<br />
the LIST and INFO commands.<br />
<br />
<br />
====SET URL====<br />
<br />
Syntax: /msg ChanServ SET channel URL [url]<br />
<br />
Associates the given URL with the channel. This URL will<br />
be displayed whenever someone requests information on the<br />
channel with the INFO command. If no parameter is given,<br />
deletes any current URL for the channel.<br />
<br />
<br />
====SET EMAIL====<br />
<br />
Syntax: /msg ChanServ SET channel EMAIL [address]<br />
<br />
Associates the given E-mail address with the channel.<br />
This address will be displayed whenever someone requests<br />
information on the channel with the INFO command. If no<br />
parameter is given, deletes any current E-mail address for<br />
the channel.<br />
<br />
<br />
====SET ENTRYMSG====<br />
<br />
Syntax: /msg ChanServ SET channel ENTRYMSG [message]<br />
<br />
Sets the message which will be sent via /notice to users<br />
when they enter the channel. If no parameter is given,<br />
causes no message to be sent upon entering the channel.<br />
<br />
<br />
====SET BANTYPE====<br />
<br />
Syntax: /msg ChanServ SET channel BANTYPE bantype<br />
<br />
Sets the ban type that will be used by services whenever<br />
they need to ban someone from your channel.<br />
<br />
bantype is a number between 0 and 3 that means:<br />
<br />
0: ban in the form *!user@host<br />
1: ban in the form *!*user@host<br />
2: ban in the form *!*@host<br />
3: ban in the form *!*user@*.domain<br />
<br />
<br />
====SET KEEPTOPIC====<br />
<br />
Syntax: /msg ChanServ SET channel KEEPTOPIC {ON | OFF}<br />
<br />
Enables or disables the topic retention option for a<br />
channel. When topic retention is set, the topic for the<br />
channel will be remembered by ChanServ even after the<br />
last user leaves the channel, and will be restored the<br />
next time the channel is created.<br />
<br />
<br />
====SET TOPICLOCK====<br />
<br />
Syntax: /msg ChanServ SET channel TOPICLOCK {ON | OFF}<br />
<br />
Enables or disables the topic lock option for a channel.<br />
When topic lock is set, ChanServ will not allow the<br />
channel topic to be changed except via the TOPIC<br />
command.<br />
<br />
<br />
====SET MLOCK====<br />
<br />
Syntax: /msg ChanServ SET channel MLOCK modes<br />
<br />
Sets the mode-lock parameter for the channel. ChanServ<br />
allows you to define certain channel modes to be always<br />
on, off or free to be either on or off.<br />
<br />
The modes parameter is constructed exactly the same way<br />
as a /MODE command; that is, modes followed by a + are<br />
locked on, and modes followed by a - are locked off. Note,<br />
however, that unlike the /MODE command, each use of<br />
SET MLOCK will remove all modes previously locked before<br />
setting the new!<br />
<br />
Warning: If you set a mode-locked key, as in the second<br />
example below, you should also set the RESTRICTED option for<br />
the channel (see HELP SET RESTRICTED), or anyone entering<br />
the channel when it is empty will be able to see the key!<br />
<br />
Examples:<br />
<br />
SET #channel MLOCK +nt-iklps<br />
Forces modes n and t on, and modes i, k, l, p, and<br />
s off. Mode m is left free to be either on or off.<br />
<br />
SET #channel MLOCK +knst-ilmp my-key<br />
Forces modes k, n, s, and t on, and modes i, l, m,<br />
and p off. Also forces the channel key to be<br />
" my-key".<br />
<br />
SET #channel MLOCK +<br />
Removes the mode lock; all channel modes are free<br />
to be either on or off.<br />
<br />
<br />
====SET PEACE====<br />
<br />
Syntax: /msg ChanServ SET channel PEACE {ON | OFF}<br />
<br />
Enables or disables the peace option for a channel.<br />
When peace is set, an user won't be able to kick,<br />
ban or remove a channel status of an user that has<br />
a level superior or equal to his via ChanServ commands.<br />
<br />
<br />
====SET PRIVATE====<br />
<br />
Syntax: /msg ChanServ SET channel PRIVATE {ON | OFF}<br />
<br />
Enables or disables the private option for a channel.<br />
When private is set, a /msg ChanServ LIST will not<br />
include the channel in any lists.<br />
<br />
<br />
====SET RESTRICTED====<br />
<br />
Syntax: /msg ChanServ SET channel RESTRICTED {ON | OFF}<br />
<br />
Enables or disables the restricted access option for a<br />
channel. When restricted access is set, users who would<br />
normally be disallowed from having channel operator<br />
privileges (users with negative access levels and, if<br />
secure ops is set, users not on the access list) will<br />
instead be kicked and banned from the channel.<br />
<br />
<br />
====SET SECURE====<br />
<br />
Syntax: /msg ChanServ SET channel SECURE {ON | OFF}<br />
<br />
Enables or disables ChanServ's security features for a<br />
channel. When SECURE is set, only users who have<br />
registered their nicknames with ChanServ and IDENTIFY'd<br />
with their password will be given access to the channel<br />
as controlled by the access list.<br />
<br />
<br />
====SET SECUREOPS====<br />
<br />
Syntax: /msg ChanServ SET channel SECUREOPS {ON | OFF}<br />
<br />
Enables or disables the secure ops option for a channel.<br />
When secure ops is set, users who are not on the userlist<br />
will not be allowed chanop status.<br />
<br />
====SET SECUREFOUNDER====<br />
<br />
Syntax: /msg ChanServ SET channel SECUREFOUNDER {ON | OFF}<br />
<br />
Enables or disables the secure founder option for a channel.<br />
When secure founder is set, only the real founder will be<br />
able to drop the channel, change its password, its founder and its<br />
successor, and not those who are IDENTIFY'd with ChanServ.<br />
<br />
====SET SIGNKICK====<br />
<br />
Syntax: /msg ChanServ SET channel SIGNKICK {ON | LEVEL | OFF}<br />
<br />
Enables or disables signed kicks for a<br />
channel. When SIGNKICK is set, kicks issued with<br />
ChanServ KICK command will have the nick that used the<br />
command in their reason.<br />
<br />
If you use LEVEL, those who have a level that is superior<br />
or equal to the SIGNKICK level on the channel won't have their<br />
kicks signed. See /msg ChanServ HELP LEVELS for more information.<br />
<br />
<br />
====SET XOP====<br />
<br />
Syntax: /msg ChanServ SET channel XOP {ON | OFF}<br />
<br />
Enables or disables the xOP lists system for a channel.<br />
When XOP is set, you have to use the AOP/SOP/VOP<br />
commands in order to give channel privileges to<br />
users, else you have to use the ACCESS command.<br />
<br />
Technical Note: when you switch from access list to xOP<br />
lists system, your level definitions and user levels will be<br />
changed, so you won't find the same values if you<br />
switch back to access system!<br />
<br />
You should also check that your users are in the good xOP<br />
list after the switch from access to xOP lists, because the<br />
guess is not always perfect... in fact, it is not recommended<br />
to use the xOP lists if you changed level definitions with<br />
the LEVELS command.<br />
<br />
Switching from xOP lists system to access list system<br />
causes no problem though.<br />
<br />
<br />
====SET OPNOTICE====<br />
<br />
Syntax: /msg ChanServ SET channel OPNOTICE {ON | OFF}<br />
<br />
Enables or disables the op-notice option for a channel.<br />
When op-notice is set, ChanServ will send a notice to the<br />
channel whenever the OP or DEOP commands are used for a user<br />
in the channel.<br />
<br />
<br />
===AOP===<br />
<br />
Syntax: /msg ChanServ AOP channel ADD nick<br />
AOP channel DEL {nick | entry-num | list}<br />
AOP channel LIST [mask | list]<br />
AOP channel CLEAR<br />
<br />
Maintains the AOP (AutoOP) list for a channel. The AOP<br />
list gives users the right to be auto-opped on your channel,<br />
to unban or invite themselves if needed, to have their<br />
greet message showed on join, and so on.<br />
<br />
The AOP ADD command adds the given nickname to the<br />
AOP list.<br />
<br />
The AOP DEL command removes the given nick from the<br />
AOP list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The AOP LIST command displays the AOP list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
AOP #channel LIST 2-5,7-9<br />
Lists AOP entries numbered 2 through 5 and<br />
7 through 9.<br />
<br />
The AOP CLEAR command clears all entries of the<br />
AOP list.<br />
<br />
The AOP ADD and AOP DEL commands are limited to<br />
<br />
SOPs or above, while the AOP CLEAR command can only<br />
be used by the channel founder. However, any user on the<br />
AOP list may use the AOP LIST command.<br />
<br />
This command may have been disabled for your channel, and<br />
in that case you need to use the access list. See<br />
/msg ChanServ HELP ACCESS for information about the access list,<br />
and /msg ChanServ HELP SET XOP to know how to toggle between<br />
the access list and xOP list systems.<br />
<br />
<br />
===HOP===<br />
<br />
Syntax: /msg ChanServ HOP channel ADD nick<br />
HOP channel DEL {nick | entry-num | list}<br />
HOP channel LIST [mask | list]<br />
HOP channel CLEAR<br />
<br />
Maintains the HOP (HalfOP) list for a channel. The HOP<br />
list gives users the right to be auto-halfopped on your<br />
channel.<br />
<br />
The HOP ADD command adds the given nickname to the<br />
HOP list.<br />
<br />
The HOP DEL command removes the given nick from the<br />
HOP list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The HOP LIST command displays the HOP list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
HOP #channel LIST 2-5,7-9<br />
Lists HOP entries numbered 2 through 5 and<br />
7 through 9.<br />
<br />
The HOP CLEAR command clears all entries of the<br />
HOP list.<br />
<br />
The HOP ADD, HOP DEL and HOP LIST commands are<br />
limited to AOPs or above, while the HOP CLEAR command can only be used by the channel founder.<br />
<br />
This command may have been disabled for your channel, and<br />
in that case you need to use the access list. See<br />
/msg ChanServ HELP ACCESS for information about the access list,<br />
and /msg ChanServ HELP SET XOP to know how to toggle between<br />
the access list and xOP list systems.<br />
<br />
<br />
===SOP===<br />
<br />
Syntax: /msg ChanServ SOP channel ADD nick<br />
SOP channel DEL {nick | entry-num | list}<br />
SOP channel LIST [mask | list]<br />
SOP channel CLEAR<br />
<br />
Maintains the SOP (SuperOP) list for a channel. The SOP<br />
list gives users all rights given by the AOP list, and adds<br />
those needed to use the AutoKick and the BadWords lists,<br />
to send and read channel memos, and so on.<br />
<br />
The SOP ADD command adds the given nickname to the<br />
SOP list.<br />
<br />
The SOP DEL command removes the given nick from the<br />
SOP list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The SOP LIST command displays the SOP list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
SOP #channel LIST 2-5,7-9<br />
Lists AOP entries numbered 2 through 5 and<br />
7 through 9.<br />
<br />
The SOP CLEAR command clears all entries of the<br />
SOP list.<br />
<br />
The SOP ADD, SOP DEL and SOP CLEAR commands are<br />
limited to the channel founder. However, any user on the<br />
AOP list may use the SOP LIST command.<br />
<br />
<br />
This command may have been disabled for your channel, and<br />
in that case you need to use the access list. See<br />
/msg ChanServ HELP ACCESS for information about the access list,<br />
and /msg ChanServ HELP SET XOP to know how to toggle between<br />
the access list and xOP list systems.<br />
<br />
<br />
===VOP===<br />
<br />
Syntax: /msg ChanServ VOP channel ADD nick<br />
VOP channel DEL {nick | entry-num | list}<br />
VOP channel LIST [mask | list]<br />
VOP channel CLEAR<br />
<br />
Maintains the VOP (VOicePeople) list for a channel.<br />
The VOP list allows users to be auto-voiced and to voice<br />
themselves if they aren't.<br />
<br />
The VOP ADD command adds the given nickname to the<br />
VOP list.<br />
<br />
The VOP DEL command removes the given nick from the<br />
VOP list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The VOP LIST command displays the VOP list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
VOP #channel LIST 2-5,7-9<br />
Lists VOP entries numbered 2 through 5 and 7 through 9.<br />
<br />
The VOP CLEAR command clears all entries of the<br />
VOP list.<br />
<br />
The VOP ADD, VOP DEL and VOP LIST commands are<br />
limited to AOPs or above, while the VOP CLEAR command<br />
can only be used by the channel founder.<br />
<br />
This command may have been disabled for your channel, and in that case you need to use the access list. See<br />
/msg ChanServ HELP ACCESS for information about the access list,<br />
and /msg ChanServ HELP SET XOP to know how to toggle between<br />
the access list and xOP list systems.<br />
<br />
<br />
===ACCESS===<br />
<br />
Syntax: /msg ChanServ ACCESS channel ADD nick level<br />
ACCESS channel DEL {nick | entry-num | list}<br />
ACCESS channel LIST [mask | list]<br />
ACCESS channel CLEAR<br />
<br />
Maintains the access list for a channel. The access<br />
list specifies which users are allowed chanop status or<br />
access to ChanServ commands on the channel. Different<br />
user levels allow for access to different subsets of<br />
privileges; /msg ChanServ HELP ACCESS LEVELS for more<br />
specific information. Any nick not on the access list has<br />
a user level of 0.<br />
<br />
The ACCESS ADD command adds the given nickname to the<br />
access list with the given user level; if the nick is<br />
already present on the list, its access level is changed to<br />
the level specified in the command. The level specified<br />
must be less than that of the user giving the command, and<br />
if the nick is already on the access list, the current<br />
access level of that nick must be less than the access level<br />
of the user giving the command.<br />
<br />
The ACCESS DEL command removes the given nick from the<br />
access list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The ACCESS LIST command displays the access list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
ACCESS #channel LIST 2-5,7-9<br />
Lists access entries numbered 2 through 5 and<br />
7 through 9.<br />
<br />
The ACCESS CLEAR command clears all entries of the<br />
access list.<br />
<br />
<br />
====ACCESS LEVELS====<br />
<br />
User access levels<br />
<br />
By default, the following access levels are defined:<br />
<br />
Founder Full access to ChanServ functions; automatic<br />
opping upon entering channel. Note<br />
that only one person may have founder<br />
status (it cannot be given using the<br />
ACCESS command).<br />
10 Access to AKICK command; automatic opping.<br />
5 Automatic opping.<br />
3 Automatic voicing.<br />
0 No special privileges; can be opped by other<br />
ops (unless secure-ops is set).<br />
< 0 May not be opped.<br />
<br />
These levels may be changed, or new ones added, using the<br />
LEVELS command; type /msg ChanServ HELP LEVELS for<br />
information.<br />
<br />
===AKICK===<br />
<br />
Syntax: /msg ChanServ AKICK channel ADD mask [reason]<br />
AKICK channel STICK mask<br />
AKICK channel UNSTICK mask<br />
AKICK channel DEL mask<br />
AKICK channel LIST [mask]<br />
AKICK channel VIEW [mask]<br />
AKICK channel ENFORCE<br />
AKICK channel CLEAR<br />
<br />
Maintains the AutoKick list for a channel. If a user<br />
on the AutoKick list attempts to join the channel,<br />
ChanServ will ban that user from the channel, then kick<br />
the user.<br />
<br />
The AKICK ADD command adds the given nick or usermask<br />
to the AutoKick list. If a reason is given with<br />
the command, that reason will be used when the user is<br />
kicked; if not, the default reason is "You have been<br />
banned from the channel".<br />
<br />
The AKICK STICK command permanently bans the given mask<br />
on the channel. If someone tries to remove the ban, ChanServ<br />
will automatically set it again. You can't use it for<br />
registered nicks.<br />
<br />
The AKICK UNSTICK command cancels the effect of the<br />
AKICK STICK command, so you'll be able to unset the<br />
ban again on the channel.<br />
<br />
The AKICK DEL command removes the given nick or mask<br />
from the AutoKick list. It does not, however, remove any<br />
bans placed by an AutoKick; those must be removed<br />
manually.<br />
<br />
The AKICK LIST command displays the AutoKick list, or<br />
optionally only those AutoKick entries which match the<br />
given mask.<br />
<br />
The AKICK VIEW command is a more verbose version of<br />
AKICK LIST command.<br />
<br />
The AKICK ENFORCE command causes ChanServ to enforce the<br />
current AKICK list by removing those users who match an<br />
AKICK mask.<br />
<br />
The AKICK CLEAR command clears all entries of the<br />
akick list.<br />
<br />
<br />
===LEVELS===<br />
<br />
Syntax: /msg ChanServ LEVELS channel SET type level<br />
LEVELS channel {DIS | DISABLE} type<br />
LEVELS channel LIST<br />
LEVELS channel RESET<br />
<br />
The LEVELS command allows fine control over the meaning of<br />
the numeric access levels used for channels. With this<br />
command, you can define the access level required for most<br />
of ChanServ's functions. (The SET FOUNDER and SET PASSWORD<br />
commands, as well as this command, are always restricted to<br />
the channel founder.)<br />
<br />
LEVELS SET allows the access level for a function or group of<br />
functions to be changed. LEVELS DISABLE (or DIS for short)<br />
disables an automatic feature or disallows access to a<br />
function by anyone other than the channel founder.<br />
LEVELS LIST shows the current levels for each function or<br />
group of functions. LEVELS RESET resets the levels to the<br />
default levels of a newly-created channel (see<br />
HELP ACCESS LEVELS).<br />
<br />
For a list of the features and functions whose levels can be<br />
set, see HELP LEVELS DESC.<br />
<br />
<br />
===INFO===<br />
<br />
Syntax: /msg ChanServ INFO channel [ALL]<br />
<br />
Lists information about the named registered channel,<br />
including its founder, time of registration, last time<br />
used, description, and mode lock, if any. If ALL is<br />
specified, the entry message and successor will also<br />
be displayed.<br />
<br />
By default, the ALL option is limited to those with<br />
founder access on the channel.<br />
<br />
<br />
===LIST===<br />
<br />
Syntax: /msg ChanServ LIST pattern<br />
<br />
Lists all registered channels matching the given pattern.<br />
(Channels with the PRIVATE option set are not listed.)<br />
<br />
<br />
===OP===<br />
<br />
Syntax: /msg ChanServ OP [#channel [nick]]<br />
<br />
Ops a selected nick on a channel. If nick is not given,<br />
it will op you. If channel and nick are not given,<br />
it will op you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel.<br />
<br />
<br />
===DEOP===<br />
<br />
Syntax: /msg ChanServ DEOP [#channel [nick]]<br />
<br />
Deops a selected nick on a channel. If nick is not given,<br />
it will deop you. If channel and nick are not given,<br />
it will deop you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel.<br />
<br />
===VOICE===<br />
<br />
Syntax: /msg ChanServ VOICE [#channel [nick]]<br />
<br />
Voices a selected nick on a channel. If nick is not given,<br />
it will voice you. If channel and nick are not given,<br />
it will voice you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel, or to VOPs or those with level 3<br />
and above for self voicing.<br />
<br />
<br />
===DEVOICE===<br />
<br />
Syntax: /msg ChanServ DEVOICE [#channel [nick]]<br />
<br />
Devoices a selected nick on a channel. If nick is not given,<br />
it will devoice you. If channel and nick are not given,<br />
it will devoice you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel, or to VOPs or those with level 3<br />
and above for self devoicing.<br />
<br />
===HALFOP===<br />
<br />
Syntax: /msg ChanServ HALFOP [#channel [nick]]<br />
<br />
Halfops a selected nick on a channel. If nick is not given,<br />
it will halfop you. If channel and nick are not given,<br />
it will halfop you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs and those with level 5 access<br />
and above on the channel, or to HOPs or those with level 4<br />
and above for self halfopping.<br />
<br />
<br />
===DEHALFOP===<br />
<br />
Syntax: /msg ChanServ DEHALFOP [#channel [nick]]<br />
<br />
Dehalfops a selected nick on a channel. If nick is not given,<br />
it will dehalfop you. If channel and nick are not given,<br />
it will dehalfop you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs and those with level 5 access<br />
and above on the channel, or to HOPs or those with level 4<br />
and above for self dehalfopping.<br />
<br />
===PROTECT===<br />
<br />
Syntax: /msg ChanServ PROTECT [#channel [nick]]<br />
<br />
Protects a selected nick on a channel. If nick is not given,<br />
it will protect you. If channel and nick are not given,<br />
it will protect you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to the founder, or to SOPs or those with<br />
level 10 and above on the channel for self protecting.<br />
<br />
<br />
===DEPROTECT===<br />
<br />
Syntax: /msg ChanServ DEPROTECT [#channel [nick]]<br />
<br />
Deprotects a selected nick on a channel. If nick is not given,<br />
it will deprotect you. If channel and nick are not given,<br />
it will deprotect you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to the founder, or to SOPs or those with<br />
level 10 and above on the channel for self deprotecting.<br />
<br />
<br />
===OWNER===<br />
<br />
Syntax: /msg ChanServ OWNER [#channel]<br />
<br />
Gives you owner status on channel. If channel is not<br />
given, it will give you owner status on all channels you're<br />
on, provided you have the rights to.<br />
<br />
Limited to those with founder access on the channel.<br />
<br />
<br />
===DEOWNER===<br />
<br />
Syntax: /msg ChanServ DEOWNER [#channel]<br />
<br />
Removes your owner status on channel. If channel is<br />
not given, it will remove your owner status on all channels<br />
you're on, provided you have the rights to.<br />
<br />
Limited to those with founder access on the channel.<br />
<br />
<br />
===INVITE===<br />
<br />
Syntax: /msg ChanServ INVITE channel<br />
<br />
Tells ChanServ to invite you into the given channel.<br />
<br />
By default, limited to AOPs or those with level 5 and above<br />
on the channel.<br />
<br />
<br />
===UNBAN===<br />
<br />
Syntax: /msg ChanServ UNBAN channel<br />
<br />
Tells ChanServ to remove all bans preventing you from<br />
entering the given channel.<br />
<br />
By default, limited to AOPs or those with level 5 and above<br />
on the channel.<br />
<br />
===KICK===<br />
<br />
Syntax: /msg ChanServ KICK [#channel [nick [reason]]]<br />
<br />
Kicks a selected nick on a channel. If nick is not given,<br />
it will kick you. If channel and nick are not given,<br />
it will kick you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel.<br />
<br />
<br />
===BAN===<br />
<br />
Syntax: /msg ChanServ BAN [#channel [nick [reason]]]<br />
<br />
Bans a selected nick on a channel. If nick is not given,<br />
it will ban you. If channel and nick are not given,<br />
it will ban you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel.<br />
<br />
<br />
===TOPIC===<br />
<br />
Syntax: /msg ChanServ TOPIC channel [topic]<br />
<br />
Causes ChanServ to set the channel topic to the one<br />
specified. If topic is not given, then an empty topic<br />
is set. This command is most useful in conjunction<br />
with SET TOPICLOCK. See /msg ChanServ HELP SET TOPICLOCK<br />
for more information.<br />
<br />
By default, limited to those with founder access on the<br />
channel.<br />
<br />
<br />
===CLEAR===<br />
<br />
Syntax: /msg ChanServ CLEAR channel what<br />
<br />
Tells ChanServ to clear certain settings on a channel. what<br />
can be any of the following:<br />
<br />
MODES Resets all modes on the channel (i.e. clears<br />
modes i,k,l,m,n,p,s,t).<br />
BANS Clears all bans on the channel.<br />
EXCEPTS Clears all excepts on the channel.<br />
OPS Removes channel-operator status (mode +o) from<br />
all channel operators.<br />
VOICES Removes "voice" status (mode +v) from anyone<br />
with that mode set.<br />
USERS Removes (kicks) all users from the channel.<br />
<br />
By default, limited to those with founder access on the<br />
channel.<br />
<br />
===GETKEY===<br />
<br />
Syntax: /msg ChanServ GETKEY channel<br />
<br />
Returns the key of the given channel. This is a command<br />
mainly intended to be used by bots and/or scripts, so<br />
the output is in the following way:<br />
<br />
KEY <channel> <key><br />
<br />
key is "NO KEY" if no key is set.<br />
<br />
[[Category:Anope]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=HostServ&diff=5163HostServ2011-06-29T03:30:16Z<p>MIXX941: Update for HS GENERIC</p>
<hr />
<div>'''HostServ''' is a MIXXnet [[Services|service]] that gives users a generic vhost to hide their real IP address/hostname. The generic free vhost is in the form of: "registerednick.users.mixxnet.net". We do not currently provide custom vhosts except in very special cases.<br />
<br />
<br />
'''To activate your generic vhost: /msg hostserv generic assign'''<br />
<br />
<br />
<br />
==HostServ Commands==<br />
===ON===<br />
<br />
Syntax: /msg HostServ ON<br />
<br />
Activates the vhost currently assigned to the nick in use.<br />
When you use this command, any user who performs a /whois<br />
on you will see the vhost instead of your real IP address.<br />
<br />
===OFF===<br />
<br />
Syntax: /msg HostServ OFF<br />
<br />
Deactivates the vhost currently assigned to the nick in use.<br />
When you use this command any user who performs a /whois<br />
on you will see your real IP address.<br />
<br />
===GROUP===<br />
<br />
Syntax: /msg HostServ GROUP<br />
<br />
This command allows users to set the vhost of their<br />
CURRENT nick to be the vhost for all nicks in the same<br />
group.<br />
<br />
===GENERIC===<br />
====ASSIGN====<br />
Assigns a generic vhost to your nickname.<br />
<br />
====REMOVE====<br />
Removes your generic vhost and restores your normal hostname.<br />
<br />
[[Category:Anope]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Start_Guide&diff=5162Channel Start Guide2011-06-29T03:24:04Z<p>MIXX941: /* Step 2: Registering with ChanServ */ Update for new CS REGISTER syntax</p>
<hr />
<div>The following is a guide to setting up your own channel on [[MIXXnet]] and protecting it with [[services]]. <br />
<br />
===Step 1: Creating The Channel===<br />
The first step in creating a [[channel]] is to join it first. While you're on [[IRC]], type "/join #yourchannel" without quotes and replace "#yourchannel" with the channel you want to create. If the channel is empty or unregistered, you will become an [[op]] (@) in that channel.<br />
<br />
===Step 2: Registering with ChanServ===<br />
In order for you to be the owner of the channel and have full privileges on it, you must register it with [[ChanServ]]. This is a very easy process, however it requires a registered [[nickname]]. If you have not already registered a nickname, see the [[NickServ]] documents for instructions on how to do that. <br />
<br />
To register a channel, type the following command into your [[IRC client]]:<br />
<br />
'''/msg chanserv register #channelname description'''<br />
<br />
Replace "#channelname" and "description" with the channel you are registering, the founder password you wish to have, and the description of your channel.<br />
<br />
If you have succeeded, you will see something like this:<br />
<br />
-ChanServ- Channel #channelname registered under your nickname: YourNick<br />
-ChanServ- Your channel password is test - remember it for later use.<br />
--- ChanServ sets mode +n #channelname<br />
--- ChanServ sets mode +t #channelname<br />
--- ChanServ sets mode +r #channelname<br />
<br />
Now most likely you will want to set the topic, give people access, and perform other channel maintenance tasks. Here are some common channel commands and what they do:<br />
<br />
===Channel Modes===<br />
For a complete list of all channel modes available on MIXXnet, please see the [[Channel_Modes|Channel Modes]] and [[Extended_Bans|Extended Bans]] articles. Below is a summary of basic channel modes:<br />
<br />
* /topic #channelname New Topic - This will set the topic of your channel to whatever you wish.<br />
<br />
* /mode #channelname +o nickname - This will op the person with the nickname "nickname".<br />
<br />
* /mode #channelname +h nickname - This will give channel-half operator status to the person with the nickname "nickname".<br />
<br />
* /mode #channelname +v nickname - This will give voice to the person with the nickname "nickname".<br />
<br />
* /mode #channelname +b user@host - This will ban that user/host mask from your channel.<br />
<br />
* /mode #channelname +s - This will make your room secret, and not show up when someone does a /list.<br />
<br />
* /mode #channelname +p - This will make your channel private.<br />
<br />
* /mode #channelname +i - This will make your channel "Invite-Only". This means you must "/invite nickname" for them to be able to enter your channel.<br />
<br />
* /mode #channelname +k yoursecretkey - This will set your channel's "key" (or password). Replace "yoursecretkey" with the key you want to set.<br />
<br />
* /mode #channelname +m - This will make your channel "Moderated". This means that only people with a voice (+v) or higher (such as an op) can speak in the channel.<br />
<br />
* /mode #channelname +N - This disallows nickname changes while in your channel.<br />
<br />
===ChanServ Modes===<br />
* AutoOP (aop) - This user will be able to kick/ban and can set almost any channel mode, but does not have access to any ChanServ commands (such as adding/deleting people from access lists, using the "akick" function, etc).<br />
<br />
* SuperOP (sop) - This user has full channel privileges. They can set almost any channel mode and can add/delete people from the ChanServ access lists. They can also use ChanServ to "AutoKick" (akick) and ban a user.<br />
<br />
* HalfOP (hop) - This user can kick and ban regular and voiced users. They cannot kick or ban ops.<br />
<br />
* Voice (vop) - This user can speak in channels with +m set, but has no channel moderation features. There is no benefit to having voice in an unmoderated channel.<br />
<br />
===ChanServ Channel Commands===<br />
* /msg chanserv aop #channel add nickname - This will add "nickname" to the channel auto-op list.<br />
<br />
* /msg chanserv sop #channel add nickname - This will add "nickname" to the channel super-op list.<br />
<br />
* /msg chanserv hop #channel add nickname - This will add "nickname" to the channel half-op list.<br />
<br />
* /msg chanserv vop #channel add nickname - This will add "nickname" to the channel auto-voice list.<br />
<br />
* /msg chanserv *op #channel del nickname - This will delete "nickname" from the *op access list. Replace "*op" with either "hop", "aop", "sop", "vop".<br />
<br />
[[Category:Services]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Services_1.9&diff=5161Services 1.92011-06-29T00:58:15Z<p>MIXX941: Initial creation</p>
<hr />
<div>This article will outline new features and changes in MIXXnet's services software throughout the 1.9 series. Version 1.9 of services is under active development, so please contact us in #help with any issues or feature requests and we will send them upstream to the developers.<br />
<br />
==2011-06-28 (1.9.4+)==<br />
===New Features===<br />
* ChanServ is now able to join channels directly instead of under different BotServ monikers. To assign ChanServ to your channel: "/msg botserv assign #channel ChanServ"<br />
* NickServ can use client certificates for authentication. "/msg nickserv help cert" for more info.<br />
* Users can now reset their own passwords instead of asking staff. "/msg nickserv help resetpass" for more info.<br />
* ChanServ CLONE command to clone settings from one channel to another. "/msg chanserv help clone" for more info.<br />
* Users can remove their own access in channels.<br />
<br />
===Changes===<br />
* To prevent bots from registering, new users need to confirm their nick registrations via email. You will be given instructions upon registration.<br />
* The syntax to register a channel has changed and no longer requires a password. "/msg chanserv register #channel description"<br />
* Generic vhosts are now handled by HostServ instead of the old HostBot system. To assign a vhost to your nick: "/msg hostserv generic assign"<br />
* ChanServ MLOCK has been moved to ChanServ MODE, along with the ability to manually set modes through ChanServ. "/msg chanserv help mode" for more info.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRC_Client&diff=5160IRC Client2011-04-17T21:05:27Z<p>MIXX941: /* lightIRC */ Added a bullet list of recommended settings</p>
<hr />
<div>An [[IRC]] Client is a software program used to connect to an [[IRC|Internet Relay Chat]] network, such as [[MIXXnet]]. Below is a list of popular IRC clients for various platforms.<br />
<br />
==Graphical Clients==<br />
===Cross-Platform===<br />
* '''XChat:''' Created by Peter Zelenzy, [[XChat]] is a free, open source, and multi-platform IRC client with a graphical user interface. There are builds for various *nix distributions, [http://xchataqua.sourceforge.net/ Mac OS X], and Windows. [http://www.xchat.org http://www.xchat.org] (Note: The "official" Windows builds are not free. To see a list of completely free Windows builds, go [http://b0at.tx0.org/xchat/ here]).<br />
<br />
* '''Quassel:''' Quassel is an open source and cross-platform distributed IRC client. Its unique feature is the ability to attach and detach the graphical client portion from the core, similar to running screen and a text based client. [http://quassel-irc.org/ http://quassel-irc.org]<br />
<br />
* '''KVIrc:''' KVIrc is another open source and cross-platform IRC client based on the QT toolkit. There are binaries available for Unix, OS X, and Windows. [http://www.kvirc.de/ http://www.kvirc.de]<br />
<br />
* '''Pidgin:''' Pidgin is an open source, cross-platform application that combines many chat networks (includng IRC) into one program. [http://pidgin.im/ http://pidgin.im]<br />
<br />
* '''Opera:''' The excellent Opera web browser also has a simple [http://www.opera.com/browser/tutorials/intro/using/chat/ built-in IRC client]. There are versions available for various platforms including Windows, Mac OS X, FreeBSD, Linux, and Solaris. [http://www.opera.com/ http://www.opera.com]<br />
<br />
===Mac OS X Specific===<br />
* '''Colloquy:''' Colloquy is a free and open source graphical client with a slick Mac-inspired interface for Mac OS X. [http://colloquy.info/ http://colloquy.info]<br />
<br />
* '''Snak (Shareware):''' Snak is an IRC client for Macintosh OS X. It has several features and is actively developed. Snak is shareware ($29). [http://www.snak.com/ http://www.snak.com]<br />
<br />
* '''Ircle (Shareware):''' Another IRC client for Mac. Ircle runs on Mac OS 7.2 through 9.0.x, as well as Mac OS X 10.1 or newer. Ircle is shareware (19 €). [http://www.ircle.com http://www.ircle.com]<br />
<br />
===Windows Specific===<br />
* '''mIRC (Shareware):''' Khaled Mardam-Bey released the first version of [[mIRC]] on February 28, 1995. mIRC is a graphical IRC client for the Windows platform with it's own scripting language. mIRC is shareware, so to legally run it past 30 days without nag screens you need a $20 license. [http://www.mirc.com http://www.mirc.com]<br />
<br />
==Text Clients==<br />
===Cross-Platform===<br />
* '''Irssi:''' Irssi is a popular open source and free text based IRC client. Irssi is different from BitchX because it does not use the old ircII code. Irssi also supports Perl scripting and runtime modules, so it is highly customizable. There are binaries available for several operating systems including Mac OSX and Windows. [http://www.irssi.org http://www.irssi.org]<br />
<br />
* '''WeeChat:''' WeeChat is an open source text based client with some advanced features like multiple interface capability, horizontal and vertical window splitting, nickname list, smart "hotlist" in the status bar to show channel activity by name, highlighting without switching channels, and spell checking. [http://weechat.flashtux.org/ http://weechat.flashtux.org]<br />
<br />
* '''BitchX:''' BitchX is another popular open source text based IRC client for UNIX. It started out as a script for the ircII client, but then panasync patched the script directly into the actual client in 1994. There are binaries for many operating systems including Windows. [http://www.bitchx.org http://www.bitchx.org]<br />
<br />
==Web-Based Clients==<br />
===Mibbit===<br />
Mibbit is a popular and feature rich AJAX client which allows users to easily connect to IRC from any web browser without plugins or special firewall requirements. Webmasters can create a [http://wiki.mibbit.com/index.php/Widget Mibbit Widget] to embed the chat application on their website. Please note that Mibbit is an externally hosted service so we have no control over its operation or reliability, though we do recommend it for its ease of use, good interface/features, and overall stability. [http://mibbit.com http://mibbit.com]<br />
<br />
MIXXnet fully supports connecting through Mibbit on all servers, and Mibbit users will have their real hostnames shown on the network. '''"irc.mixxnet.net"''' must be used in the "server" parameter to allow users' real hostnames to show up.<br />
<br />
===lightIRC===<br />
lightIRC is a freeware Flash IRC client with a clean and easy to use interface. Website admins can host the files on their own server or add an iframe to existing files on lightIRC's server. This client requires users to have the Adobe Flash plugin enabled in their browser which can limit compatibility as there is not official Flash support for all operating systems/browsers. [http://lightirc.com/ http://lightirc.com]<br />
<br />
Below are a few notes and recommendations on how to use lightIRC on MIXXnet:<br />
<br />
* All MIXXnet servers in the main rotation have support for lightIRC, however '''the "policyPort" parameter must be set to "6843"''' for the application to properly connect.<br />
<br />
* We recommend setting the "ident" parameter on lightIRC to the name of your channel as the default random string may cause users to be incorrectly identified as malicious bots.<br />
<br />
* The "nickAlternate" parameter should be set to prevent lightIRC from rapidly reconnecting if the nickname is in use.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRC_Client&diff=5159IRC Client2011-04-10T08:58:13Z<p>MIXX941: /* lightIRC */ Add note about ident parameter</p>
<hr />
<div>An [[IRC]] Client is a software program used to connect to an [[IRC|Internet Relay Chat]] network, such as [[MIXXnet]]. Below is a list of popular IRC clients for various platforms.<br />
<br />
==Graphical Clients==<br />
===Cross-Platform===<br />
* '''XChat:''' Created by Peter Zelenzy, [[XChat]] is a free, open source, and multi-platform IRC client with a graphical user interface. There are builds for various *nix distributions, [http://xchataqua.sourceforge.net/ Mac OS X], and Windows. [http://www.xchat.org http://www.xchat.org] (Note: The "official" Windows builds are not free. To see a list of completely free Windows builds, go [http://b0at.tx0.org/xchat/ here]).<br />
<br />
* '''Quassel:''' Quassel is an open source and cross-platform distributed IRC client. Its unique feature is the ability to attach and detach the graphical client portion from the core, similar to running screen and a text based client. [http://quassel-irc.org/ http://quassel-irc.org]<br />
<br />
* '''KVIrc:''' KVIrc is another open source and cross-platform IRC client based on the QT toolkit. There are binaries available for Unix, OS X, and Windows. [http://www.kvirc.de/ http://www.kvirc.de]<br />
<br />
* '''Pidgin:''' Pidgin is an open source, cross-platform application that combines many chat networks (includng IRC) into one program. [http://pidgin.im/ http://pidgin.im]<br />
<br />
* '''Opera:''' The excellent Opera web browser also has a simple [http://www.opera.com/browser/tutorials/intro/using/chat/ built-in IRC client]. There are versions available for various platforms including Windows, Mac OS X, FreeBSD, Linux, and Solaris. [http://www.opera.com/ http://www.opera.com]<br />
<br />
===Mac OS X Specific===<br />
* '''Colloquy:''' Colloquy is a free and open source graphical client with a slick Mac-inspired interface for Mac OS X. [http://colloquy.info/ http://colloquy.info]<br />
<br />
* '''Snak (Shareware):''' Snak is an IRC client for Macintosh OS X. It has several features and is actively developed. Snak is shareware ($29). [http://www.snak.com/ http://www.snak.com]<br />
<br />
* '''Ircle (Shareware):''' Another IRC client for Mac. Ircle runs on Mac OS 7.2 through 9.0.x, as well as Mac OS X 10.1 or newer. Ircle is shareware (19 €). [http://www.ircle.com http://www.ircle.com]<br />
<br />
===Windows Specific===<br />
* '''mIRC (Shareware):''' Khaled Mardam-Bey released the first version of [[mIRC]] on February 28, 1995. mIRC is a graphical IRC client for the Windows platform with it's own scripting language. mIRC is shareware, so to legally run it past 30 days without nag screens you need a $20 license. [http://www.mirc.com http://www.mirc.com]<br />
<br />
==Text Clients==<br />
===Cross-Platform===<br />
* '''Irssi:''' Irssi is a popular open source and free text based IRC client. Irssi is different from BitchX because it does not use the old ircII code. Irssi also supports Perl scripting and runtime modules, so it is highly customizable. There are binaries available for several operating systems including Mac OSX and Windows. [http://www.irssi.org http://www.irssi.org]<br />
<br />
* '''WeeChat:''' WeeChat is an open source text based client with some advanced features like multiple interface capability, horizontal and vertical window splitting, nickname list, smart "hotlist" in the status bar to show channel activity by name, highlighting without switching channels, and spell checking. [http://weechat.flashtux.org/ http://weechat.flashtux.org]<br />
<br />
* '''BitchX:''' BitchX is another popular open source text based IRC client for UNIX. It started out as a script for the ircII client, but then panasync patched the script directly into the actual client in 1994. There are binaries for many operating systems including Windows. [http://www.bitchx.org http://www.bitchx.org]<br />
<br />
==Web-Based Clients==<br />
===Mibbit===<br />
Mibbit is a popular and feature rich AJAX client which allows users to easily connect to IRC from any web browser without plugins or special firewall requirements. Webmasters can create a [http://wiki.mibbit.com/index.php/Widget Mibbit Widget] to embed the chat application on their website. Please note that Mibbit is an externally hosted service so we have no control over its operation or reliability, though we do recommend it for its ease of use, good interface/features, and overall stability. [http://mibbit.com http://mibbit.com]<br />
<br />
MIXXnet fully supports connecting through Mibbit on all servers, and Mibbit users will have their real hostnames shown on the network. '''"irc.mixxnet.net"''' must be used in the "server" parameter to allow users' real hostnames to show up.<br />
<br />
===lightIRC===<br />
lightIRC is a freeware Flash IRC client with a clean and easy to use interface. Website admins can host the files on their own server or add an iframe to existing files on lightIRC's server. This client requires users to have the Adobe Flash plugin enabled in their browser which can limit compatibility as there is not official Flash support for all operating systems/browsers. [http://lightirc.com/ http://lightirc.com]<br />
<br />
All MIXXnet servers in the main rotation have support for lightIRC, however '''the "policyPort" parameter must be set to "6843"''' for the application to properly connect.<br />
<br />
We also recommend setting the "ident" parameter on lightIRC to the name of your channel as the default random string may cause users to be incorrectly identified as malicious bots.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRC_Client&diff=5158IRC Client2011-04-01T19:26:55Z<p>MIXX941: /* Windows Specific */ Add clarification on mIRC registration</p>
<hr />
<div>An [[IRC]] Client is a software program used to connect to an [[IRC|Internet Relay Chat]] network, such as [[MIXXnet]]. Below is a list of popular IRC clients for various platforms.<br />
<br />
==Graphical Clients==<br />
===Cross-Platform===<br />
* '''XChat:''' Created by Peter Zelenzy, [[XChat]] is a free, open source, and multi-platform IRC client with a graphical user interface. There are builds for various *nix distributions, [http://xchataqua.sourceforge.net/ Mac OS X], and Windows. [http://www.xchat.org http://www.xchat.org] (Note: The "official" Windows builds are not free. To see a list of completely free Windows builds, go [http://b0at.tx0.org/xchat/ here]).<br />
<br />
* '''Quassel:''' Quassel is an open source and cross-platform distributed IRC client. Its unique feature is the ability to attach and detach the graphical client portion from the core, similar to running screen and a text based client. [http://quassel-irc.org/ http://quassel-irc.org]<br />
<br />
* '''KVIrc:''' KVIrc is another open source and cross-platform IRC client based on the QT toolkit. There are binaries available for Unix, OS X, and Windows. [http://www.kvirc.de/ http://www.kvirc.de]<br />
<br />
* '''Pidgin:''' Pidgin is an open source, cross-platform application that combines many chat networks (includng IRC) into one program. [http://pidgin.im/ http://pidgin.im]<br />
<br />
* '''Opera:''' The excellent Opera web browser also has a simple [http://www.opera.com/browser/tutorials/intro/using/chat/ built-in IRC client]. There are versions available for various platforms including Windows, Mac OS X, FreeBSD, Linux, and Solaris. [http://www.opera.com/ http://www.opera.com]<br />
<br />
===Mac OS X Specific===<br />
* '''Colloquy:''' Colloquy is a free and open source graphical client with a slick Mac-inspired interface for Mac OS X. [http://colloquy.info/ http://colloquy.info]<br />
<br />
* '''Snak (Shareware):''' Snak is an IRC client for Macintosh OS X. It has several features and is actively developed. Snak is shareware ($29). [http://www.snak.com/ http://www.snak.com]<br />
<br />
* '''Ircle (Shareware):''' Another IRC client for Mac. Ircle runs on Mac OS 7.2 through 9.0.x, as well as Mac OS X 10.1 or newer. Ircle is shareware (19 €). [http://www.ircle.com http://www.ircle.com]<br />
<br />
===Windows Specific===<br />
* '''mIRC (Shareware):''' Khaled Mardam-Bey released the first version of [[mIRC]] on February 28, 1995. mIRC is a graphical IRC client for the Windows platform with it's own scripting language. mIRC is shareware, so to legally run it past 30 days without nag screens you need a $20 license. [http://www.mirc.com http://www.mirc.com]<br />
<br />
==Text Clients==<br />
===Cross-Platform===<br />
* '''Irssi:''' Irssi is a popular open source and free text based IRC client. Irssi is different from BitchX because it does not use the old ircII code. Irssi also supports Perl scripting and runtime modules, so it is highly customizable. There are binaries available for several operating systems including Mac OSX and Windows. [http://www.irssi.org http://www.irssi.org]<br />
<br />
* '''WeeChat:''' WeeChat is an open source text based client with some advanced features like multiple interface capability, horizontal and vertical window splitting, nickname list, smart "hotlist" in the status bar to show channel activity by name, highlighting without switching channels, and spell checking. [http://weechat.flashtux.org/ http://weechat.flashtux.org]<br />
<br />
* '''BitchX:''' BitchX is another popular open source text based IRC client for UNIX. It started out as a script for the ircII client, but then panasync patched the script directly into the actual client in 1994. There are binaries for many operating systems including Windows. [http://www.bitchx.org http://www.bitchx.org]<br />
<br />
==Web-Based Clients==<br />
===Mibbit===<br />
Mibbit is a popular and feature rich AJAX client which allows users to easily connect to IRC from any web browser without plugins or special firewall requirements. Webmasters can create a [http://wiki.mibbit.com/index.php/Widget Mibbit Widget] to embed the chat application on their website. Please note that Mibbit is an externally hosted service so we have no control over its operation or reliability, though we do recommend it for its ease of use, good interface/features, and overall stability. [http://mibbit.com http://mibbit.com]<br />
<br />
MIXXnet fully supports connecting through Mibbit on all servers, and Mibbit users will have their real hostnames shown on the network. '''"irc.mixxnet.net"''' must be used in the "server" parameter to allow users' real hostnames to show up.<br />
<br />
===lightIRC===<br />
lightIRC is a freeware Flash IRC client with a clean and easy to use interface. Website admins can host the files on their own server or add an iframe to existing files on lightIRC's server. This client requires users to have the Adobe Flash plugin enabled in their browser which can limit compatibility as there is not official Flash support for all operating systems/browsers. [http://lightirc.com/ http://lightirc.com]<br />
<br />
All MIXXnet servers in the main rotation have support for lightIRC, however '''the "policyPort" parameter must be set to "6843"''' for the application to properly connect.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Modes&diff=5157Channel Modes2011-03-20T06:55:25Z<p>MIXX941: /* X (Exempt Channel Ops) */ Capitalization</p>
<hr />
<div>Below is a full list of channel modes on MIXXnet and how they are used.<br />
<br />
In general, modes are set and removed in the following way:<br />
<br />
/mode #channel +<mode><br />
/mode #channel -<mode><br />
<br />
Examples of how to set each mode and their various parameters are provided below.<br />
<br />
==Basic Modes==<br />
===b (Ban)===<br />
Bans user from channel that matches the nick!ident@host hostmask. Can optionally redirect the banned user to a special channel if they attempt to join the channel while banned (see example 2 below).<br />
<br />
/mode #channel +b <nick!ident@host><br />
/mode #channel +b <nick!ident@host#bannedchannel><br />
<br />
===h (Halfop)===<br />
Gives <nickname> half-operator status on the channel<br />
<br />
/mode #channel +h <nickname><br />
<br />
===i (Invite Only)===<br />
Sets channel invite only. Users must be invited to join.<br />
<br />
/mode #channel +i<br />
<br />
===k (Channel Password)===<br />
Sets a channel password that users must have in order to join.<br />
<br />
/mode #channel +k <password><br />
<br />
===l (Channel Limit)===<br />
Sets a limit for the maximum numbers of users that can be on the channel at once.<br />
<br />
/mode #channel +l <limit><br />
<br />
===m (Moderated)===<br />
Sets channel to "moderated"; users must be voiced (+v) or higher to talk.<br />
<br />
/mode #channel +m<br />
<br />
===n (No External Messages)===<br />
Blocks external messages; users must be on the channel to talk. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +n<br />
<br />
===o (Channel Operator)===<br />
Gives <nickname> operator status on the channel. Requires channel operator status.<br />
<br />
/mode #channel +o <nickname<br />
<br />
===p (Private)===<br />
Sets channel as private; hides channel from user's WHOIS reply<br />
<br />
/mode #channel +p<br />
<br />
===s (Secret)===<br />
Sets channel as secret. This is the same as mode "p", however it also hides the channel from a /LIST<br />
<br />
/mode #channel +s<br />
<br />
===t (Topic Protection)===<br />
Makes it so only channel (half-)operators or higher can change the channel topic. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +t<br />
<br />
===v (Voice)===<br />
Gives voice to <nickname>. Requires half-operator status or higher.<br />
<br />
/mode #channel +v <nickname><br />
<br />
==Advanced Modes==<br />
<br />
===A (Allow Regular Users To Invite)===<br />
Allows regular, non-opped users to invite users to the channel using "/invite". As invites bypass channel bans, limits, and keys, '''setting this mode will allow regular users to invite anyone into the channel even if they are banned, do not have the channel key, or the channel limit has been exceeded. USE THIS MODE WITH CAUTION.'''<br />
<br />
===a (Protected User)===<br />
Gives protected status to <nickname>. Protected users cannot be kicked or deopped except by the channel founder or services. Channel mode +a does not give +o, so non operators can be protected with +a.<br />
<br />
/mode #channel +a <nickname><br />
<br />
===B (Block Caps)===<br />
Blocks messages to the channel that contain more than 75% CAPITAL LETTERS.<br />
<br />
/mode #channel +B<br />
<br />
===e (Ban Exception)===<br />
Sets a ban exception on a nick!user@host hostmask. Users who match can still join the channel even if banned.<br />
<br />
/mode #channel +e <nick!user@host><br />
<br />
===c (Block Colors)===<br />
Blocks messages to the channel that contain colors.<br />
<br />
/mode #channel +c<br />
<br />
===C (No CTCP)===<br />
Blocks CTCP (PING, TIME, etc) to channels.<br />
<br />
/mode #channel +C<br />
<br />
===d (Delay Message)===<br />
Requires new users joining the channel to wait <sec> seconds before sending to the channel.<br />
<br />
/mode #channel +d <sec><br />
<br />
===f (Message Flood Protection)===<br />
Provides protection against message/notice flooding. When a user types more lines than <lines> in <sec> seconds, they will be kicked. If <lines> is prefixed with a *, the user will be kicked and banned.<br />
<br />
/mode #channel +f <lines>:<sec><br />
/mode #channel +f 5:10 (Kicks a user who says more than 5 lines in 10 seconds)<br />
/mode #channel +f *3:5 (Kicks and bans a user who says more than 3 lines in 5 seconds)<br />
<br />
===g (Channel Message Filter)===<br />
Manages the channel message filter which gives channels the ability to have custom words to block/filter. Words are added with "+g <word>" and removed with "-g <word>" (examples are below):<br />
<br />
/mode #channel +g abadword (Adds "abadword" to the channel filter)<br />
/mode #channel -g abadword (Removes "abadword" from the channel filter)<br />
/mode #channel +g (Shows all words on the channel filter)<br />
<br />
===G (Censor)===<br />
Filters out common swear words that are said in the channel. The message still goes through, however any swear words said are censored out.<br />
<br />
/mode #channel +G<br />
<br />
===H (Channel History)===<br />
Replays the last <lines> lines of channel activity within <sec> seconds to new users joining.<br />
<br />
/mode #channel +H <lines>:<sec><br />
<br />
===I (Invite Exception)===<br />
Allows users who match a nick!user@host hostmask to join the channel even if it is +i (invite only).<br />
<br />
/mode #channel +I <nick!user@host><br />
<br />
===j (Join Flood Protection)===<br />
Provides protection against join flooding. If there are more than <joins> joins in <sec> seconds, the channel will be locked for 60 seconds and new users will not be able to join for this time period. The lock can be removed before the 60 second time by unsetting and resetting +j. <br />
<br />
/mode #channel +j <joins>:<sec><br />
<br />
===J (Rejoin Prevention)===<br />
Prevents a user from rejoining the channel for <sec> seconds after being kicked.<br />
<br />
/mode #channel +J <sec><br />
<br />
===K (No Knocking)===<br />
Prevents users from doing a /KNOCK on an invite only (+i) channel.<br />
<br />
/mode #channel +K<br />
<br />
===L (Redirect When Full)===<br />
Redirects users to <channel> when the user limit (+l) has been reached on the current channel.<br />
<br />
/mode #channel +L <channel><br />
<br />
===M (Only Registered Users Talk)===<br />
Restricts users from talking on the channel unless they are registered and identified to [[NickServ]].<br />
<br />
/mode #channel +M<br />
<br />
===N (No Nick Changes)===<br />
Prevents users from changing their nicknames while in the channel.<br />
<br />
/mode #channel +N<br />
<br />
===P (Block Caps)===<br />
Blocks messages to the channel that are made up of mostly capital letters.<br />
<br />
/mode #channel +P<br />
<br />
===R (Only Registered Users Join)===<br />
Restricts users from joining the channel unless they are registered and identified to NickServ.<br />
<br />
/mode #channel +R<br />
<br />
===S (Strip Colors)===<br />
Strips colors from messages to the channel.<br />
<br />
/mode #channel +S<br />
<br />
===T (No Notices)===<br />
Prevents users from sending NOTICEs to the channel.<br />
<br />
/mode #channel +T<br />
<br />
===u (Auditorium Mode)===<br />
Provides an "auditorium mode" for the channel. When set, users will only see themselves and ops in the channel but will not see any other users in the userlist or any joins/parts/quits from other users.<br />
<br />
/mode #channel +u<br />
<br />
===x (Exception)===<br />
Allows users who match a nick!user@host hostmask to override ALL join restrictions such as +i/+l/+k/+b and join the channel no matter what.<br />
<br />
/mode #channel +x <nick!user@host><br />
<br />
===X (Exempt Channel Ops)===<br />
Allows channel operators of various ranks to be exempt from certain restrictions.<br />
<br />
/mode +X <permission>:<mode><br />
<br />
Valid permissions are:<br />
<br />
* topiclock - Change the topic if +t is set<br />
* auditorium-vis - Be visible in a +u channel<br />
* auditorium-see - See full user list of a +u channel<br />
* blockcaps<br />
* blockcolor<br />
* censor<br />
* filter<br />
* flood<br />
* nickflood<br />
* noctcp<br />
* nonick<br />
* nonotice<br />
* regmoderated<br />
* stripcolor<br />
<br />
Valid modes/ranks are:<br />
<br />
* q - Founder<br />
* o - Operator<br />
* a - Protected<br />
* h - Halfop<br />
* v - Voice<br />
<br />
===z (SSL Users Only)===<br />
Requires all users on the channel to be connected to MIXXnet via [[SSL]]. Non-SSL users will not be allowed to join.<br />
<br />
/mode #channel +z<br />
<br />
==Extended Bans==<br />
Extended Bans are an extension of channel ban-matching modes which allow fine control over who can do what on your channel.<br />
<br />
Please see the [[Extended_Bans|Extended Bans documentation]] for more information.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Modes&diff=5156Channel Modes2011-03-20T03:01:28Z<p>MIXX941: /* X (Exempt Channel Ops) */ Fix reversed syntax</p>
<hr />
<div>Below is a full list of channel modes on MIXXnet and how they are used.<br />
<br />
In general, modes are set and removed in the following way:<br />
<br />
/mode #channel +<mode><br />
/mode #channel -<mode><br />
<br />
Examples of how to set each mode and their various parameters are provided below.<br />
<br />
==Basic Modes==<br />
===b (Ban)===<br />
Bans user from channel that matches the nick!ident@host hostmask. Can optionally redirect the banned user to a special channel if they attempt to join the channel while banned (see example 2 below).<br />
<br />
/mode #channel +b <nick!ident@host><br />
/mode #channel +b <nick!ident@host#bannedchannel><br />
<br />
===h (Halfop)===<br />
Gives <nickname> half-operator status on the channel<br />
<br />
/mode #channel +h <nickname><br />
<br />
===i (Invite Only)===<br />
Sets channel invite only. Users must be invited to join.<br />
<br />
/mode #channel +i<br />
<br />
===k (Channel Password)===<br />
Sets a channel password that users must have in order to join.<br />
<br />
/mode #channel +k <password><br />
<br />
===l (Channel Limit)===<br />
Sets a limit for the maximum numbers of users that can be on the channel at once.<br />
<br />
/mode #channel +l <limit><br />
<br />
===m (Moderated)===<br />
Sets channel to "moderated"; users must be voiced (+v) or higher to talk.<br />
<br />
/mode #channel +m<br />
<br />
===n (No External Messages)===<br />
Blocks external messages; users must be on the channel to talk. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +n<br />
<br />
===o (Channel Operator)===<br />
Gives <nickname> operator status on the channel. Requires channel operator status.<br />
<br />
/mode #channel +o <nickname<br />
<br />
===p (Private)===<br />
Sets channel as private; hides channel from user's WHOIS reply<br />
<br />
/mode #channel +p<br />
<br />
===s (Secret)===<br />
Sets channel as secret. This is the same as mode "p", however it also hides the channel from a /LIST<br />
<br />
/mode #channel +s<br />
<br />
===t (Topic Protection)===<br />
Makes it so only channel (half-)operators or higher can change the channel topic. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +t<br />
<br />
===v (Voice)===<br />
Gives voice to <nickname>. Requires half-operator status or higher.<br />
<br />
/mode #channel +v <nickname><br />
<br />
==Advanced Modes==<br />
<br />
===A (Allow Regular Users To Invite)===<br />
Allows regular, non-opped users to invite users to the channel using "/invite". As invites bypass channel bans, limits, and keys, '''setting this mode will allow regular users to invite anyone into the channel even if they are banned, do not have the channel key, or the channel limit has been exceeded. USE THIS MODE WITH CAUTION.'''<br />
<br />
===a (Protected User)===<br />
Gives protected status to <nickname>. Protected users cannot be kicked or deopped except by the channel founder or services. Channel mode +a does not give +o, so non operators can be protected with +a.<br />
<br />
/mode #channel +a <nickname><br />
<br />
===B (Block Caps)===<br />
Blocks messages to the channel that contain more than 75% CAPITAL LETTERS.<br />
<br />
/mode #channel +B<br />
<br />
===e (Ban Exception)===<br />
Sets a ban exception on a nick!user@host hostmask. Users who match can still join the channel even if banned.<br />
<br />
/mode #channel +e <nick!user@host><br />
<br />
===c (Block Colors)===<br />
Blocks messages to the channel that contain colors.<br />
<br />
/mode #channel +c<br />
<br />
===C (No CTCP)===<br />
Blocks CTCP (PING, TIME, etc) to channels.<br />
<br />
/mode #channel +C<br />
<br />
===d (Delay Message)===<br />
Requires new users joining the channel to wait <sec> seconds before sending to the channel.<br />
<br />
/mode #channel +d <sec><br />
<br />
===f (Message Flood Protection)===<br />
Provides protection against message/notice flooding. When a user types more lines than <lines> in <sec> seconds, they will be kicked. If <lines> is prefixed with a *, the user will be kicked and banned.<br />
<br />
/mode #channel +f <lines>:<sec><br />
/mode #channel +f 5:10 (Kicks a user who says more than 5 lines in 10 seconds)<br />
/mode #channel +f *3:5 (Kicks and bans a user who says more than 3 lines in 5 seconds)<br />
<br />
===g (Channel Message Filter)===<br />
Manages the channel message filter which gives channels the ability to have custom words to block/filter. Words are added with "+g <word>" and removed with "-g <word>" (examples are below):<br />
<br />
/mode #channel +g abadword (Adds "abadword" to the channel filter)<br />
/mode #channel -g abadword (Removes "abadword" from the channel filter)<br />
/mode #channel +g (Shows all words on the channel filter)<br />
<br />
===G (Censor)===<br />
Filters out common swear words that are said in the channel. The message still goes through, however any swear words said are censored out.<br />
<br />
/mode #channel +G<br />
<br />
===H (Channel History)===<br />
Replays the last <lines> lines of channel activity within <sec> seconds to new users joining.<br />
<br />
/mode #channel +H <lines>:<sec><br />
<br />
===I (Invite Exception)===<br />
Allows users who match a nick!user@host hostmask to join the channel even if it is +i (invite only).<br />
<br />
/mode #channel +I <nick!user@host><br />
<br />
===j (Join Flood Protection)===<br />
Provides protection against join flooding. If there are more than <joins> joins in <sec> seconds, the channel will be locked for 60 seconds and new users will not be able to join for this time period. The lock can be removed before the 60 second time by unsetting and resetting +j. <br />
<br />
/mode #channel +j <joins>:<sec><br />
<br />
===J (Rejoin Prevention)===<br />
Prevents a user from rejoining the channel for <sec> seconds after being kicked.<br />
<br />
/mode #channel +J <sec><br />
<br />
===K (No Knocking)===<br />
Prevents users from doing a /KNOCK on an invite only (+i) channel.<br />
<br />
/mode #channel +K<br />
<br />
===L (Redirect When Full)===<br />
Redirects users to <channel> when the user limit (+l) has been reached on the current channel.<br />
<br />
/mode #channel +L <channel><br />
<br />
===M (Only Registered Users Talk)===<br />
Restricts users from talking on the channel unless they are registered and identified to [[NickServ]].<br />
<br />
/mode #channel +M<br />
<br />
===N (No Nick Changes)===<br />
Prevents users from changing their nicknames while in the channel.<br />
<br />
/mode #channel +N<br />
<br />
===P (Block Caps)===<br />
Blocks messages to the channel that are made up of mostly capital letters.<br />
<br />
/mode #channel +P<br />
<br />
===R (Only Registered Users Join)===<br />
Restricts users from joining the channel unless they are registered and identified to NickServ.<br />
<br />
/mode #channel +R<br />
<br />
===S (Strip Colors)===<br />
Strips colors from messages to the channel.<br />
<br />
/mode #channel +S<br />
<br />
===T (No Notices)===<br />
Prevents users from sending NOTICEs to the channel.<br />
<br />
/mode #channel +T<br />
<br />
===u (Auditorium Mode)===<br />
Provides an "auditorium mode" for the channel. When set, users will only see themselves and ops in the channel but will not see any other users in the userlist or any joins/parts/quits from other users.<br />
<br />
/mode #channel +u<br />
<br />
===x (Exception)===<br />
Allows users who match a nick!user@host hostmask to override ALL join restrictions such as +i/+l/+k/+b and join the channel no matter what.<br />
<br />
/mode #channel +x <nick!user@host><br />
<br />
===X (Exempt Channel Ops)===<br />
Allows channel operators of various ranks to be exempt from certain restrictions.<br />
<br />
/mode +X <permission>:<mode><br />
<br />
Valid permissions are:<br />
<br />
* topiclock - Change the topic if +t is set<br />
* auditorium-vis - Be visible in a +u channel<br />
* auditorium-see - See full user list of a +u channel<br />
* blockcaps<br />
* blockcolor<br />
* censor<br />
* filter<br />
* flood<br />
* nickflood<br />
* noctcp<br />
* nonick<br />
* nonotice<br />
* regmoderated<br />
* stripcolor<br />
<br />
Valid modes/ranks are:<br />
<br />
* q - Founder<br />
* o - Operator<br />
* a - Protected<br />
* h - Halfop<br />
* v - voice<br />
<br />
===z (SSL Users Only)===<br />
Requires all users on the channel to be connected to MIXXnet via [[SSL]]. Non-SSL users will not be allowed to join.<br />
<br />
/mode #channel +z<br />
<br />
==Extended Bans==<br />
Extended Bans are an extension of channel ban-matching modes which allow fine control over who can do what on your channel.<br />
<br />
Please see the [[Extended_Bans|Extended Bans documentation]] for more information.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Modes&diff=5155Channel Modes2011-03-17T19:41:06Z<p>MIXX941: /* B (Block Caps) */ 50% -> 75%</p>
<hr />
<div>Below is a full list of channel modes on MIXXnet and how they are used.<br />
<br />
In general, modes are set and removed in the following way:<br />
<br />
/mode #channel +<mode><br />
/mode #channel -<mode><br />
<br />
Examples of how to set each mode and their various parameters are provided below.<br />
<br />
==Basic Modes==<br />
===b (Ban)===<br />
Bans user from channel that matches the nick!ident@host hostmask. Can optionally redirect the banned user to a special channel if they attempt to join the channel while banned (see example 2 below).<br />
<br />
/mode #channel +b <nick!ident@host><br />
/mode #channel +b <nick!ident@host#bannedchannel><br />
<br />
===h (Halfop)===<br />
Gives <nickname> half-operator status on the channel<br />
<br />
/mode #channel +h <nickname><br />
<br />
===i (Invite Only)===<br />
Sets channel invite only. Users must be invited to join.<br />
<br />
/mode #channel +i<br />
<br />
===k (Channel Password)===<br />
Sets a channel password that users must have in order to join.<br />
<br />
/mode #channel +k <password><br />
<br />
===l (Channel Limit)===<br />
Sets a limit for the maximum numbers of users that can be on the channel at once.<br />
<br />
/mode #channel +l <limit><br />
<br />
===m (Moderated)===<br />
Sets channel to "moderated"; users must be voiced (+v) or higher to talk.<br />
<br />
/mode #channel +m<br />
<br />
===n (No External Messages)===<br />
Blocks external messages; users must be on the channel to talk. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +n<br />
<br />
===o (Channel Operator)===<br />
Gives <nickname> operator status on the channel. Requires channel operator status.<br />
<br />
/mode #channel +o <nickname<br />
<br />
===p (Private)===<br />
Sets channel as private; hides channel from user's WHOIS reply<br />
<br />
/mode #channel +p<br />
<br />
===s (Secret)===<br />
Sets channel as secret. This is the same as mode "p", however it also hides the channel from a /LIST<br />
<br />
/mode #channel +s<br />
<br />
===t (Topic Protection)===<br />
Makes it so only channel (half-)operators or higher can change the channel topic. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +t<br />
<br />
===v (Voice)===<br />
Gives voice to <nickname>. Requires half-operator status or higher.<br />
<br />
/mode #channel +v <nickname><br />
<br />
==Advanced Modes==<br />
<br />
===A (Allow Regular Users To Invite)===<br />
Allows regular, non-opped users to invite users to the channel using "/invite". As invites bypass channel bans, limits, and keys, '''setting this mode will allow regular users to invite anyone into the channel even if they are banned, do not have the channel key, or the channel limit has been exceeded. USE THIS MODE WITH CAUTION.'''<br />
<br />
===a (Protected User)===<br />
Gives protected status to <nickname>. Protected users cannot be kicked or deopped except by the channel founder or services. Channel mode +a does not give +o, so non operators can be protected with +a.<br />
<br />
/mode #channel +a <nickname><br />
<br />
===B (Block Caps)===<br />
Blocks messages to the channel that contain more than 75% CAPITAL LETTERS.<br />
<br />
/mode #channel +B<br />
<br />
===e (Ban Exception)===<br />
Sets a ban exception on a nick!user@host hostmask. Users who match can still join the channel even if banned.<br />
<br />
/mode #channel +e <nick!user@host><br />
<br />
===c (Block Colors)===<br />
Blocks messages to the channel that contain colors.<br />
<br />
/mode #channel +c<br />
<br />
===C (No CTCP)===<br />
Blocks CTCP (PING, TIME, etc) to channels.<br />
<br />
/mode #channel +C<br />
<br />
===d (Delay Message)===<br />
Requires new users joining the channel to wait <sec> seconds before sending to the channel.<br />
<br />
/mode #channel +d <sec><br />
<br />
===f (Message Flood Protection)===<br />
Provides protection against message/notice flooding. When a user types more lines than <lines> in <sec> seconds, they will be kicked. If <lines> is prefixed with a *, the user will be kicked and banned.<br />
<br />
/mode #channel +f <lines>:<sec><br />
/mode #channel +f 5:10 (Kicks a user who says more than 5 lines in 10 seconds)<br />
/mode #channel +f *3:5 (Kicks and bans a user who says more than 3 lines in 5 seconds)<br />
<br />
===g (Channel Message Filter)===<br />
Manages the channel message filter which gives channels the ability to have custom words to block/filter. Words are added with "+g <word>" and removed with "-g <word>" (examples are below):<br />
<br />
/mode #channel +g abadword (Adds "abadword" to the channel filter)<br />
/mode #channel -g abadword (Removes "abadword" from the channel filter)<br />
/mode #channel +g (Shows all words on the channel filter)<br />
<br />
===G (Censor)===<br />
Filters out common swear words that are said in the channel. The message still goes through, however any swear words said are censored out.<br />
<br />
/mode #channel +G<br />
<br />
===H (Channel History)===<br />
Replays the last <lines> lines of channel activity within <sec> seconds to new users joining.<br />
<br />
/mode #channel +H <lines>:<sec><br />
<br />
===I (Invite Exception)===<br />
Allows users who match a nick!user@host hostmask to join the channel even if it is +i (invite only).<br />
<br />
/mode #channel +I <nick!user@host><br />
<br />
===j (Join Flood Protection)===<br />
Provides protection against join flooding. If there are more than <joins> joins in <sec> seconds, the channel will be locked for 60 seconds and new users will not be able to join for this time period. The lock can be removed before the 60 second time by unsetting and resetting +j. <br />
<br />
/mode #channel +j <joins>:<sec><br />
<br />
===J (Rejoin Prevention)===<br />
Prevents a user from rejoining the channel for <sec> seconds after being kicked.<br />
<br />
/mode #channel +J <sec><br />
<br />
===K (No Knocking)===<br />
Prevents users from doing a /KNOCK on an invite only (+i) channel.<br />
<br />
/mode #channel +K<br />
<br />
===L (Redirect When Full)===<br />
Redirects users to <channel> when the user limit (+l) has been reached on the current channel.<br />
<br />
/mode #channel +L <channel><br />
<br />
===M (Only Registered Users Talk)===<br />
Restricts users from talking on the channel unless they are registered and identified to [[NickServ]].<br />
<br />
/mode #channel +M<br />
<br />
===N (No Nick Changes)===<br />
Prevents users from changing their nicknames while in the channel.<br />
<br />
/mode #channel +N<br />
<br />
===P (Block Caps)===<br />
Blocks messages to the channel that are made up of mostly capital letters.<br />
<br />
/mode #channel +P<br />
<br />
===R (Only Registered Users Join)===<br />
Restricts users from joining the channel unless they are registered and identified to NickServ.<br />
<br />
/mode #channel +R<br />
<br />
===S (Strip Colors)===<br />
Strips colors from messages to the channel.<br />
<br />
/mode #channel +S<br />
<br />
===T (No Notices)===<br />
Prevents users from sending NOTICEs to the channel.<br />
<br />
/mode #channel +T<br />
<br />
===u (Auditorium Mode)===<br />
Provides an "auditorium mode" for the channel. When set, users will only see themselves and ops in the channel but will not see any other users in the userlist or any joins/parts/quits from other users.<br />
<br />
/mode #channel +u<br />
<br />
===x (Exception)===<br />
Allows users who match a nick!user@host hostmask to override ALL join restrictions such as +i/+l/+k/+b and join the channel no matter what.<br />
<br />
/mode #channel +x <nick!user@host><br />
<br />
===X (Exempt Channel Ops)===<br />
Allows channel operators of various ranks to be exempt from certain restrictions.<br />
<br />
/mode +X <mode>:<permission><br />
<br />
Valid modes/ranks are:<br />
<br />
* q - Founder<br />
* o - Operator<br />
* a - Protected<br />
* h - Halfop<br />
* v - voice<br />
<br />
Valid permissions are:<br />
<br />
* topiclock - Change the topic if +t is set<br />
* auditorium-vis - Be visible in a +u channel<br />
* auditorium-see - See full user list of a +u channel<br />
* blockcaps<br />
* blockcolor<br />
* censor<br />
* filter<br />
* flood<br />
* nickflood<br />
* noctcp<br />
* nonick<br />
* nonotice<br />
* regmoderated<br />
* stripcolor<br />
<br />
===z (SSL Users Only)===<br />
Requires all users on the channel to be connected to MIXXnet via [[SSL]]. Non-SSL users will not be allowed to join.<br />
<br />
/mode #channel +z<br />
<br />
==Extended Bans==<br />
Extended Bans are an extension of channel ban-matching modes which allow fine control over who can do what on your channel.<br />
<br />
Please see the [[Extended_Bans|Extended Bans documentation]] for more information.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Modes&diff=5154Channel Modes2011-03-17T18:05:24Z<p>MIXX941: Add channel mode +B</p>
<hr />
<div>Below is a full list of channel modes on MIXXnet and how they are used.<br />
<br />
In general, modes are set and removed in the following way:<br />
<br />
/mode #channel +<mode><br />
/mode #channel -<mode><br />
<br />
Examples of how to set each mode and their various parameters are provided below.<br />
<br />
==Basic Modes==<br />
===b (Ban)===<br />
Bans user from channel that matches the nick!ident@host hostmask. Can optionally redirect the banned user to a special channel if they attempt to join the channel while banned (see example 2 below).<br />
<br />
/mode #channel +b <nick!ident@host><br />
/mode #channel +b <nick!ident@host#bannedchannel><br />
<br />
===h (Halfop)===<br />
Gives <nickname> half-operator status on the channel<br />
<br />
/mode #channel +h <nickname><br />
<br />
===i (Invite Only)===<br />
Sets channel invite only. Users must be invited to join.<br />
<br />
/mode #channel +i<br />
<br />
===k (Channel Password)===<br />
Sets a channel password that users must have in order to join.<br />
<br />
/mode #channel +k <password><br />
<br />
===l (Channel Limit)===<br />
Sets a limit for the maximum numbers of users that can be on the channel at once.<br />
<br />
/mode #channel +l <limit><br />
<br />
===m (Moderated)===<br />
Sets channel to "moderated"; users must be voiced (+v) or higher to talk.<br />
<br />
/mode #channel +m<br />
<br />
===n (No External Messages)===<br />
Blocks external messages; users must be on the channel to talk. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +n<br />
<br />
===o (Channel Operator)===<br />
Gives <nickname> operator status on the channel. Requires channel operator status.<br />
<br />
/mode #channel +o <nickname<br />
<br />
===p (Private)===<br />
Sets channel as private; hides channel from user's WHOIS reply<br />
<br />
/mode #channel +p<br />
<br />
===s (Secret)===<br />
Sets channel as secret. This is the same as mode "p", however it also hides the channel from a /LIST<br />
<br />
/mode #channel +s<br />
<br />
===t (Topic Protection)===<br />
Makes it so only channel (half-)operators or higher can change the channel topic. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +t<br />
<br />
===v (Voice)===<br />
Gives voice to <nickname>. Requires half-operator status or higher.<br />
<br />
/mode #channel +v <nickname><br />
<br />
==Advanced Modes==<br />
<br />
===A (Allow Regular Users To Invite)===<br />
Allows regular, non-opped users to invite users to the channel using "/invite". As invites bypass channel bans, limits, and keys, '''setting this mode will allow regular users to invite anyone into the channel even if they are banned, do not have the channel key, or the channel limit has been exceeded. USE THIS MODE WITH CAUTION.'''<br />
<br />
===a (Protected User)===<br />
Gives protected status to <nickname>. Protected users cannot be kicked or deopped except by the channel founder or services. Channel mode +a does not give +o, so non operators can be protected with +a.<br />
<br />
/mode #channel +a <nickname><br />
<br />
===B (Block Caps)===<br />
Blocks messages to the channel that contain more than 50% of CAPITAL LETTERS.<br />
<br />
/mode #channel +B<br />
<br />
===e (Ban Exception)===<br />
Sets a ban exception on a nick!user@host hostmask. Users who match can still join the channel even if banned.<br />
<br />
/mode #channel +e <nick!user@host><br />
<br />
===c (Block Colors)===<br />
Blocks messages to the channel that contain colors.<br />
<br />
/mode #channel +c<br />
<br />
===C (No CTCP)===<br />
Blocks CTCP (PING, TIME, etc) to channels.<br />
<br />
/mode #channel +C<br />
<br />
===d (Delay Message)===<br />
Requires new users joining the channel to wait <sec> seconds before sending to the channel.<br />
<br />
/mode #channel +d <sec><br />
<br />
===f (Message Flood Protection)===<br />
Provides protection against message/notice flooding. When a user types more lines than <lines> in <sec> seconds, they will be kicked. If <lines> is prefixed with a *, the user will be kicked and banned.<br />
<br />
/mode #channel +f <lines>:<sec><br />
/mode #channel +f 5:10 (Kicks a user who says more than 5 lines in 10 seconds)<br />
/mode #channel +f *3:5 (Kicks and bans a user who says more than 3 lines in 5 seconds)<br />
<br />
===g (Channel Message Filter)===<br />
Manages the channel message filter which gives channels the ability to have custom words to block/filter. Words are added with "+g <word>" and removed with "-g <word>" (examples are below):<br />
<br />
/mode #channel +g abadword (Adds "abadword" to the channel filter)<br />
/mode #channel -g abadword (Removes "abadword" from the channel filter)<br />
/mode #channel +g (Shows all words on the channel filter)<br />
<br />
===G (Censor)===<br />
Filters out common swear words that are said in the channel. The message still goes through, however any swear words said are censored out.<br />
<br />
/mode #channel +G<br />
<br />
===H (Channel History)===<br />
Replays the last <lines> lines of channel activity within <sec> seconds to new users joining.<br />
<br />
/mode #channel +H <lines>:<sec><br />
<br />
===I (Invite Exception)===<br />
Allows users who match a nick!user@host hostmask to join the channel even if it is +i (invite only).<br />
<br />
/mode #channel +I <nick!user@host><br />
<br />
===j (Join Flood Protection)===<br />
Provides protection against join flooding. If there are more than <joins> joins in <sec> seconds, the channel will be locked for 60 seconds and new users will not be able to join for this time period. The lock can be removed before the 60 second time by unsetting and resetting +j. <br />
<br />
/mode #channel +j <joins>:<sec><br />
<br />
===J (Rejoin Prevention)===<br />
Prevents a user from rejoining the channel for <sec> seconds after being kicked.<br />
<br />
/mode #channel +J <sec><br />
<br />
===K (No Knocking)===<br />
Prevents users from doing a /KNOCK on an invite only (+i) channel.<br />
<br />
/mode #channel +K<br />
<br />
===L (Redirect When Full)===<br />
Redirects users to <channel> when the user limit (+l) has been reached on the current channel.<br />
<br />
/mode #channel +L <channel><br />
<br />
===M (Only Registered Users Talk)===<br />
Restricts users from talking on the channel unless they are registered and identified to [[NickServ]].<br />
<br />
/mode #channel +M<br />
<br />
===N (No Nick Changes)===<br />
Prevents users from changing their nicknames while in the channel.<br />
<br />
/mode #channel +N<br />
<br />
===P (Block Caps)===<br />
Blocks messages to the channel that are made up of mostly capital letters.<br />
<br />
/mode #channel +P<br />
<br />
===R (Only Registered Users Join)===<br />
Restricts users from joining the channel unless they are registered and identified to NickServ.<br />
<br />
/mode #channel +R<br />
<br />
===S (Strip Colors)===<br />
Strips colors from messages to the channel.<br />
<br />
/mode #channel +S<br />
<br />
===T (No Notices)===<br />
Prevents users from sending NOTICEs to the channel.<br />
<br />
/mode #channel +T<br />
<br />
===u (Auditorium Mode)===<br />
Provides an "auditorium mode" for the channel. When set, users will only see themselves and ops in the channel but will not see any other users in the userlist or any joins/parts/quits from other users.<br />
<br />
/mode #channel +u<br />
<br />
===x (Exception)===<br />
Allows users who match a nick!user@host hostmask to override ALL join restrictions such as +i/+l/+k/+b and join the channel no matter what.<br />
<br />
/mode #channel +x <nick!user@host><br />
<br />
===X (Exempt Channel Ops)===<br />
Allows channel operators of various ranks to be exempt from certain restrictions.<br />
<br />
/mode +X <mode>:<permission><br />
<br />
Valid modes/ranks are:<br />
<br />
* q - Founder<br />
* o - Operator<br />
* a - Protected<br />
* h - Halfop<br />
* v - voice<br />
<br />
Valid permissions are:<br />
<br />
* topiclock - Change the topic if +t is set<br />
* auditorium-vis - Be visible in a +u channel<br />
* auditorium-see - See full user list of a +u channel<br />
* blockcaps<br />
* blockcolor<br />
* censor<br />
* filter<br />
* flood<br />
* nickflood<br />
* noctcp<br />
* nonick<br />
* nonotice<br />
* regmoderated<br />
* stripcolor<br />
<br />
===z (SSL Users Only)===<br />
Requires all users on the channel to be connected to MIXXnet via [[SSL]]. Non-SSL users will not be allowed to join.<br />
<br />
/mode #channel +z<br />
<br />
==Extended Bans==<br />
Extended Bans are an extension of channel ban-matching modes which allow fine control over who can do what on your channel.<br />
<br />
Please see the [[Extended_Bans|Extended Bans documentation]] for more information.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Main_Page&diff=5153Main Page2011-03-15T21:32:25Z<p>MIXX941: Added user modes link</p>
<hr />
<div>Welcome to the MIXXnet Wiki. Here you will find user and staff contributed documents about [[MIXXnet]] and [[IRC]] in general. We encourage users to help out our documentation project by contributing information, however due to spam, editing can now only be done if you have registered and logged in.<br />
<br />
If you have any questions and need immediate help, log on to IRC: <br />
<br />
'''irc.mixxnet.net / #help'''<br />
<br />
You can use the search box to your left to search for articles that others have written or you can [[Special:Allpages|browse all articles]].<br />
<br />
== Getting Started ==<br />
Here are some articles that will help you get started on MIXXnet:<br />
<br />
* [[Channel_Start_Guide|Channel Start Guide - A complete guide to starting a channel]]<br />
* [[Channel_Modes|Channel Modes]]<br />
* [[User_Modes|User Modes]]<br />
* [[HostServ|vhost Information - Assign or remove a vhost on your nickname]]<br />
* [[SSL|SSL Information]]<br />
* [[IRC_client|Popular IRC Clients List]]<br />
* [[Proxy|Proxy policies and features]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=User_Modes&diff=5152User Modes2011-03-15T21:29:09Z<p>MIXX941: Initial creation</p>
<hr />
<div>Below is a list of user modes modes available on MIXXnet. Modes are set and removed in the following way:<br />
<br />
/mode nick +<mode><br />
/mode nick -<mode><br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
!scope="col"|Mode<br />
!scope="col"|Description<br />
|-<br />
|scope="row"|B<br />
|Marks user as being a bot.<br />
|-<br />
|scope="row"|c<br />
|Requires users to be in a common channel to send you a private message or notice.<br />
|-<br />
|scope="row"|G<br />
|Censors bad words out of incoming private messages/notices.<br />
|-<br />
|scope="row"|I<br />
|Hides channels you are in from your /whois output.<br />
|-<br />
|scope="row"|R<br />
|Allows only registered users to send you a private message/notice.<br />
|-<br />
|scope="row"|S<br />
|Strips colors and control codes from incoming private messages/notices.<br />
|}</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRCd_2.0_Upgrade&diff=5151IRCd 2.0 Upgrade2011-03-15T11:25:45Z<p>MIXX941: /* Introduction */ Add completion info</p>
<hr />
<div>==Introduction==<br />
MIXXnet is currently planning some major upgrades to our IRC server software. This article will outline our upgrade plans, testnet information, new features, and required actions by users as part of this upgrade.<br />
<br />
'''The upgrades were completed as scheduled on 2011-03-15.'''<br />
<br />
If you have any questions about this upgrade, please ask in #help and we will be glad to answer them.<br />
<br />
==New Features==<br />
There are many improvements under the hood as well as several new features that will be available as part of this upgrade. A short list of user-visible new features is below:<br />
<br />
* [[Extended Bans]]<br />
* Channel history mode - Channel mode "+H X:T" to replay last X lines to new users joining (T = max time to keep buffer)<br />
* Delay message mode - Channel mode "+d X" to require joiners to wait X seconds before sending to channel<br />
* Exempt ops mode - Channel mode +X; per-channel list of modes that do not enforce their limits on channel ops<br />
* Timed invites - Have invites expire after a set amount of time (/invite user #chan 60s)<br />
* IPv6 access will be restored as a software bug in the old IRCd version prevented us from offering IPv6<br />
<br />
==Switching Over==<br />
The switchover process itself will be quick with very little downtime. Less than a minute of complete downtime is expected while we restart servers with the new version. All services data (NickServ/ChanServ/HostServ/BotServ/MemoServ) will be carried over to the new version, however certain channel modes cannot be preserved across the upgrade.<br />
<br />
===Required User Actions===<br />
Due to the two major versions we are upgrading across, linking the old version to the new version to preserve channel modes/bans/exceptions is not possible. Channel operators will need to take a few steps in conjunction with this upgrade:<br />
<br />
* Note channel bans and re-apply them on the new server version. If you use ChanServ's AKICK or your own channel bot to manage your channel bans you will not need to do this, however if you use channel mode +b (or +e) you will need to make a list of channel bans and reapply them. You can get a channel's banlist by typing "/mode #channel +b".<br />
* Re-apply channel modes like keys (+k), limits and redirects (+l and +L), invite only (+i), secret (+s), private (+p), etc. This can also be done with ChanServ by setting MLOCK for your modes on the current production network.<br />
<br />
Manually performing these tasks should not be required when upgrading in the future as the IRCd now supports backwards linking to previous versions which would transfer this data automatically.<br />
<br />
==Test Network==<br />
A fully functional test network is currently up and running, and we invite interested users to connect, test things out, and let us know of any issues so they can be addressed before the upgrade is performed.<br />
<br />
'''You can connect to the test network now using the following info:<br />
<br />
irc.mixxnet.net<br />
<br />
Ports: 6659 (plain text), 6699 (SSL)<br />
<br />
You must use one of the above two ports to get to the testnet; any other ports may bring you to the current network or not work at all.'''<br />
<br />
Please keep in mind that this is a test network and we may need to make modifications which could require us to restart servers or services.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Start_Guide&diff=5150Channel Start Guide2011-03-15T11:23:22Z<p>MIXX941: Add extended bans link</p>
<hr />
<div>The following is a guide to setting up your own channel on [[MIXXnet]] and protecting it with [[services]]. <br />
<br />
===Step 1: Creating The Channel===<br />
The first step in creating a [[channel]] is to join it first. While you're on [[IRC]], type "/join #yourchannel" without quotes and replace "#yourchannel" with the channel you want to create. If the channel is empty or unregistered, you will become an [[op]] (@) in that channel.<br />
<br />
===Step 2: Registering with ChanServ===<br />
In order for you to be the owner of the channel and have full privileges on it, you must register it with [[ChanServ]]. This is a very easy process, however it requires a registered [[nickname]]. If you have not already registered a nickname, see the [[NickServ]] documents for instructions on how to do that. <br />
<br />
To register a channel, type the following command into your [[IRC client]]:<br />
<br />
'''/msg chanserv register #channelname password description'''<br />
<br />
Replace "#channelname", "password", and "description" with the channel you are registering, the founder password you wish to have, and the description of your channel.<br />
<br />
If you have succeeded, you will see something like this:<br />
<br />
-ChanServ- Channel #channelname registered under your nickname: YourNick<br />
-ChanServ- Your channel password is test - remember it for later use.<br />
--- ChanServ sets mode +n #channelname<br />
--- ChanServ sets mode +t #channelname<br />
--- ChanServ sets mode +r #channelname<br />
<br />
Now most likely you will want to set the topic, give people access, and perform other channel maintenance tasks. Here are some common channel commands and what they do:<br />
<br />
===Channel Modes===<br />
For a complete list of all channel modes available on MIXXnet, please see the [[Channel_Modes|Channel Modes]] and [[Extended_Bans|Extended Bans]] articles. Below is a summary of basic channel modes:<br />
<br />
* /topic #channelname New Topic - This will set the topic of your channel to whatever you wish.<br />
<br />
* /mode #channelname +o nickname - This will op the person with the nickname "nickname".<br />
<br />
* /mode #channelname +h nickname - This will give channel-half operator status to the person with the nickname "nickname".<br />
<br />
* /mode #channelname +v nickname - This will give voice to the person with the nickname "nickname".<br />
<br />
* /mode #channelname +b user@host - This will ban that user/host mask from your channel.<br />
<br />
* /mode #channelname +s - This will make your room secret, and not show up when someone does a /list.<br />
<br />
* /mode #channelname +p - This will make your channel private.<br />
<br />
* /mode #channelname +i - This will make your channel "Invite-Only". This means you must "/invite nickname" for them to be able to enter your channel.<br />
<br />
* /mode #channelname +k yoursecretkey - This will set your channel's "key" (or password). Replace "yoursecretkey" with the key you want to set.<br />
<br />
* /mode #channelname +m - This will make your channel "Moderated". This means that only people with a voice (+v) or higher (such as an op) can speak in the channel.<br />
<br />
* /mode #channelname +N - This disallows nickname changes while in your channel.<br />
<br />
===ChanServ Modes===<br />
* AutoOP (aop) - This user will be able to kick/ban and can set almost any channel mode, but does not have access to any ChanServ commands (such as adding/deleting people from access lists, using the "akick" function, etc).<br />
<br />
* SuperOP (sop) - This user has full channel privileges. They can set almost any channel mode and can add/delete people from the ChanServ access lists. They can also use ChanServ to "AutoKick" (akick) and ban a user.<br />
<br />
* HalfOP (hop) - This user can kick and ban regular and voiced users. They cannot kick or ban ops.<br />
<br />
* Voice (vop) - This user can speak in channels with +m set, but has no channel moderation features. There is no benefit to having voice in an unmoderated channel.<br />
<br />
===ChanServ Channel Commands===<br />
* /msg chanserv aop #channel add nickname - This will add "nickname" to the channel auto-op list.<br />
<br />
* /msg chanserv sop #channel add nickname - This will add "nickname" to the channel super-op list.<br />
<br />
* /msg chanserv hop #channel add nickname - This will add "nickname" to the channel half-op list.<br />
<br />
* /msg chanserv vop #channel add nickname - This will add "nickname" to the channel auto-voice list.<br />
<br />
* /msg chanserv *op #channel del nickname - This will delete "nickname" from the *op access list. Replace "*op" with either "hop", "aop", "sop", "vop".<br />
<br />
[[Category:Services]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IPv6&diff=5149IPv62011-03-15T07:22:07Z<p>MIXX941: Fix IPv6 address</p>
<hr />
<div>'''IPv6''' stands for Internet Protocol version 6. [[MIXXnet]] currently has one server that supports IPv6. <br />
<br />
You can connect to MIXXnet via IPv6 by using the main round robin: '''irc.mixxnet.net'''<br />
<br />
==External Links==<br />
* [http://en.wikipedia.org/wiki/IPv6 IPv6 at Wikipedia]<br />
<br />
{{stub}}</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Modes&diff=5148Channel Modes2011-03-15T01:02:27Z<p>MIXX941: Update with new modes for IRCd 2.0 upgrade</p>
<hr />
<div>Below is a full list of channel modes on MIXXnet and how they are used.<br />
<br />
In general, modes are set and removed in the following way:<br />
<br />
/mode #channel +<mode><br />
/mode #channel -<mode><br />
<br />
Examples of how to set each mode and their various parameters are provided below.<br />
<br />
==Basic Modes==<br />
===b (Ban)===<br />
Bans user from channel that matches the nick!ident@host hostmask. Can optionally redirect the banned user to a special channel if they attempt to join the channel while banned (see example 2 below).<br />
<br />
/mode #channel +b <nick!ident@host><br />
/mode #channel +b <nick!ident@host#bannedchannel><br />
<br />
===h (Halfop)===<br />
Gives <nickname> half-operator status on the channel<br />
<br />
/mode #channel +h <nickname><br />
<br />
===i (Invite Only)===<br />
Sets channel invite only. Users must be invited to join.<br />
<br />
/mode #channel +i<br />
<br />
===k (Channel Password)===<br />
Sets a channel password that users must have in order to join.<br />
<br />
/mode #channel +k <password><br />
<br />
===l (Channel Limit)===<br />
Sets a limit for the maximum numbers of users that can be on the channel at once.<br />
<br />
/mode #channel +l <limit><br />
<br />
===m (Moderated)===<br />
Sets channel to "moderated"; users must be voiced (+v) or higher to talk.<br />
<br />
/mode #channel +m<br />
<br />
===n (No External Messages)===<br />
Blocks external messages; users must be on the channel to talk. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +n<br />
<br />
===o (Channel Operator)===<br />
Gives <nickname> operator status on the channel. Requires channel operator status.<br />
<br />
/mode #channel +o <nickname<br />
<br />
===p (Private)===<br />
Sets channel as private; hides channel from user's WHOIS reply<br />
<br />
/mode #channel +p<br />
<br />
===s (Secret)===<br />
Sets channel as secret. This is the same as mode "p", however it also hides the channel from a /LIST<br />
<br />
/mode #channel +s<br />
<br />
===t (Topic Protection)===<br />
Makes it so only channel (half-)operators or higher can change the channel topic. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +t<br />
<br />
===v (Voice)===<br />
Gives voice to <nickname>. Requires half-operator status or higher.<br />
<br />
/mode #channel +v <nickname><br />
<br />
==Advanced Modes==<br />
<br />
===A (Allow Regular Users To Invite)===<br />
Allows regular, non-opped users to invite users to the channel using "/invite". As invites bypass channel bans, limits, and keys, '''setting this mode will allow regular users to invite anyone into the channel even if they are banned, do not have the channel key, or the channel limit has been exceeded. USE THIS MODE WITH CAUTION.'''<br />
<br />
===a (Protected User)===<br />
Gives protected status to <nickname>. Protected users cannot be kicked or deopped except by the channel founder or services. Channel mode +a does not give +o, so non operators can be protected with +a.<br />
<br />
/mode #channel +a <nickname><br />
<br />
===e (Ban Exception)===<br />
Sets a ban exception on a nick!user@host hostmask. Users who match can still join the channel even if banned.<br />
<br />
/mode #channel +e <nick!user@host><br />
<br />
===c (Block Colors)===<br />
Blocks messages to the channel that contain colors.<br />
<br />
/mode #channel +c<br />
<br />
===C (No CTCP)===<br />
Blocks CTCP (PING, TIME, etc) to channels.<br />
<br />
/mode #channel +C<br />
<br />
===d (Delay Message)===<br />
Requires new users joining the channel to wait <sec> seconds before sending to the channel.<br />
<br />
/mode #channel +d <sec><br />
<br />
===f (Message Flood Protection)===<br />
Provides protection against message/notice flooding. When a user types more lines than <lines> in <sec> seconds, they will be kicked. If <lines> is prefixed with a *, the user will be kicked and banned.<br />
<br />
/mode #channel +f <lines>:<sec><br />
/mode #channel +f 5:10 (Kicks a user who says more than 5 lines in 10 seconds)<br />
/mode #channel +f *3:5 (Kicks and bans a user who says more than 3 lines in 5 seconds)<br />
<br />
===g (Channel Message Filter)===<br />
Manages the channel message filter which gives channels the ability to have custom words to block/filter. Words are added with "+g <word>" and removed with "-g <word>" (examples are below):<br />
<br />
/mode #channel +g abadword (Adds "abadword" to the channel filter)<br />
/mode #channel -g abadword (Removes "abadword" from the channel filter)<br />
/mode #channel +g (Shows all words on the channel filter)<br />
<br />
===G (Censor)===<br />
Filters out common swear words that are said in the channel. The message still goes through, however any swear words said are censored out.<br />
<br />
/mode #channel +G<br />
<br />
===H (Channel History)===<br />
Replays the last <lines> lines of channel activity within <sec> seconds to new users joining.<br />
<br />
/mode #channel +H <lines>:<sec><br />
<br />
===I (Invite Exception)===<br />
Allows users who match a nick!user@host hostmask to join the channel even if it is +i (invite only).<br />
<br />
/mode #channel +I <nick!user@host><br />
<br />
===j (Join Flood Protection)===<br />
Provides protection against join flooding. If there are more than <joins> joins in <sec> seconds, the channel will be locked for 60 seconds and new users will not be able to join for this time period. The lock can be removed before the 60 second time by unsetting and resetting +j. <br />
<br />
/mode #channel +j <joins>:<sec><br />
<br />
===J (Rejoin Prevention)===<br />
Prevents a user from rejoining the channel for <sec> seconds after being kicked.<br />
<br />
/mode #channel +J <sec><br />
<br />
===K (No Knocking)===<br />
Prevents users from doing a /KNOCK on an invite only (+i) channel.<br />
<br />
/mode #channel +K<br />
<br />
===L (Redirect When Full)===<br />
Redirects users to <channel> when the user limit (+l) has been reached on the current channel.<br />
<br />
/mode #channel +L <channel><br />
<br />
===M (Only Registered Users Talk)===<br />
Restricts users from talking on the channel unless they are registered and identified to [[NickServ]].<br />
<br />
/mode #channel +M<br />
<br />
===N (No Nick Changes)===<br />
Prevents users from changing their nicknames while in the channel.<br />
<br />
/mode #channel +N<br />
<br />
===P (Block Caps)===<br />
Blocks messages to the channel that are made up of mostly capital letters.<br />
<br />
/mode #channel +P<br />
<br />
===R (Only Registered Users Join)===<br />
Restricts users from joining the channel unless they are registered and identified to NickServ.<br />
<br />
/mode #channel +R<br />
<br />
===S (Strip Colors)===<br />
Strips colors from messages to the channel.<br />
<br />
/mode #channel +S<br />
<br />
===T (No Notices)===<br />
Prevents users from sending NOTICEs to the channel.<br />
<br />
/mode #channel +T<br />
<br />
===u (Auditorium Mode)===<br />
Provides an "auditorium mode" for the channel. When set, users will only see themselves and ops in the channel but will not see any other users in the userlist or any joins/parts/quits from other users.<br />
<br />
/mode #channel +u<br />
<br />
===x (Exception)===<br />
Allows users who match a nick!user@host hostmask to override ALL join restrictions such as +i/+l/+k/+b and join the channel no matter what.<br />
<br />
/mode #channel +x <nick!user@host><br />
<br />
===X (Exempt Channel Ops)===<br />
Allows channel operators of various ranks to be exempt from certain restrictions.<br />
<br />
/mode +X <mode>:<permission><br />
<br />
Valid modes/ranks are:<br />
<br />
* q - Founder<br />
* o - Operator<br />
* a - Protected<br />
* h - Halfop<br />
* v - voice<br />
<br />
Valid permissions are:<br />
<br />
* topiclock - Change the topic if +t is set<br />
* auditorium-vis - Be visible in a +u channel<br />
* auditorium-see - See full user list of a +u channel<br />
* blockcaps<br />
* blockcolor<br />
* censor<br />
* filter<br />
* flood<br />
* nickflood<br />
* noctcp<br />
* nonick<br />
* nonotice<br />
* regmoderated<br />
* stripcolor<br />
<br />
===z (SSL Users Only)===<br />
Requires all users on the channel to be connected to MIXXnet via [[SSL]]. Non-SSL users will not be allowed to join.<br />
<br />
/mode #channel +z<br />
<br />
==Extended Bans==<br />
Extended Bans are an extension of channel ban-matching modes which allow fine control over who can do what on your channel.<br />
<br />
Please see the [[Extended_Bans|Extended Bans documentation]] for more information.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=User_talk:Regtest&diff=5147User talk:Regtest2011-03-12T22:46:14Z<p>MIXX941: Welcome!</p>
<hr />
<div>'''Welcome to ''MIXXnet Wiki''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [[Help:Contents|help pages]].<br />
Again, welcome and have fun! [[User:MIXX941|MIXX941]] 16:46, 12 March 2011 (CST)</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRCd_2.0_Upgrade&diff=5146IRCd 2.0 Upgrade2011-03-12T21:57:44Z<p>MIXX941: Add note about services data and fix a couple typos</p>
<hr />
<div>==Introduction==<br />
MIXXnet is currently planning some major upgrades to our IRC server software. This article will outline our upgrade plans, testnet information, new features, and required actions by users as part of this upgrade.<br />
<br />
'''The upgrade is currently scheduled for Tuesday March 15, 2011 at 1:00 AM Eastern USA time / 05:00 GMT / 06:00 CET.'''<br />
<br />
If you have any questions about this upgrade, please ask in #help and we will be glad to answer them.<br />
<br />
==New Features==<br />
There are many improvements under the hood as well as several new features that will be available as part of this upgrade. A short list of user-visible new features is below:<br />
<br />
* [[Extended Bans]]<br />
* Channel history mode - Channel mode "+H X:T" to replay last X lines to new users joining (T = max time to keep buffer)<br />
* Delay message mode - Channel mode "+d X" to require joiners to wait X seconds before sending to channel<br />
* Exempt ops mode - Channel mode +X; per-channel list of modes that do not enforce their limits on channel ops<br />
* Timed invites - Have invites expire after a set amount of time (/invite user #chan 60s)<br />
* IPv6 access will be restored as a software bug in the old IRCd version prevented us from offering IPv6<br />
<br />
==Switching Over==<br />
The switchover process itself will be quick with very little downtime. Less than a minute of complete downtime is expected while we restart servers with the new version. All services data (NickServ/ChanServ/HostServ/BotServ/MemoServ) will be carried over to the new version, however certain channel modes cannot be preserved across the upgrade.<br />
<br />
===Required User Actions===<br />
Due to the two major versions we are upgrading across, linking the old version to the new version to preserve channel modes/bans/exceptions is not possible. Channel operators will need to take a few steps in conjunction with this upgrade:<br />
<br />
* Note channel bans and re-apply them on the new server version. If you use ChanServ's AKICK or your own channel bot to manage your channel bans you will not need to do this, however if you use channel mode +b (or +e) you will need to make a list of channel bans and reapply them. You can get a channel's banlist by typing "/mode #channel +b".<br />
* Re-apply channel modes like keys (+k), limits and redirects (+l and +L), invite only (+i), secret (+s), private (+p), etc. This can also be done with ChanServ by setting MLOCK for your modes on the current production network.<br />
<br />
Manually performing these tasks should not be required when upgrading in the future as the IRCd now supports backwards linking to previous versions which would transfer this data automatically.<br />
<br />
==Test Network==<br />
A fully functional test network is currently up and running, and we invite interested users to connect, test things out, and let us know of any issues so they can be addressed before the upgrade is performed.<br />
<br />
'''You can connect to the test network now using the following info:<br />
<br />
irc.mixxnet.net<br />
<br />
Ports: 6659 (plain text), 6699 (SSL)<br />
<br />
You must use one of the above two ports to get to the testnet; any other ports may bring you to the current network or not work at all.'''<br />
<br />
Please keep in mind that this is a test network and we may need to make modifications which could require us to restart servers or services.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRCd_2.0_Upgrade&diff=5145IRCd 2.0 Upgrade2011-03-12T21:40:23Z<p>MIXX941: Updated Europe times for US DST</p>
<hr />
<div>==Introduction==<br />
MIXXnet is currently planning some major upgrades to our IRC server software. This article will outline our upgrade plans, testnet information, new features, and required actions by users as part of this upgrade.<br />
<br />
'''The upgrade is currently scheduled for Tuesday March 15, 2011 at 1:00 AM Eastern USA time / 05:00 GMT / 06:00 CET.'''<br />
<br />
If you have any questions about this upgrade, please ask in #help and we will be glad to answer them.<br />
<br />
==New Features==<br />
There are many improvements under the hood as well as several new features that will be available as part of this upgrade. A short list of user-visible new features is below:<br />
<br />
* [[Extended Bans]]<br />
* Channel history mode - Channel mode "+H X:T" to replay last X lines to new users joining (T = max time to keep buffer)<br />
* Delay message mode - Channel mode "+d X" to require joiners to wait X seconds before sending to channel<br />
* Exempt ops mode - Channel mode +X; per-channel list of modes that do not enforce their limits on channel ops<br />
* Timed invites - Have invites expire after a set amount of time (/invite user #chan 60s)<br />
* IPv6 access will be restored as a software bug in the old IRCd version prevented us from offering IPv6<br />
<br />
==Switching Over==<br />
The switchover process itself will be quick with very little downtime. Less than a minute of complete downtime is expected while we restart servers with the new version.<br />
<br />
===Required User Actions===<br />
Due to the two major versions we are upgrading across, linking the old version to the new version to preserve channel modes/bans bans is not possible. Channel operators will need to take a few steps in conjunction with this upgrade:<br />
<br />
* Note channel bans and re-apply them on the new server version. If you use ChanServ's AKICK or your own channel bot to manage your channel bans you will not need to do this, however if you use channel mode +b you will need to make a list of channel bans and reapply them. You can get a channel's banlist by typing "/mode #channel +b".<br />
* Re-apply channel modes like keys (+k), limits and redirects (+l and +L), invite only (+i), secret (+s), private (+p), etc. This can also be done with ChanServ by setting MLOCK for your modes on the current production network.<br />
<br />
Manually performing these tasks should not be required when upgrading in the future as the IRCd now supports backwards linking to previous versions which would transfer this data automatically.<br />
<br />
==Test Network==<br />
A fully functional test network is currently up and running, and we invite interested users to connect, test things out, and let us know of any issues so they can be addressed before the upgrade is performed.<br />
<br />
'''You can connect to the test network now using the following info:<br />
<br />
irc.mixxnet.net<br />
<br />
Ports: 6659 (plain text), 6699 (SSL)<br />
<br />
You must use one of the above two ports to get to the testnet; any other ports may bring you to the current network or not work at all.'''<br />
<br />
Please keep in mind that this is a test network and we may need to make modifications which could require us to restart servers or services.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Extended_Bans&diff=5139Extended Bans2011-03-09T21:25:06Z<p>MIXX941: A couple tweaks on examples</p>
<hr />
<div>Extended Bans are an extension of channel ban-matching modes which allow fine control over who can do what on your channel.<br />
<br />
==Matching Extended Bans==<br />
These extbans extend the regular +b, +e, and +I channel modes to allow for matching on other criteria, and are applied like so:<br />
<br />
<br />
/mode +b <extban> - Bans based on extban<br />
<br />
/mode +e <extban> - Adds an exception based on extban<br />
<br />
/mode +I <extban> - Allows matching users to join a +i channel<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
!scope="col"|Extended Ban<br />
!scope="col"|Description<br />
!scope="col"|Example<br />
|-<br />
|scope="row"|j:[state][#channel]<br />
|Matches if the user is also on the specified channel.<br />
|/mode +b j:#badchan<br />
/mode +b j:@#badchan (Matches ops on #badchan)<br />
|-<br />
|scope="row"|r:[gecos]<br />
|Matches against a real name (GECOS) field.<br />
|/mode +b r:BadBot<br />
|-<br />
|scope="row"|R:[account]<br />
|Matches registered nicks that are registered to an account.<br />
|/mode +b R:BadUser<br />
|}<br />
<br />
==Acting Extended Bans==<br />
Modes that restrict certain channel activity also have corresponding extended bans so they can be applied to certain users only. They are applied with channel modes +b and +e in the regular hostmask syntax of nick!user@host.<br />
<br />
<br />
/mode +b <extban>:<mask> - Blocks users matching the mask from performing the specified activity<br />
<br />
/mode +e <extban>:<mask> - Allows users matching the mask to perform the specified activity<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
!scope="col"|Extended Ban<br />
!scope="col"|Description<br />
!scope="col"|Example<br />
|-<br />
|scope="row"|A:[mask]<br />
|Blocks user from using /invite.<br />
|/mode +b A:*!*@bad.hostname.example.com<br />
|-<br />
|scope="row"|B:[mask]<br />
|Blocks user from using ALL CAPS.<br />
|/mode +b A:*!*@bad.hostname.example.com<br />
|-<br />
|scope="row"|c:[mask]<br />
|Blocks colors from matching users.<br />
|/mode +b c:*!*@excessive.color.user.example.com<br />
|-<br />
|scope="row"|C:[mask]<br />
|Blocks CTCPs from matching users.<br />
|/mode +b C:*!*@bad.hostname.example.com<br />
|-<br />
|scope="row"|m:[mask]<br />
|Blocks messages to the channel from matching users (like channel mode +m).<br />
|/mode +b m:*!*@bad.hostname.example.com<br />
|-<br />
|scope="row"|N:[mask]<br />
|Prevents matching users from changing their nickname while in the channel.<br />
|/mode +b m:*!*@bad.hostname.example.com<br />
|-<br />
|scope="row"|p:[mask]<br />
|Blocks part messages from matching users.<br />
|/mode +b p:*!*@bad.hostname.example.com<br />
|-<br />
|scope="row"|Q:[mask]<br />
|Prevents matching users from being kicked from the channel.<br />
|/mode +b Q:*!*@important.user.example.com<br />
|-<br />
|scope="row"|S:[mask]<br />
|Strips colors from messages by matching users.<br />
|/mode +b S:*!*@excessive.color.user.example.com<br />
|-<br />
|scope="row"|T:[mask]<br />
|Prevents matching users from sending NOTICEs to the channel.<br />
|/mode +b T:*!*@bad.hostname.example.com<br />
|}<br />
<br />
==Stacking==<br />
Extended bans can also be stacked. For example:<br />
<br />
/mode +b S:r:*mirc* - Strips colors from messages by anyone with "mirc" in their real name/GECOS.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRCd_2.0_Upgrade&diff=5136IRCd 2.0 Upgrade2011-03-09T12:42:30Z<p>MIXX941: </p>
<hr />
<div>==Introduction==<br />
MIXXnet is currently planning some major upgrades to our IRC server software. This article will outline our upgrade plans, testnet information, new features, and required actions by users as part of this upgrade.<br />
<br />
'''The upgrade is currently scheduled for Tuesday March 15, 2011 at 1:00 AM Eastern USA time / 06:00 GMT / 07:00 CET.'''<br />
<br />
If you have any questions about this upgrade, please ask in #help and we will be glad to answer them.<br />
<br />
==New Features==<br />
There are many improvements under the hood as well as several new features that will be available as part of this upgrade. A short list of user-visible new features is below:<br />
<br />
* [[Extended Bans]]<br />
* Channel history mode - Channel mode "+H X:T" to replay last X lines to new users joining (T = max time to keep buffer)<br />
* Delay message mode - Channel mode "+d X" to require joiners to wait X seconds before sending to channel<br />
* Exempt ops mode - Channel mode +X; per-channel list of modes that do not enforce their limits on channel ops<br />
* Timed invites - Have invites expire after a set amount of time (/invite user #chan 60s)<br />
* IPv6 access will be restored as a software bug in the old IRCd version prevented us from offering IPv6<br />
<br />
==Switching Over==<br />
The switchover process itself will be quick with very little downtime. Less than a minute of complete downtime is expected while we restart servers with the new version.<br />
<br />
===Required User Actions===<br />
Due to the two major versions we are upgrading across, linking the old version to the new version to preserve channel modes/bans bans is not possible. Channel operators will need to take a few steps in conjunction with this upgrade:<br />
<br />
* Note channel bans and re-apply them on the new server version. If you use ChanServ's AKICK or your own channel bot to manage your channel bans you will not need to do this, however if you use channel mode +b you will need to make a list of channel bans and reapply them. You can get a channel's banlist by typing "/mode #channel +b".<br />
* Re-apply channel modes like keys (+k), limits and redirects (+l and +L), invite only (+i), secret (+s), private (+p), etc. This can also be done with ChanServ by setting MLOCK for your modes on the current production network.<br />
<br />
Manually performing these tasks should not be required when upgrading in the future as the IRCd now supports backwards linking to previous versions which would transfer this data automatically.<br />
<br />
==Test Network==<br />
A fully functional test network is currently up and running, and we invite interested users to connect, test things out, and let us know of any issues so they can be addressed before the upgrade is performed.<br />
<br />
'''You can connect to the test network now using the following info:<br />
<br />
irc.mixxnet.net<br />
<br />
Ports: 6659 (plain text), 6699 (SSL)<br />
<br />
You must use one of the above two ports to get to the testnet; any other ports may bring you to the current network or not work at all.'''<br />
<br />
Please keep in mind that this is a test network and we may need to make modifications which could require us to restart servers or services.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRCd_2.0_Upgrade&diff=5134IRCd 2.0 Upgrade2011-03-08T22:42:55Z<p>MIXX941: </p>
<hr />
<div>==Introduction==<br />
MIXXnet is currently planning some major upgrades to our IRC server software. This article will outline our upgrade plans, testnet information, new features, and required actions by users as part of this upgrade.<br />
<br />
'''The upgrade is currently scheduled for Tuesday March 15, 2011 at 1:00 AM Eastern USA time / 6:00 AM GMT / 7:00 AM CET.'''<br />
<br />
==New Features==<br />
There are many improvements under the hood as well as several new features that will be available as part of this upgrade. A short list of user-visible new features is below:<br />
<br />
* [[Extended Bans]]<br />
* Channel history mode - Channel mode "+H X:T" to replay last X lines to new users joining (T = max time to keep buffer)<br />
* Delay message mode - Channel mode "+d X" to require joiners to wait X seconds before sending to channel<br />
* Exempt ops mode - Channel mode +X; per-channel list of modes that do not enforce their limits on channel ops<br />
* Timed invites - Have invites expire after a set amount of time (/invite user #chan 60s)<br />
* IPv6 access will be restored as a software bug in the old IRCd version prevented us from offering IPv6<br />
<br />
==Switching Over==<br />
The switchover process itself will be quick with very little downtime. Less than a minute of complete downtime is expected while we restart servers with the new version.<br />
<br />
===Required User Actions===<br />
Due to the two major versions we are upgrading across, linking the old version to the new version to preserve channel modes/bans bans is not possible. Channel operators will need to take a few steps in conjunction with this upgrade:<br />
<br />
* Note channel bans and re-apply them on the new server version. If you use ChanServ's AKICK or your own channel bot to manage your channel bans you will not need to do this, however if you use channel mode +b you will need to make a list of channel bans and reapply them. You can get a channel's banlist by typing "/mode #channel +b".<br />
* Re-apply channel modes like keys (+k), limits and redirects (+l and +L), invite only (+i), secret (+s), private (+p), etc. This can also be done with ChanServ by setting MLOCK for your modes on the current production network.<br />
<br />
Manually performing these tasks should not be required when upgrading in the future as the IRCd now supports backwards linking to previous versions which would transfer this data automatically.<br />
<br />
==Test Network==<br />
A fully functional test network is currently up and running, and we invite interested users to connect, test things out, and let us know of any issues so they can be addressed before the upgrade is performed.<br />
<br />
'''You can connect to the test network now using the following info:<br />
<br />
irc.mixxnet.net<br />
<br />
Ports: 6659 (plain text), 6699 (SSL)<br />
<br />
You must use one of the above two ports to get to the testnet; any other ports may bring you to the current network or not work at all.'''<br />
<br />
Please keep in mind that this is a test network and we may need to make modifications which could require us to restart servers or services.<br />
<br />
Please ask any questions or report any problems in #help.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRCd_2.0_Upgrade&diff=5131IRCd 2.0 Upgrade2011-03-08T22:29:41Z<p>MIXX941: Fix time</p>
<hr />
<div>==Introduction==<br />
MIXXnet is currently planning some major upgrades to our IRC server software. This article will outline our upgrade plans, testnet information, new features, and required actions by users as part of this upgrade.<br />
<br />
'''The upgrade is currently scheduled for Tuesday March 15, 2011 at 1:00 AM Eastern USA time / 6:00 AM GMT / 7:00 AM CET.'''<br />
<br />
==New Features==<br />
There are many improvements under the hood as well as several new features that will be available as part of this upgrade. A short list of user-visible new features is below:<br />
<br />
* [[Extended Bans]]<br />
* Channel history mode - Channel mode "+H X:T" to replay last X lines to new users joining (T = max time to keep buffer)<br />
* Delay message mode - Channel mode "+d X" to require joiners to wait X seconds before sending to channel<br />
* Exempt ops mode - Channel mode +X; per-channel list of modes that do not enforce their limits on channel ops<br />
* Timed invites - Have invites expire after a set amount of time (/invite user #chan 60s)<br />
* IPv6 access will be restored as a software bug in the old IRCd version prevented us from offering IPv6<br />
<br />
==Switching Over==<br />
The switchover process itself will be quick with very little downtime. Less than a minute of complete downtime is expected while we restart servers with the new version.<br />
<br />
===Required User Actions===<br />
Due to the two major versions we are upgrading across, linking the old version to the new version to preserve channel modes/bans bans is not possible. Channel operators will need to take a few steps in conjunction with this upgrade:<br />
<br />
* Note channel bans and re-apply them on the new server version. If you use ChanServ's AKICK or your own channel bot to manage your channel bans you will not need to do this, however if you use channel mode +b you will need to make a list of channel bans and reapply them. You can get a channel's banlist by typing "/mode #channel +b".<br />
* Re-apply channel modes like keys (+k), limits and redirects (+l and +L), invite only (+i), secret (+s), private (+p), etc. This can also be done with ChanServ by setting MLOCK for your modes on the current production network.<br />
<br />
Manually performing these tasks should not be required when upgrading in the future as the IRCd now supports backwards linking to previous versions which would transfer this data automatically.<br />
<br />
==Test Network==<br />
A fully functional test network is currently up and running, and we invite interested users to connect, test things out, and let us know of any issues so they can be addressed before the upgrade is performed.<br />
<br />
'''You can connect to the test network now using the following info:<br />
<br />
irc.mixxnet.net<br />
<br />
Ports: 6659 (plain text), 6699 (SSL)<br />
<br />
You must use one of the above two ports to get to the testnet; any other ports may bring you to the current network or not work at all.'''<br />
<br />
Please keep in mind that this is a test network and we may need to make modifications which could require us to restart servers or services. Also, our testnet pool of servers consists of ALL MIXXnet's leaves and may not be constantly optimized based on performance or stability like our main pool.<br />
<br />
Please ask any questions or report any problems in #help.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRCd_2.0_Upgrade&diff=5130IRCd 2.0 Upgrade2011-03-08T22:29:21Z<p>MIXX941: Initial creation</p>
<hr />
<div>==Introduction==<br />
MIXXnet is currently planning some major upgrades to our IRC server software. This article will outline our upgrade plans, testnet information, new features, and required actions by users as part of this upgrade.<br />
<br />
'''The upgrade is currently scheduled for Tuesday March 15, 2011 at 1:00 AM Eastern USA time / 7:00 AM GMT / 8:00 AM CET.'''<br />
<br />
==New Features==<br />
There are many improvements under the hood as well as several new features that will be available as part of this upgrade. A short list of user-visible new features is below:<br />
<br />
* [[Extended Bans]]<br />
* Channel history mode - Channel mode "+H X:T" to replay last X lines to new users joining (T = max time to keep buffer)<br />
* Delay message mode - Channel mode "+d X" to require joiners to wait X seconds before sending to channel<br />
* Exempt ops mode - Channel mode +X; per-channel list of modes that do not enforce their limits on channel ops<br />
* Timed invites - Have invites expire after a set amount of time (/invite user #chan 60s)<br />
* IPv6 access will be restored as a software bug in the old IRCd version prevented us from offering IPv6<br />
<br />
==Switching Over==<br />
The switchover process itself will be quick with very little downtime. Less than a minute of complete downtime is expected while we restart servers with the new version.<br />
<br />
===Required User Actions===<br />
Due to the two major versions we are upgrading across, linking the old version to the new version to preserve channel modes/bans bans is not possible. Channel operators will need to take a few steps in conjunction with this upgrade:<br />
<br />
* Note channel bans and re-apply them on the new server version. If you use ChanServ's AKICK or your own channel bot to manage your channel bans you will not need to do this, however if you use channel mode +b you will need to make a list of channel bans and reapply them. You can get a channel's banlist by typing "/mode #channel +b".<br />
* Re-apply channel modes like keys (+k), limits and redirects (+l and +L), invite only (+i), secret (+s), private (+p), etc. This can also be done with ChanServ by setting MLOCK for your modes on the current production network.<br />
<br />
Manually performing these tasks should not be required when upgrading in the future as the IRCd now supports backwards linking to previous versions which would transfer this data automatically.<br />
<br />
==Test Network==<br />
A fully functional test network is currently up and running, and we invite interested users to connect, test things out, and let us know of any issues so they can be addressed before the upgrade is performed.<br />
<br />
'''You can connect to the test network now using the following info:<br />
<br />
irc.mixxnet.net<br />
<br />
Ports: 6659 (plain text), 6699 (SSL)<br />
<br />
You must use one of the above two ports to get to the testnet; any other ports may bring you to the current network or not work at all.'''<br />
<br />
Please keep in mind that this is a test network and we may need to make modifications which could require us to restart servers or services. Also, our testnet pool of servers consists of ALL MIXXnet's leaves and may not be constantly optimized based on performance or stability like our main pool.<br />
<br />
Please ask any questions or report any problems in #help.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Extended_Bans&diff=5129Extended Bans2011-03-08T22:24:11Z<p>MIXX941: Add stacking section and a couple examples</p>
<hr />
<div>Extended Bans are an extension of channel ban-matching modes which allow fine control over who can do what on your channel.<br />
<br />
==Matching Extended Bans==<br />
These extbans extend the regular +b, +e, and +I channel modes to allow for matching on other criteria, and are applied like so:<br />
<br />
<br />
/mode +b <extban> - Bans based on extban<br />
<br />
/mode +e <extban> - Adds an exception based on extban<br />
<br />
/mode +I <extban> - Allows matching users to join a +i channel<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
!scope="col"|Extended Ban<br />
!scope="col"|Description<br />
!scope="col"|Example<br />
|-<br />
|scope="row"|j:[state][#channel]<br />
|Matches if the user is also on the specified channel.<br />
|/mode +b j:#badchan<br />
/mode +b j:@#badchan (Matches ops on #badchan)<br />
|-<br />
|scope="row"|r:[gecos]<br />
|Matches against a real name (GECOS) field.<br />
|/mode +b r:BadBot<br />
|-<br />
|scope="row"|R:[account]<br />
|Matches registered nicks that are registered to an account.<br />
|/mode +b R:BadUser<br />
|}<br />
<br />
==Acting Extended Bans==<br />
Modes that restrict certain channel activity also have corresponding extended bans so they can be applied to certain users only. They are applied with channel modes +b and +e in the regular hostmask syntax of nick!user@host.<br />
<br />
<br />
/mode +b <extban>:<mask> - Blocks users matching the mask from performing the specified activity<br />
<br />
/mode +e <extban>:<mask> - Allows users matching the mask to perform the specified activity<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
!scope="col"|Extended Ban<br />
!scope="col"|Description<br />
!scope="col"|Example<br />
|-<br />
|scope="row"|A:[mask]<br />
|Blocks user from using /invite.<br />
|/mode +b A:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|B:[mask]<br />
|Blocks user from using ALL CAPS.<br />
|/mode +b A:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|c:[mask]<br />
|Blocks colors from matching users.<br />
|/mode +b c:*!*@excessive.color.user.name.example.com<br />
|-<br />
|scope="row"|C:[mask]<br />
|Blocks CTCPs from matching users.<br />
|/mode +b C:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|m:[mask]<br />
|Blocks messages to the channel from matching users (like channel mode +m).<br />
|/mode +b m:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|N:[mask]<br />
|Prevents matching users from changing their nickname while in the channel.<br />
|/mode +b m:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|p:[mask]<br />
|Blocks part messages from matching users.<br />
|/mode +b p:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|Q:[mask]<br />
|Prevents matching users from being kicked from the channel.<br />
|/mode +b Q:*!*@important.user.example.com<br />
|-<br />
|scope="row"|S:[mask]<br />
|Strips colors from messages by matching users.<br />
|/mode +b S:*!*@excessive.color.user.example.com<br />
|-<br />
|scope="row"|T:[mask]<br />
|Prevents matching users from sending NOTICEs to the channel.<br />
|/mode +b T:*!*@bad.host.name.example.com<br />
|}<br />
<br />
==Stacking==<br />
Extended bans can also be stacked. For example:<br />
<br />
/mode +b S:r:*mirc* - Strips colors from messages by anyone with "mirc" in their real name/GECOS.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Extended_Bans&diff=5128Extended Bans2011-03-08T22:17:00Z<p>MIXX941: Initial creation</p>
<hr />
<div>Extended Bans are an extension of channel ban-matching modes which allow fine control over who can do what on your channel.<br />
<br />
==Matching Extended Bans==<br />
These extbans extend the regular +b and +e channel modes to allow for matching on other criteria, and are applied like so:<br />
<br />
<br />
/mode +b <extban> - Bans based on extban<br />
<br />
/mode +e <extban> - Adds an exception based on extban<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
!scope="col"|Extended Ban<br />
!scope="col"|Description<br />
!scope="col"|Example<br />
|-<br />
|scope="row"|j:[state][#channel]<br />
|Matches if the user is also on the specified channel.<br />
|/mode +b j:#badchan<br />
/mode +b j:@#badchan (Matches ops on #badchan)<br />
|-<br />
|scope="row"|r:[gecos]<br />
|Matches against a real name (GECOS) field.<br />
|/mode +b r:BadBot<br />
|-<br />
|scope="row"|R:[account]<br />
|Matches registered nicks that are registered to an account.<br />
|/mode +b R:BadUser<br />
|}<br />
<br />
==Acting Extended Bans==<br />
Modes that restrict certain channel activity also have corresponding extended bans so they can be applied to certain users only. They are applied with channel modes +b and +e in the regular hostmask syntax of nick!user@host.<br />
<br />
<br />
/mode +b <extban>:<mask> - Blocks users matching the mask from performing the specified activity<br />
<br />
/mode +e <extban>:<mask> - Allows users matching the mask to perform the specified activity.<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
!scope="col"|Extended Ban<br />
!scope="col"|Description<br />
!scope="col"|Example<br />
|-<br />
|scope="row"|A:[mask]<br />
|Blocks user from using /invite.<br />
|/mode +b A:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|B:[mask]<br />
|Blocks user from using ALL CAPS.<br />
|/mode +b A:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|c:[mask]<br />
|Blocks colors from matching users.<br />
|/mode +b c:*!*@excessive.color.user.name.example.com<br />
|-<br />
|scope="row"|C:[mask]<br />
|Blocks CTCPs from matching users.<br />
|/mode +b C:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|m:[mask]<br />
|Blocks messages to the channel from matching users (like channel mode +m).<br />
|/mode +b m:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|N:[mask]<br />
|Prevents matching users from changing their nickname while in the channel.<br />
|/mode +b m:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|p:[mask]<br />
|Blocks part messages from matching users.<br />
|/mode +b p:*!*@bad.host.name.example.com<br />
|-<br />
|scope="row"|Q:[mask]<br />
|Prevents matching users from being kicked from the channel.<br />
|/mode +b Q:*!*@important.user.example.com<br />
|-<br />
|scope="row"|S:[mask]<br />
|Strips colors from messages by matching users.<br />
|/mode +b S:*!*@excessive.color.user.example.com<br />
|-<br />
|scope="row"|T:[mask]<br />
|Prevents matching users from sending NOTICEs to the channel.<br />
|/mode +b T:*!*@bad.host.name.example.com<br />
|}</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Modes&diff=5071Channel Modes2010-09-16T02:21:49Z<p>MIXX941: Added section for mode "A"</p>
<hr />
<div>Below is a full list of channel modes on MIXXnet and how they are used.<br />
<br />
In general, modes are set and removed in the following way:<br />
<br />
/mode #channel +<mode><br />
/mode #channel -<mode><br />
<br />
Examples of how to set each mode and their various parameters are provided below.<br />
<br />
==Basic Modes==<br />
===b (Ban)===<br />
Bans user from channel that matches the nick!ident@host hostmask. Can optionally redirect the banned user to a special channel if they attempt to join the channel while banned (see example 2 below).<br />
<br />
/mode #channel +b <nick!ident@host><br />
/mode #channel +b <nick!ident@host#bannedchannel><br />
<br />
===h (Halfop)===<br />
Gives <nickname> half-operator status on the channel<br />
<br />
/mode #channel +h <nickname><br />
<br />
===i (Invite Only)===<br />
Sets channel invite only. Users must be invited to join.<br />
<br />
/mode #channel +i<br />
<br />
===k (Channel Password)===<br />
Sets a channel password that users must have in order to join.<br />
<br />
/mode #channel +k <password><br />
<br />
===l (Channel Limit)===<br />
Sets a limit for the maximum numbers of users that can be on the channel at once.<br />
<br />
/mode #channel +l <limit><br />
<br />
===m (Moderated)===<br />
Sets channel to "moderated"; users must be voiced (+v) or higher to talk.<br />
<br />
/mode #channel +m<br />
<br />
===n (No External Messages)===<br />
Blocks external messages; users must be on the channel to talk. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +n<br />
<br />
===o (Channel Operator)===<br />
Gives <nickname> operator status on the channel. Requires channel operator status.<br />
<br />
/mode #channel +o <nickname<br />
<br />
===p (Private)===<br />
Sets channel as private; hides channel from user's WHOIS reply<br />
<br />
/mode #channel +p<br />
<br />
===s (Secret)===<br />
Sets channel as secret. This is the same as mode "p", however it also hides the channel from a /LIST<br />
<br />
/mode #channel +s<br />
<br />
===t (Topic Protection)===<br />
Makes it so only channel (half-)operators or higher can change the channel topic. '''This mode is enabled by default on all channels'''.<br />
<br />
/mode #channel +t<br />
<br />
===v (Voice)===<br />
Gives voice to <nickname>. Requires half-operator status or higher.<br />
<br />
/mode #channel +v <nickname><br />
<br />
==Advanced Modes==<br />
<br />
===A (Allow Regular Users To Invite)===<br />
Allows regular, non-opped users to invite users to the channel using "/invite". As invites bypass channel bans, limits, and keys, '''setting this mode will allow regular users to invite anyone into the channel even if they are banned, do not have the channel key, or the channel limit has been exceeded. USE THIS MODE WITH CAUTION.'''<br />
<br />
===a (Protected User)===<br />
Gives protected status to <nickname>. Protected users cannot be kicked or deopped except by the channel founder or services. Channel mode +a does not give +o, so non operators can be protected with +a.<br />
<br />
/mode #channel +a <nickname><br />
<br />
===e (Ban Exception)===<br />
Sets a ban exception on a nick!user@host hostmask. Users who match can still join the channel even if banned.<br />
<br />
/mode #channel +e <nick!user@host><br />
<br />
===c (Block Colors)===<br />
Blocks messages to the channel that contain colors.<br />
<br />
/mode #channel +c<br />
<br />
===C (No CTCP)===<br />
Blocks CTCP (PING, TIME, etc) to channels.<br />
<br />
/mode #channel +C<br />
<br />
===f (Message Flood Protection)===<br />
Provides protection against message/notice flooding. When a user types more lines than <lines> in <sec> seconds, they will be kicked. If <lines> is prefixed with a *, the user will be kicked and banned.<br />
<br />
/mode #channel +f <lines>:<sec><br />
/mode #channel +f 5:10 (Kicks a user who says more than 5 lines in 10 seconds)<br />
/mode #channel +f *3:5 (Kicks and bans a user who says more than 3 lines in 5 seconds)<br />
<br />
===g (Channel Message Filter)===<br />
Manages the channel message filter which gives channels the ability to have custom words to block/filter. Words are added with "+g <word>" and removed with "-g <word>" (examples are below):<br />
<br />
/mode #channel +g abadword (Adds "abadword" to the channel filter)<br />
/mode #channel -g abadword (Removes "abadword" from the channel filter)<br />
/mode #channel +g (Shows all words on the channel filter)<br />
<br />
===G (Censor)===<br />
Filters out common swear words that are said in the channel. The message still goes through, however any swear words said are censored out.<br />
<br />
/mode #channel +G<br />
<br />
===I (Invite Exception)===<br />
Allows users who match a nick!user@host hostmask to join the channel even if it is +i (invite only).<br />
<br />
/mode #channel +I <nick!user@host><br />
<br />
===j (Join Flood Protection)===<br />
Provides protection against join flooding. If there are more than <joins> joins in <sec> seconds, the channel will be locked for 60 seconds and new users will not be able to join for this time period. The lock can be removed before the 60 second time by unsetting and resetting +j. <br />
<br />
/mode #channel +j <joins>:<sec><br />
<br />
'''NOTE:''' The join flood protection may be triggered in the event of a netsplit and may incorrectly lock the channel when users rejoin on netjoin. This is a software issue which will be resolved in future updates.<br />
<br />
===J (Rejoin Prevention)===<br />
Prevents a user from rejoining the channel for <sec> seconds after being kicked.<br />
<br />
/mode #channel +J <sec><br />
<br />
===K (No Knocking)===<br />
Prevents users from doing a /KNOCK on an invite only (+i) channel.<br />
<br />
/mode #channel +K<br />
<br />
===L (Redirect When Full)===<br />
Redirects users to <channel> when the user limit (+l) has been reached on the current channel.<br />
<br />
/mode #channel +L <channel><br />
<br />
===M (Only Registered Users Talk)===<br />
Restricts users from talking on the channel unless they are registered and identified to [[NickServ]].<br />
<br />
/mode #channel +M<br />
<br />
===N (No Nick Changes)===<br />
Prevents users from changing their nicknames while in the channel.<br />
<br />
/mode #channel +N<br />
<br />
===P (Block Caps)===<br />
Blocks messages to the channel that are made up of mostly capital letters.<br />
<br />
/mode #channel +P<br />
<br />
===R (Only Registered Users Join)===<br />
Restricts users from joining the channel unless they are registered and identified to NickServ.<br />
<br />
/mode #channel +R<br />
<br />
===S (Strip Colors)===<br />
Strips colors from messages to the channel.<br />
<br />
/mode #channel +S<br />
<br />
===T (No Notices)===<br />
Prevents users from sending NOTICEs to the channel.<br />
<br />
/mode #channel +T<br />
<br />
===u (Auditorium Mode)===<br />
Provides an "auditorium mode" for the channel. When set, users will only see themselves and ops in the channel but will not see any other users in the userlist or any joins/parts/quits from other users.<br />
<br />
/mode #channel +u<br />
<br />
===x (Exception)===<br />
Allows users who match a nick!user@host hostmask to override ALL join restrictions such as +i/+l/+k/+b and join the channel no matter what.<br />
<br />
/mode #channel +x <nick!user@host><br />
<br />
===z (SSL Users Only)===<br />
Requires all users on the channel to be connected to MIXXnet via [[SSL]]. Non-SSL users will not be allowed to join.<br />
<br />
/mode #channel +z</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IRC_Client&diff=5069IRC Client2010-04-25T08:50:27Z<p>MIXX941: Add a web-based client section for Mibbit and lightIRC</p>
<hr />
<div>An [[IRC]] Client is a software program used to connect to an [[IRC|Internet Relay Chat]] network, such as [[MIXXnet]]. Below is a list of popular IRC clients for various platforms.<br />
<br />
==Graphical Clients==<br />
===Cross-Platform===<br />
* '''XChat:''' Created by Peter Zelenzy, [[XChat]] is a free, open source, and multi-platform IRC client with a graphical user interface. There are builds for various *nix distributions, [http://xchataqua.sourceforge.net/ Mac OS X], and Windows. [http://www.xchat.org http://www.xchat.org] (Note: The "official" Windows builds are not free. To see a list of completely free Windows builds, go [http://b0at.tx0.org/xchat/ here]).<br />
<br />
* '''Quassel:''' Quassel is an open source and cross-platform distributed IRC client. Its unique feature is the ability to attach and detach the graphical client portion from the core, similar to running screen and a text based client. [http://quassel-irc.org/ http://quassel-irc.org]<br />
<br />
* '''KVIrc:''' KVIrc is another open source and cross-platform IRC client based on the QT toolkit. There are binaries available for Unix, OS X, and Windows. [http://www.kvirc.de/ http://www.kvirc.de]<br />
<br />
* '''Pidgin:''' Pidgin is an open source, cross-platform application that combines many chat networks (includng IRC) into one program. [http://pidgin.im/ http://pidgin.im]<br />
<br />
* '''Opera:''' The excellent Opera web browser also has a simple [http://www.opera.com/browser/tutorials/intro/using/chat/ built-in IRC client]. There are versions available for various platforms including Windows, Mac OS X, FreeBSD, Linux, and Solaris. [http://www.opera.com/ http://www.opera.com]<br />
<br />
===Mac OS X Specific===<br />
* '''Colloquy:''' Colloquy is a free and open source graphical client with a slick Mac-inspired interface for Mac OS X. [http://colloquy.info/ http://colloquy.info]<br />
<br />
* '''Snak (Shareware):''' Snak is an IRC client for Macintosh OS X. It has several features and is actively developed. Snak is shareware ($29). [http://www.snak.com/ http://www.snak.com]<br />
<br />
* '''Ircle (Shareware):''' Another IRC client for Mac. Ircle runs on Mac OS 7.2 through 9.0.x, as well as Mac OS X 10.1 or newer. Ircle is shareware (19 €). [http://www.ircle.com http://www.ircle.com]<br />
<br />
===Windows Specific===<br />
* '''mIRC (Shareware):''' Khaled Mardam-Bey released the first version of [[mIRC]] on February 28, 1995. mIRC is a graphical IRC client for the Windows platform with it's own scripting language. mIRC is shareware, so to legally run it past 30 days you need a $20 license. [http://www.mirc.com http://www.mirc.com]<br />
<br />
==Text Clients==<br />
===Cross-Platform===<br />
* '''Irssi:''' Irssi is a popular open source and free text based IRC client. Irssi is different from BitchX because it does not use the old ircII code. Irssi also supports Perl scripting and runtime modules, so it is highly customizable. There are binaries available for several operating systems including Mac OSX and Windows. [http://www.irssi.org http://www.irssi.org]<br />
<br />
* '''WeeChat:''' WeeChat is an open source text based client with some advanced features like multiple interface capability, horizontal and vertical window splitting, nickname list, smart "hotlist" in the status bar to show channel activity by name, highlighting without switching channels, and spell checking. [http://weechat.flashtux.org/ http://weechat.flashtux.org]<br />
<br />
* '''BitchX:''' BitchX is another popular open source text based IRC client for UNIX. It started out as a script for the ircII client, but then panasync patched the script directly into the actual client in 1994. There are binaries for many operating systems including Windows. [http://www.bitchx.org http://www.bitchx.org]<br />
<br />
==Web-Based Clients==<br />
===Mibbit===<br />
Mibbit is a popular and feature rich AJAX client which allows users to easily connect to IRC from any web browser without plugins or special firewall requirements. Webmasters can create a [http://wiki.mibbit.com/index.php/Widget Mibbit Widget] to embed the chat application on their website. Please note that Mibbit is an externally hosted service so we have no control over its operation or reliability, though we do recommend it for its ease of use, good interface/features, and overall stability. [http://mibbit.com http://mibbit.com]<br />
<br />
MIXXnet fully supports connecting through Mibbit on all servers, and Mibbit users will have their real hostnames shown on the network. '''"irc.mixxnet.net"''' must be used in the "server" parameter to allow users' real hostnames to show up.<br />
<br />
===lightIRC===<br />
lightIRC is a freeware Flash IRC client with a clean and easy to use interface. Website admins can host the files on their own server or add an iframe to existing files on lightIRC's server. This client requires users to have the Adobe Flash plugin enabled in their browser which can limit compatibility as there is not official Flash support for all operating systems/browsers. [http://lightirc.com/ http://lightirc.com]<br />
<br />
All MIXXnet servers in the main rotation have support for lightIRC, however '''the "policyPort" parameter must be set to "6843"''' for the application to properly connect.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Start_Guide&diff=5068Channel Start Guide2010-04-05T22:52:21Z<p>MIXX941: Some minor cleanup</p>
<hr />
<div>The following is a guide to setting up your own channel on [[MIXXnet]] and protecting it with [[services]]. <br />
<br />
===Step 1: Creating The Channel===<br />
The first step in creating a [[channel]] is to join it first. While you're on [[IRC]], type "/join #yourchannel" without quotes and replace "#yourchannel" with the channel you want to create. If the channel is empty or unregistered, you will become an [[op]] (@) in that channel.<br />
<br />
===Step 2: Registering with ChanServ===<br />
In order for you to be the owner of the channel and have full privileges on it, you must register it with [[ChanServ]]. This is a very easy process, however it requires a registered [[nickname]]. If you have not already registered a nickname, see the [[NickServ]] documents for instructions on how to do that. <br />
<br />
To register a channel, type the following command into your [[IRC client]]:<br />
<br />
'''/msg chanserv register #channelname password description'''<br />
<br />
Replace "#channelname", "password", and "description" with the channel you are registering, the founder password you wish to have, and the description of your channel.<br />
<br />
If you have succeeded, you will see something like this:<br />
<br />
-ChanServ- Channel #channelname registered under your nickname: YourNick<br />
-ChanServ- Your channel password is test - remember it for later use.<br />
--- ChanServ sets mode +n #channelname<br />
--- ChanServ sets mode +t #channelname<br />
--- ChanServ sets mode +r #channelname<br />
<br />
Now most likely you will want to set the topic, give people access, and perform other channel maintenance tasks. Here are some common channel commands and what they do:<br />
<br />
===Channel Modes===<br />
For a complete list of all channel modes available on MIXXnet, please see the [[Channel_Modes|Channel Modes]] article. Below is a summary of basic channel modes:<br />
<br />
* /topic #channelname New Topic - This will set the topic of your channel to whatever you wish.<br />
<br />
* /mode #channelname +o nickname - This will op the person with the nickname "nickname".<br />
<br />
* /mode #channelname +h nickname - This will give channel-half operator status to the person with the nickname "nickname".<br />
<br />
* /mode #channelname +v nickname - This will give voice to the person with the nickname "nickname".<br />
<br />
* /mode #channelname +b user@host - This will ban that user/host mask from your channel.<br />
<br />
* /mode #channelname +s - This will make your room secret, and not show up when someone does a /list.<br />
<br />
* /mode #channelname +p - This will make your channel private.<br />
<br />
* /mode #channelname +i - This will make your channel "Invite-Only". This means you must "/invite nickname" for them to be able to enter your channel.<br />
<br />
* /mode #channelname +k yoursecretkey - This will set your channel's "key" (or password). Replace "yoursecretkey" with the key you want to set.<br />
<br />
* /mode #channelname +m - This will make your channel "Moderated". This means that only people with a voice (+v) or higher (such as an op) can speak in the channel.<br />
<br />
* /mode #channelname +N - This disallows nickname changes while in your channel.<br />
<br />
===ChanServ Modes===<br />
* AutoOP (aop) - This user will be able to kick/ban and can set almost any channel mode, but does not have access to any ChanServ commands (such as adding/deleting people from access lists, using the "akick" function, etc).<br />
<br />
* SuperOP (sop) - This user has full channel privileges. They can set almost any channel mode and can add/delete people from the ChanServ access lists. They can also use ChanServ to "AutoKick" (akick) and ban a user.<br />
<br />
* HalfOP (hop) - This user can kick and ban regular and voiced users. They cannot kick or ban ops.<br />
<br />
* Voice (vop) - This user can speak in channels with +m set, but has no channel moderation features. There is no benefit to having voice in an unmoderated channel.<br />
<br />
===ChanServ Channel Commands===<br />
* /msg chanserv aop #channel add nickname - This will add "nickname" to the channel auto-op list.<br />
<br />
* /msg chanserv sop #channel add nickname - This will add "nickname" to the channel super-op list.<br />
<br />
* /msg chanserv hop #channel add nickname - This will add "nickname" to the channel half-op list.<br />
<br />
* /msg chanserv vop #channel add nickname - This will add "nickname" to the channel auto-voice list.<br />
<br />
* /msg chanserv *op #channel del nickname - This will delete "nickname" from the *op access list. Replace "*op" with either "hop", "aop", "sop", "vop".<br />
<br />
[[Category:Services]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=ChanServ&diff=5067ChanServ2010-04-05T22:49:22Z<p>MIXX941: Changed some things around and added some notes</p>
<hr />
<div>ChanServ is a MIXXnet [[Services|service]] that allows you to register a [[channel]]. Registering your channel provides an easy way to manage [[operator|ops]] and prevent channel takeovers.<br />
<br />
For a guide on how to set up your channel using ChanServ, visit the [[Channel Start Guide]]<br />
<br />
==ChanServ Tips and Notes==<br />
===Automatic Expiration===<br />
Channels that have not been used in 180 days (when no user on the channel's access list has entered) will automatically expire and be available for other users to register.<br />
<br />
If the channel founder's nickname expires due to inactivity, the channel will also expire if no [[#SET SUCCESSOR|successor]] is set.<br />
<br />
===xOP vs Access Systems===<br />
xOP is the default access scheme for channels. Access is controlled by predefined levels known as [[#SOP]], [[#AOP]], [[#HOP]], and [[#VOP]]. If you wish to use the [[#ACCESS|access system]] instead, you must first disable the xOP system:<br />
<br />
/msg chanserv set #channel xop off<br />
<br />
===Autovoice For All Users===<br />
To get ChanServ to automatically voice everyone in your channel upon joining, do the following: <br />
<br />
/msg chanserv set #channel xop off<br />
/msg chanserv set #channel secure off<br />
/msg chanserv levels #channel set autovoice 0<br />
<br />
==ChanServ Commands==<br />
===HELP===<br />
<br />
ChanServ allows you to register and control various<br />
aspects of channels. ChanServ can often prevent<br />
malicious users from "taking over" channels by limiting<br />
who is allowed channel operator priviliges. Available<br />
commands are listed below; to use them, type<br />
/msg ChanServ command. For more information on a<br />
specific command, type /msg ChanServ HELP command.<br />
<br />
REGISTER Register a channel<br />
IDENTIFY Identify yourself with your password<br />
SET Set channel options and information<br />
AOP Modify the list of AOP users<br />
SOP Modify the list of SOP users<br />
ACCESS Modify the list of privileged users<br />
LEVELS Redefine the meanings of access levels<br />
AKICK Maintain the AutoKick list<br />
DROP Cancel the registration of a channel<br />
SENDPASS Help retrive lost passwords<br />
<br />
Other commands: BAN, CLEAR, DEOP, DEVOICE, GETKEY, INFO,<br />
INVITE, KICK, LIST, LOGOUT, OP, TOPIC,<br />
UNBAN, VOICE, VOP<br />
<br />
<br />
===REGISTER===<br />
<br />
Syntax: /msg ChanServ REGISTER channel password description<br />
<br />
Registers a channel in the ChanServ database. In order<br />
to use this command, you must first be a channel operator<br />
on the channel you're trying to register. The password<br />
is used with the IDENTIFY command to allow others to<br />
make changes to the channel settings at a later time.<br />
The last parameter, which must be included, is a<br />
general description of the channel's purpose.<br />
<br />
When you register a channel, you are recorded as the<br />
" founder" of the channel. The channel founder is allowed<br />
to change all of the channel settings for the channel;<br />
ChanServ will also automatically give the founder<br />
channel-operator privileges when s/he enters the channel.<br />
See the ACCESS command (/msg ChanServ HELP ACCESS) for<br />
information on giving a subset of these privileges to<br />
other channel users.<br />
<br />
NOTICE: In order to register a channel, you must have<br />
first registered your nickname. If you haven't,<br />
/msg ChanServ HELP for information on how to do so.<br />
<br />
<br />
===IDENTIFY===<br />
<br />
Syntax: /msg ChanServ IDENTIFY channel password<br />
<br />
Authenticates you to ChanServ as the founder of the given<br />
channel. Many commands require you to use this command<br />
before using them. The password should be the same one<br />
you sent with the REGISTER command.<br />
<br />
===LOGOUT===<br />
<br />
Syntax: /msg ChanServ LOGOUT channel nickname<br />
<br />
This command makes the selected nickname not identified<br />
anymore for the given channel.<br />
<br />
If you are the founder of the channel, you can log out anybody,<br />
else you can only log out yourself.<br />
<br />
<br />
===DROP===<br />
<br />
Syntax: /msg ChanServ DROP channel<br />
<br />
Unregisters the named channel. Can only be used by<br />
channel founder, who must use the IDENTIFY command first.<br />
<br />
<br />
===SET===<br />
<br />
Syntax: /msg ChanServ SET channel option parameters<br />
<br />
Allows the channel founder to set various channel options<br />
and other information.<br />
<br />
Available options:<br />
<br />
FOUNDER Set the founder of a channel<br />
SUCCESSOR Set the successor for a channel<br />
PASSWORD Set the founder password<br />
DESC Set the channel description<br />
URL Associate a URL with the channel<br />
EMAIL Associate an E-mail address with the channel<br />
ENTRYMSG Set a message to be sent to users when they<br />
enter the channel<br />
BANTYPE Set how Services make bans on the channel<br />
MLOCK Lock channel modes on or off<br />
KEEPTOPIC Retain topic when channel is not in use<br />
OPNOTICE Send a notice when OP/DEOP commands are used<br />
PEACE Regulate the use of critical commands<br />
PRIVATE Hide channel from LIST command<br />
RESTRICTED Restrict access to the channel<br />
SECURE Activate ChanServ security features<br />
SECUREOPS Stricter control of chanop status<br />
SECUREFOUNDER Stricter control of channel founder status<br />
SIGNKICK Sign kicks that are done with KICK command<br />
TOPICLOCK Topic can only be changed with TOPIC<br />
XOP Toggle the user privilege system<br />
<br />
Type /msg ChanServ HELP option for more information on a<br />
particular option.<br />
<br />
<br />
====SET FOUNDER====<br />
<br />
Syntax: /msg ChanServ SET channel FOUNDER nick<br />
<br />
Changes the founder of a channel. The new nickname must<br />
be a registered one.<br />
<br />
====SET SUCCESSOR====<br />
<br />
Syntax: /msg ChanServ SET channel SUCCESSOR nick<br />
<br />
Changes the successor of a channel. If the founder's<br />
nickname expires or is dropped while the channel is still<br />
registered, the successor will become the new founder of the<br />
channel. However, if the successor already has too many<br />
channels registered (<num>), the channel will be dropped<br />
instead, just as if no successor had been set. The new<br />
nickname must be a registered one.<br />
<br />
<br />
====SET PASSWORD====<br />
<br />
Syntax: /msg ChanServ SET channel PASSWORD password<br />
<br />
Sets the password used to identify as the founder of the<br />
channel.<br />
<br />
<br />
====SET DESC====<br />
<br />
Syntax: /msg ChanServ SET channel DESC description<br />
<br />
Sets the description for the channel, which shows up with<br />
the LIST and INFO commands.<br />
<br />
<br />
====SET URL====<br />
<br />
Syntax: /msg ChanServ SET channel URL [url]<br />
<br />
Associates the given URL with the channel. This URL will<br />
be displayed whenever someone requests information on the<br />
channel with the INFO command. If no parameter is given,<br />
deletes any current URL for the channel.<br />
<br />
<br />
====SET EMAIL====<br />
<br />
Syntax: /msg ChanServ SET channel EMAIL [address]<br />
<br />
Associates the given E-mail address with the channel.<br />
This address will be displayed whenever someone requests<br />
information on the channel with the INFO command. If no<br />
parameter is given, deletes any current E-mail address for<br />
the channel.<br />
<br />
<br />
====SET ENTRYMSG====<br />
<br />
Syntax: /msg ChanServ SET channel ENTRYMSG [message]<br />
<br />
Sets the message which will be sent via /notice to users<br />
when they enter the channel. If no parameter is given,<br />
causes no message to be sent upon entering the channel.<br />
<br />
<br />
====SET BANTYPE====<br />
<br />
Syntax: /msg ChanServ SET channel BANTYPE bantype<br />
<br />
Sets the ban type that will be used by services whenever<br />
they need to ban someone from your channel.<br />
<br />
bantype is a number between 0 and 3 that means:<br />
<br />
0: ban in the form *!user@host<br />
1: ban in the form *!*user@host<br />
2: ban in the form *!*@host<br />
3: ban in the form *!*user@*.domain<br />
<br />
<br />
====SET KEEPTOPIC====<br />
<br />
Syntax: /msg ChanServ SET channel KEEPTOPIC {ON | OFF}<br />
<br />
Enables or disables the topic retention option for a<br />
channel. When topic retention is set, the topic for the<br />
channel will be remembered by ChanServ even after the<br />
last user leaves the channel, and will be restored the<br />
next time the channel is created.<br />
<br />
<br />
====SET TOPICLOCK====<br />
<br />
Syntax: /msg ChanServ SET channel TOPICLOCK {ON | OFF}<br />
<br />
Enables or disables the topic lock option for a channel.<br />
When topic lock is set, ChanServ will not allow the<br />
channel topic to be changed except via the TOPIC<br />
command.<br />
<br />
<br />
====SET MLOCK====<br />
<br />
Syntax: /msg ChanServ SET channel MLOCK modes<br />
<br />
Sets the mode-lock parameter for the channel. ChanServ<br />
allows you to define certain channel modes to be always<br />
on, off or free to be either on or off.<br />
<br />
The modes parameter is constructed exactly the same way<br />
as a /MODE command; that is, modes followed by a + are<br />
locked on, and modes followed by a - are locked off. Note,<br />
however, that unlike the /MODE command, each use of<br />
SET MLOCK will remove all modes previously locked before<br />
setting the new!<br />
<br />
Warning: If you set a mode-locked key, as in the second<br />
example below, you should also set the RESTRICTED option for<br />
the channel (see HELP SET RESTRICTED), or anyone entering<br />
the channel when it is empty will be able to see the key!<br />
<br />
Examples:<br />
<br />
SET #channel MLOCK +nt-iklps<br />
Forces modes n and t on, and modes i, k, l, p, and<br />
s off. Mode m is left free to be either on or off.<br />
<br />
SET #channel MLOCK +knst-ilmp my-key<br />
Forces modes k, n, s, and t on, and modes i, l, m,<br />
and p off. Also forces the channel key to be<br />
" my-key".<br />
<br />
SET #channel MLOCK +<br />
Removes the mode lock; all channel modes are free<br />
to be either on or off.<br />
<br />
<br />
====SET PEACE====<br />
<br />
Syntax: /msg ChanServ SET channel PEACE {ON | OFF}<br />
<br />
Enables or disables the peace option for a channel.<br />
When peace is set, an user won't be able to kick,<br />
ban or remove a channel status of an user that has<br />
a level superior or equal to his via ChanServ commands.<br />
<br />
<br />
====SET PRIVATE====<br />
<br />
Syntax: /msg ChanServ SET channel PRIVATE {ON | OFF}<br />
<br />
Enables or disables the private option for a channel.<br />
When private is set, a /msg ChanServ LIST will not<br />
include the channel in any lists.<br />
<br />
<br />
====SET RESTRICTED====<br />
<br />
Syntax: /msg ChanServ SET channel RESTRICTED {ON | OFF}<br />
<br />
Enables or disables the restricted access option for a<br />
channel. When restricted access is set, users who would<br />
normally be disallowed from having channel operator<br />
privileges (users with negative access levels and, if<br />
secure ops is set, users not on the access list) will<br />
instead be kicked and banned from the channel.<br />
<br />
<br />
====SET SECURE====<br />
<br />
Syntax: /msg ChanServ SET channel SECURE {ON | OFF}<br />
<br />
Enables or disables ChanServ's security features for a<br />
channel. When SECURE is set, only users who have<br />
registered their nicknames with ChanServ and IDENTIFY'd<br />
with their password will be given access to the channel<br />
as controlled by the access list.<br />
<br />
<br />
====SET SECUREOPS====<br />
<br />
Syntax: /msg ChanServ SET channel SECUREOPS {ON | OFF}<br />
<br />
Enables or disables the secure ops option for a channel.<br />
When secure ops is set, users who are not on the userlist<br />
will not be allowed chanop status.<br />
<br />
====SET SECUREFOUNDER====<br />
<br />
Syntax: /msg ChanServ SET channel SECUREFOUNDER {ON | OFF}<br />
<br />
Enables or disables the secure founder option for a channel.<br />
When secure founder is set, only the real founder will be<br />
able to drop the channel, change its password, its founder and its<br />
successor, and not those who are IDENTIFY'd with ChanServ.<br />
<br />
====SET SIGNKICK====<br />
<br />
Syntax: /msg ChanServ SET channel SIGNKICK {ON | LEVEL | OFF}<br />
<br />
Enables or disables signed kicks for a<br />
channel. When SIGNKICK is set, kicks issued with<br />
ChanServ KICK command will have the nick that used the<br />
command in their reason.<br />
<br />
If you use LEVEL, those who have a level that is superior<br />
or equal to the SIGNKICK level on the channel won't have their<br />
kicks signed. See /msg ChanServ HELP LEVELS for more information.<br />
<br />
<br />
====SET XOP====<br />
<br />
Syntax: /msg ChanServ SET channel XOP {ON | OFF}<br />
<br />
Enables or disables the xOP lists system for a channel.<br />
When XOP is set, you have to use the AOP/SOP/VOP<br />
commands in order to give channel privileges to<br />
users, else you have to use the ACCESS command.<br />
<br />
Technical Note: when you switch from access list to xOP<br />
lists system, your level definitions and user levels will be<br />
changed, so you won't find the same values if you<br />
switch back to access system!<br />
<br />
You should also check that your users are in the good xOP<br />
list after the switch from access to xOP lists, because the<br />
guess is not always perfect... in fact, it is not recommended<br />
to use the xOP lists if you changed level definitions with<br />
the LEVELS command.<br />
<br />
Switching from xOP lists system to access list system<br />
causes no problem though.<br />
<br />
<br />
====SET OPNOTICE====<br />
<br />
Syntax: /msg ChanServ SET channel OPNOTICE {ON | OFF}<br />
<br />
Enables or disables the op-notice option for a channel.<br />
When op-notice is set, ChanServ will send a notice to the<br />
channel whenever the OP or DEOP commands are used for a user<br />
in the channel.<br />
<br />
<br />
===AOP===<br />
<br />
Syntax: /msg ChanServ AOP channel ADD nick<br />
AOP channel DEL {nick | entry-num | list}<br />
AOP channel LIST [mask | list]<br />
AOP channel CLEAR<br />
<br />
Maintains the AOP (AutoOP) list for a channel. The AOP<br />
list gives users the right to be auto-opped on your channel,<br />
to unban or invite themselves if needed, to have their<br />
greet message showed on join, and so on.<br />
<br />
The AOP ADD command adds the given nickname to the<br />
AOP list.<br />
<br />
The AOP DEL command removes the given nick from the<br />
AOP list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The AOP LIST command displays the AOP list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
AOP #channel LIST 2-5,7-9<br />
Lists AOP entries numbered 2 through 5 and<br />
7 through 9.<br />
<br />
The AOP CLEAR command clears all entries of the<br />
AOP list.<br />
<br />
The AOP ADD and AOP DEL commands are limited to<br />
<br />
SOPs or above, while the AOP CLEAR command can only<br />
be used by the channel founder. However, any user on the<br />
AOP list may use the AOP LIST command.<br />
<br />
This command may have been disabled for your channel, and<br />
in that case you need to use the access list. See<br />
/msg ChanServ HELP ACCESS for information about the access list,<br />
and /msg ChanServ HELP SET XOP to know how to toggle between<br />
the access list and xOP list systems.<br />
<br />
<br />
===HOP===<br />
<br />
Syntax: /msg ChanServ HOP channel ADD nick<br />
HOP channel DEL {nick | entry-num | list}<br />
HOP channel LIST [mask | list]<br />
HOP channel CLEAR<br />
<br />
Maintains the HOP (HalfOP) list for a channel. The HOP<br />
list gives users the right to be auto-halfopped on your<br />
channel.<br />
<br />
The HOP ADD command adds the given nickname to the<br />
HOP list.<br />
<br />
The HOP DEL command removes the given nick from the<br />
HOP list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The HOP LIST command displays the HOP list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
HOP #channel LIST 2-5,7-9<br />
Lists HOP entries numbered 2 through 5 and<br />
7 through 9.<br />
<br />
The HOP CLEAR command clears all entries of the<br />
HOP list.<br />
<br />
The HOP ADD, HOP DEL and HOP LIST commands are<br />
limited to AOPs or above, while the HOP CLEAR command can only be used by the channel founder.<br />
<br />
This command may have been disabled for your channel, and<br />
in that case you need to use the access list. See<br />
/msg ChanServ HELP ACCESS for information about the access list,<br />
and /msg ChanServ HELP SET XOP to know how to toggle between<br />
the access list and xOP list systems.<br />
<br />
<br />
===SOP===<br />
<br />
Syntax: /msg ChanServ SOP channel ADD nick<br />
SOP channel DEL {nick | entry-num | list}<br />
SOP channel LIST [mask | list]<br />
SOP channel CLEAR<br />
<br />
Maintains the SOP (SuperOP) list for a channel. The SOP<br />
list gives users all rights given by the AOP list, and adds<br />
those needed to use the AutoKick and the BadWords lists,<br />
to send and read channel memos, and so on.<br />
<br />
The SOP ADD command adds the given nickname to the<br />
SOP list.<br />
<br />
The SOP DEL command removes the given nick from the<br />
SOP list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The SOP LIST command displays the SOP list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
SOP #channel LIST 2-5,7-9<br />
Lists AOP entries numbered 2 through 5 and<br />
7 through 9.<br />
<br />
The SOP CLEAR command clears all entries of the<br />
SOP list.<br />
<br />
The SOP ADD, SOP DEL and SOP CLEAR commands are<br />
limited to the channel founder. However, any user on the<br />
AOP list may use the SOP LIST command.<br />
<br />
<br />
This command may have been disabled for your channel, and<br />
in that case you need to use the access list. See<br />
/msg ChanServ HELP ACCESS for information about the access list,<br />
and /msg ChanServ HELP SET XOP to know how to toggle between<br />
the access list and xOP list systems.<br />
<br />
<br />
===VOP===<br />
<br />
Syntax: /msg ChanServ VOP channel ADD nick<br />
VOP channel DEL {nick | entry-num | list}<br />
VOP channel LIST [mask | list]<br />
VOP channel CLEAR<br />
<br />
Maintains the VOP (VOicePeople) list for a channel.<br />
The VOP list allows users to be auto-voiced and to voice<br />
themselves if they aren't.<br />
<br />
The VOP ADD command adds the given nickname to the<br />
VOP list.<br />
<br />
The VOP DEL command removes the given nick from the<br />
VOP list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The VOP LIST command displays the VOP list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
VOP #channel LIST 2-5,7-9<br />
Lists VOP entries numbered 2 through 5 and 7 through 9.<br />
<br />
The VOP CLEAR command clears all entries of the<br />
VOP list.<br />
<br />
The VOP ADD, VOP DEL and VOP LIST commands are<br />
limited to AOPs or above, while the VOP CLEAR command<br />
can only be used by the channel founder.<br />
<br />
This command may have been disabled for your channel, and in that case you need to use the access list. See<br />
/msg ChanServ HELP ACCESS for information about the access list,<br />
and /msg ChanServ HELP SET XOP to know how to toggle between<br />
the access list and xOP list systems.<br />
<br />
<br />
===ACCESS===<br />
<br />
Syntax: /msg ChanServ ACCESS channel ADD nick level<br />
ACCESS channel DEL {nick | entry-num | list}<br />
ACCESS channel LIST [mask | list]<br />
ACCESS channel CLEAR<br />
<br />
Maintains the access list for a channel. The access<br />
list specifies which users are allowed chanop status or<br />
access to ChanServ commands on the channel. Different<br />
user levels allow for access to different subsets of<br />
privileges; /msg ChanServ HELP ACCESS LEVELS for more<br />
specific information. Any nick not on the access list has<br />
a user level of 0.<br />
<br />
The ACCESS ADD command adds the given nickname to the<br />
access list with the given user level; if the nick is<br />
already present on the list, its access level is changed to<br />
the level specified in the command. The level specified<br />
must be less than that of the user giving the command, and<br />
if the nick is already on the access list, the current<br />
access level of that nick must be less than the access level<br />
of the user giving the command.<br />
<br />
The ACCESS DEL command removes the given nick from the<br />
access list. If a list of entry numbers is given, those<br />
entries are deleted. (See the example for LIST below.)<br />
<br />
The ACCESS LIST command displays the access list. If<br />
a wildcard mask is given, only those entries matching the<br />
mask are displayed. If a list of entry numbers is given,<br />
only those entries are shown; for example:<br />
<br />
ACCESS #channel LIST 2-5,7-9<br />
Lists access entries numbered 2 through 5 and<br />
7 through 9.<br />
<br />
The ACCESS CLEAR command clears all entries of the<br />
access list.<br />
<br />
<br />
====ACCESS LEVELS====<br />
<br />
User access levels<br />
<br />
By default, the following access levels are defined:<br />
<br />
Founder Full access to ChanServ functions; automatic<br />
opping upon entering channel. Note<br />
that only one person may have founder<br />
status (it cannot be given using the<br />
ACCESS command).<br />
10 Access to AKICK command; automatic opping.<br />
5 Automatic opping.<br />
3 Automatic voicing.<br />
0 No special privileges; can be opped by other<br />
ops (unless secure-ops is set).<br />
< 0 May not be opped.<br />
<br />
These levels may be changed, or new ones added, using the<br />
LEVELS command; type /msg ChanServ HELP LEVELS for<br />
information.<br />
<br />
===AKICK===<br />
<br />
Syntax: /msg ChanServ AKICK channel ADD mask [reason]<br />
AKICK channel STICK mask<br />
AKICK channel UNSTICK mask<br />
AKICK channel DEL mask<br />
AKICK channel LIST [mask]<br />
AKICK channel VIEW [mask]<br />
AKICK channel ENFORCE<br />
AKICK channel CLEAR<br />
<br />
Maintains the AutoKick list for a channel. If a user<br />
on the AutoKick list attempts to join the channel,<br />
ChanServ will ban that user from the channel, then kick<br />
the user.<br />
<br />
The AKICK ADD command adds the given nick or usermask<br />
to the AutoKick list. If a reason is given with<br />
the command, that reason will be used when the user is<br />
kicked; if not, the default reason is "You have been<br />
banned from the channel".<br />
<br />
The AKICK STICK command permanently bans the given mask<br />
on the channel. If someone tries to remove the ban, ChanServ<br />
will automatically set it again. You can't use it for<br />
registered nicks.<br />
<br />
The AKICK UNSTICK command cancels the effect of the<br />
AKICK STICK command, so you'll be able to unset the<br />
ban again on the channel.<br />
<br />
The AKICK DEL command removes the given nick or mask<br />
from the AutoKick list. It does not, however, remove any<br />
bans placed by an AutoKick; those must be removed<br />
manually.<br />
<br />
The AKICK LIST command displays the AutoKick list, or<br />
optionally only those AutoKick entries which match the<br />
given mask.<br />
<br />
The AKICK VIEW command is a more verbose version of<br />
AKICK LIST command.<br />
<br />
The AKICK ENFORCE command causes ChanServ to enforce the<br />
current AKICK list by removing those users who match an<br />
AKICK mask.<br />
<br />
The AKICK CLEAR command clears all entries of the<br />
akick list.<br />
<br />
<br />
===LEVELS===<br />
<br />
Syntax: /msg ChanServ LEVELS channel SET type level<br />
LEVELS channel {DIS | DISABLE} type<br />
LEVELS channel LIST<br />
LEVELS channel RESET<br />
<br />
The LEVELS command allows fine control over the meaning of<br />
the numeric access levels used for channels. With this<br />
command, you can define the access level required for most<br />
of ChanServ's functions. (The SET FOUNDER and SET PASSWORD<br />
commands, as well as this command, are always restricted to<br />
the channel founder.)<br />
<br />
LEVELS SET allows the access level for a function or group of<br />
functions to be changed. LEVELS DISABLE (or DIS for short)<br />
disables an automatic feature or disallows access to a<br />
function by anyone other than the channel founder.<br />
LEVELS LIST shows the current levels for each function or<br />
group of functions. LEVELS RESET resets the levels to the<br />
default levels of a newly-created channel (see<br />
HELP ACCESS LEVELS).<br />
<br />
For a list of the features and functions whose levels can be<br />
set, see HELP LEVELS DESC.<br />
<br />
<br />
===INFO===<br />
<br />
Syntax: /msg ChanServ INFO channel [ALL]<br />
<br />
Lists information about the named registered channel,<br />
including its founder, time of registration, last time<br />
used, description, and mode lock, if any. If ALL is<br />
specified, the entry message and successor will also<br />
be displayed.<br />
<br />
By default, the ALL option is limited to those with<br />
founder access on the channel.<br />
<br />
<br />
===LIST===<br />
<br />
Syntax: /msg ChanServ LIST pattern<br />
<br />
Lists all registered channels matching the given pattern.<br />
(Channels with the PRIVATE option set are not listed.)<br />
<br />
<br />
===OP===<br />
<br />
Syntax: /msg ChanServ OP [#channel [nick]]<br />
<br />
Ops a selected nick on a channel. If nick is not given,<br />
it will op you. If channel and nick are not given,<br />
it will op you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel.<br />
<br />
<br />
===DEOP===<br />
<br />
Syntax: /msg ChanServ DEOP [#channel [nick]]<br />
<br />
Deops a selected nick on a channel. If nick is not given,<br />
it will deop you. If channel and nick are not given,<br />
it will deop you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel.<br />
<br />
===VOICE===<br />
<br />
Syntax: /msg ChanServ VOICE [#channel [nick]]<br />
<br />
Voices a selected nick on a channel. If nick is not given,<br />
it will voice you. If channel and nick are not given,<br />
it will voice you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel, or to VOPs or those with level 3<br />
and above for self voicing.<br />
<br />
<br />
===DEVOICE===<br />
<br />
Syntax: /msg ChanServ DEVOICE [#channel [nick]]<br />
<br />
Devoices a selected nick on a channel. If nick is not given,<br />
it will devoice you. If channel and nick are not given,<br />
it will devoice you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel, or to VOPs or those with level 3<br />
and above for self devoicing.<br />
<br />
===HALFOP===<br />
<br />
Syntax: /msg ChanServ HALFOP [#channel [nick]]<br />
<br />
Halfops a selected nick on a channel. If nick is not given,<br />
it will halfop you. If channel and nick are not given,<br />
it will halfop you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs and those with level 5 access<br />
and above on the channel, or to HOPs or those with level 4<br />
and above for self halfopping.<br />
<br />
<br />
===DEHALFOP===<br />
<br />
Syntax: /msg ChanServ DEHALFOP [#channel [nick]]<br />
<br />
Dehalfops a selected nick on a channel. If nick is not given,<br />
it will dehalfop you. If channel and nick are not given,<br />
it will dehalfop you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs and those with level 5 access<br />
and above on the channel, or to HOPs or those with level 4<br />
and above for self dehalfopping.<br />
<br />
===PROTECT===<br />
<br />
Syntax: /msg ChanServ PROTECT [#channel [nick]]<br />
<br />
Protects a selected nick on a channel. If nick is not given,<br />
it will protect you. If channel and nick are not given,<br />
it will protect you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to the founder, or to SOPs or those with<br />
level 10 and above on the channel for self protecting.<br />
<br />
<br />
===DEPROTECT===<br />
<br />
Syntax: /msg ChanServ DEPROTECT [#channel [nick]]<br />
<br />
Deprotects a selected nick on a channel. If nick is not given,<br />
it will deprotect you. If channel and nick are not given,<br />
it will deprotect you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to the founder, or to SOPs or those with<br />
level 10 and above on the channel for self deprotecting.<br />
<br />
<br />
===OWNER===<br />
<br />
Syntax: /msg ChanServ OWNER [#channel]<br />
<br />
Gives you owner status on channel. If channel is not<br />
given, it will give you owner status on all channels you're<br />
on, provided you have the rights to.<br />
<br />
Limited to those with founder access on the channel.<br />
<br />
<br />
===DEOWNER===<br />
<br />
Syntax: /msg ChanServ DEOWNER [#channel]<br />
<br />
Removes your owner status on channel. If channel is<br />
not given, it will remove your owner status on all channels<br />
you're on, provided you have the rights to.<br />
<br />
Limited to those with founder access on the channel.<br />
<br />
<br />
===INVITE===<br />
<br />
Syntax: /msg ChanServ INVITE channel<br />
<br />
Tells ChanServ to invite you into the given channel.<br />
<br />
By default, limited to AOPs or those with level 5 and above<br />
on the channel.<br />
<br />
<br />
===UNBAN===<br />
<br />
Syntax: /msg ChanServ UNBAN channel<br />
<br />
Tells ChanServ to remove all bans preventing you from<br />
entering the given channel.<br />
<br />
By default, limited to AOPs or those with level 5 and above<br />
on the channel.<br />
<br />
===KICK===<br />
<br />
Syntax: /msg ChanServ KICK [#channel [nick [reason]]]<br />
<br />
Kicks a selected nick on a channel. If nick is not given,<br />
it will kick you. If channel and nick are not given,<br />
it will kick you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel.<br />
<br />
<br />
===BAN===<br />
<br />
Syntax: /msg ChanServ BAN [#channel [nick [reason]]]<br />
<br />
Bans a selected nick on a channel. If nick is not given,<br />
it will ban you. If channel and nick are not given,<br />
it will ban you on all channels you're on, provided you<br />
have the rights to.<br />
<br />
By default, limited to AOPs or those with level 5 access<br />
and above on the channel.<br />
<br />
<br />
===TOPIC===<br />
<br />
Syntax: /msg ChanServ TOPIC channel [topic]<br />
<br />
Causes ChanServ to set the channel topic to the one<br />
specified. If topic is not given, then an empty topic<br />
is set. This command is most useful in conjunction<br />
with SET TOPICLOCK. See /msg ChanServ HELP SET TOPICLOCK<br />
for more information.<br />
<br />
By default, limited to those with founder access on the<br />
channel.<br />
<br />
<br />
===CLEAR===<br />
<br />
Syntax: /msg ChanServ CLEAR channel what<br />
<br />
Tells ChanServ to clear certain settings on a channel. what<br />
can be any of the following:<br />
<br />
MODES Resets all modes on the channel (i.e. clears<br />
modes i,k,l,m,n,p,s,t).<br />
BANS Clears all bans on the channel.<br />
EXCEPTS Clears all excepts on the channel.<br />
OPS Removes channel-operator status (mode +o) from<br />
all channel operators.<br />
VOICES Removes "voice" status (mode +v) from anyone<br />
with that mode set.<br />
USERS Removes (kicks) all users from the channel.<br />
<br />
By default, limited to those with founder access on the<br />
channel.<br />
<br />
===GETKEY===<br />
<br />
Syntax: /msg ChanServ GETKEY channel<br />
<br />
Returns the key of the given channel. This is a command<br />
mainly intended to be used by bots and/or scripts, so<br />
the output is in the following way:<br />
<br />
KEY <channel> <key><br />
<br />
key is "NO KEY" if no key is set.<br />
<br />
[[Category:Anope]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=IPv6&diff=5065IPv62009-11-03T19:15:49Z<p>MIXX941: Updated IPv6 address and removed spam</p>
<hr />
<div>'''IPv6''' stands for Internet Protocol version 6. [[MIXXnet]] currently has one server that supports IPv6. <br />
<br />
You can connect to MIXXnet via IPv6 by using: '''irc.ipv6.mixxnet.net'''<br />
<br />
==External Links==<br />
* [http://en.wikipedia.org/wiki/IPv6 IPv6 at Wikipedia]<br />
<br />
{{stub}}</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel_Start_Guide&diff=5064Channel Start Guide2009-10-16T22:27:30Z<p>MIXX941: Reverted edits by CarolineWilson (Talk) to last revision by MIXX941</p>
<hr />
<div>The following is a guide to setting up your own channel on [[MIXXnet]] and protecting it with [[services]]. <br />
<br />
===Step 1: Creating The Channel===<br />
The first step in creating a [[channel]] is to join it first. While you're on [[IRC]], type "/join #yourchannel" without quotes and replace "#yourchannel" with the channel you want to create. If the channel is empty or unregistered, you will become an [[op]] (@) in that channel.<br />
<br />
===Step 2: Registering with ChanServ===<br />
In order for you to be the owner of the channel and have full privileges on it, you must register it with [[ChanServ]]. This is a very easy process, however it requires a registered [[nickname]]. If you have not already registered a nickname, see the [[NickServ]] documents for instructions on how to do that. <br />
<br />
To register a channel, type the following command into your [[IRC client]]:<br />
<br />
'''/msg chanserv register #channelname password description'''<br />
<br />
Replace "#channelname", "password", and "description" with the channel you are registering, the founder password you wish to have, and the description of your channel.<br />
<br />
If you have succeeded, you will see something like this:<br />
<br />
-ChanServ- Channel #channelname registered under your nickname: YourNick<br />
-ChanServ- Your channel password is test - remember it for later use.<br />
--- ChanServ sets mode +n #channelname<br />
--- ChanServ sets mode +t #channelname<br />
--- ChanServ sets mode +r #channelname<br />
<br />
Now most likely you will want to set the topic, give people access, and perform other channel maintenance tasks. Here are some common channel commands and what they do:<br />
<br />
===Channel Modes===<br />
For a complete list of all channel modes available on MIXXnet, please see the [[Channel_Modes|Channel Modes]] article. Below is a summary of basic channel modes:<br />
<br />
* /topic #channelname New Topic - This will set the topic of your channel to whatever you wish.<br />
<br />
* /mode #channelname +o nickname - This will op the person with the nickname "nickname".<br />
<br />
* /mode #channelname +h nickname - This will give channel-half operator status to the person with the nickname "nickname".<br />
<br />
* /mode #channelname +v nickname - This will give voice to the person with the nickname "nickname".<br />
<br />
* /mode #channelname +b user@host - This will ban that user/host mask from your channel.<br />
<br />
* /mode #channelname +s - This will make your room secret, and not show up when someone does a /list.<br />
<br />
* /mode #channelname +p - This will make your channel private.<br />
<br />
* /mode #channelname +i - This will make your channel "Invite-Only". This means you must "/invite nickname" for them to be able to enter your channel.<br />
<br />
* /mode #channelname +k yoursecretkey - This will set your channel's "key" (or password). Replace "yoursecretkey" with the key you want to set.<br />
<br />
* /mode #channelname +m - This will make your channel "Moderated". This means that only people with a voice (+v) or higher (such as an op) can speak in the channel.<br />
<br />
* /mode #channelname +N - This disallows nickname changes while in your channel.<br />
<br />
===ChanServ Modes===<br />
* AutoOP (aop) - This user will be able to kick/ban and can set almost any channel mode, but does not have access to any ChanServ commands (such as adding/deleting people from access lists, using the "akick" function, etc).<br />
<br />
* SuperOP (sop) - This user has full channel privileges. They can set almost any channel mode and can add/delete people from the ChanServ access lists. They can also use ChanServ to "AutoKick" (akick) and ban a user.<br />
<br />
* HalfOP (hop) - This user can kick and ban regular and voiced users. They cannot kick or ban ops.<br />
<br />
* Voice (vop) - This user can speak in channels with +m set, but has no channel moderation features. Having a voice in an unmoderated room does no good.<br />
<br />
===ChanServ Channel Commands===<br />
* /chanserv aop #channel add nickname - This will add "nickname" to the channel auto-op list.<br />
<br />
* /chanserv sop #channel add nickname - This will add "nickname" to the channel super-op list.<br />
<br />
* /chanserv hop #channel add nickname - This will add "nickname" to the channel half-op list.<br />
<br />
* /chanserv vop #channel add nickname - This will add "nickname" to the channel auto-voice list.<br />
<br />
* /chanserv *op #channel del nickname - This will delete "nickname" from the *op access list. Replace "*op" with either "hop", "aop", "sop", "vop".<br />
<br />
[[Category:Services]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Main_Page&diff=5062Main Page2009-10-03T21:03:35Z<p>MIXX941: Added proxy link</p>
<hr />
<div>Welcome to the MIXXnet Wiki. Here you will find user and staff contributed documents about [[MIXXnet]] and [[IRC]] in general. We encourage users to help out our documentation project by contributing information, however due to spam, editing can now only be done if you have registered and logged in.<br />
<br />
If you have any questions and need immediate help, log on to IRC: <br />
<br />
'''irc.mixxnet.net / #help'''<br />
<br />
You can use the search box to your left to search for articles that others have written or you can click [[Special:Allpages|here]] to browse all articles.<br />
<br />
== Getting Started ==<br />
Here are some articles that will help you get started on MIXXnet:<br />
<br />
* [[Channel_Start_Guide|Channel Start Guide - A complete guide to starting a channel]]<br />
* [[Channel_Modes|Channel Modes List]]<br />
* [[HostServ|vhost Information - Assign or remove a vhost on your nickname]]<br />
* [[SSL|SSL Information]]<br />
* [[IRC_client|Popular IRC Clients List]]<br />
* [[Proxy|Proxy policies and features]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Proxy&diff=5061Proxy2009-10-03T19:25:38Z<p>MIXX941: Minor formatting edit</p>
<hr />
<div>MIXXnet allows connections to the network using a proxy. While we do not globally deny access to proxied connections under normal circumstances, we do have mechanisms in place which provide channel operators fine control over what is and what is not allowed in their channels. This article will outline MIXXnet's network-wide proxy policies and how we handle connections made through proxies.<br />
<br />
==General Information==<br />
All connections made to the network are checked against various Domain Name Service Blacklists (DNSBLs) which can identify potential sources of abuse. Port scans may also be performed to check for active open proxies running on your IP address. If the IP address you are connecting from is detected as being a proxy, you will receive a private message from "ProxyGuard" notifying you of this and your hostname will be altered with one of the following appended to the end:<br />
<br />
*'''.dnsbl.proxy''' - IP address is on a blacklist that we check against<br />
*'''.tor.proxy''' - Tor Project exit node that allows connections to IRC ports<br />
<br />
If your IP address is on a blacklist, you will be given removal instructions via private message. Please follow these instructions to get your IP removed from the blacklist and reconnect to MIXXnet when the removal process is complete. If the removal process is successful, you should no longer be detected as a proxy and your normal hostname should be shown on the network.<br />
<br />
Channel operators have the option of banning some or all users that are detected as using a proxy. If you are detected and notified, please be aware that you may not be able to join certain channels on the network until you are removed from the blacklist. This is entirely a channel's decision and we as a network will not override this channel policy.<br />
<br />
MIXXnet reserves the right to impose temporary global limits or restrictions on proxied connections if a situation warrants.<br />
<br />
If you have any questions about or need help regarding connections through proxies, please ask in #help.<br />
<br />
==Channel Implementation==<br />
MIXXnet provides the ability for channels to restrict access to users using proxies which can help with potential abuse issues like bot floods or ban evasion. This is not enabled by default in any channels, however it can be set and removed at will by channel operators. Blocking proxied connections is handled through channel mode "b" (ban). The following is a list of hostmasks you can ban to block proxies from your channel:<br />
<br />
* '''*!*@*.dnsbl.proxy''' - Block users whose IP is blacklisted as an abusive IP (does not include Tor)<br />
* '''*!*@*.tor.proxy''' - Block users who are connecting through the Tor Project<br />
* '''*!*@*.proxy''' - Block all detected proxies<br />
<br />
If your channel blocks some or all of the above proxies and a user attempts to join, they will be notified that they are banned. We understand that this might not be the most desired behavior, however we have come up with a couple methods to help the user know why they are banned and how to fix it.<br />
<br />
1) Anytime a user is detected as being a proxy, they will receive a private message notifying them of this which provides a link to this article with the explanation above as well as instructions for removal if possible. This should hopefully clarify why they are banned from your channel, and once they are removed from the blacklist they will be allowed to join immediately upon reconnecting to IRC.<br />
<br />
2) Channel operators also have the option of setting a channel to redirect users to if they are banned and attempt to join. In this case, you should direct users who are banned due to using a proxy to #proxyhelp to receive further help on this issue. For example, to block all proxies and redirect proxied users to #proxyhelp:<br />
<br />
/mode #channel +b *!*@*.proxy#proxyhelp<br />
<br />
While false positives in our testing have been very low so far, we do recommend carefully thinking about your channel's normal proxy policy as banning based on detections through this system will be placing trust in third party blacklists to be accurate and responsible. <br />
<br />
For any help regarding restricting proxies in your channel, please ask in #help.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Proxy&diff=5060Proxy2009-10-03T18:08:25Z<p>MIXX941: Update for 2009 proxy policies/features</p>
<hr />
<div>MIXXnet allows connections to the network using a proxy. While we do not globally deny access to proxied connections under normal circumstances, we do have mechanisms in place which provide channel operators fine control over what is and what is not allowed in their channels. This article will outline MIXXnet's network-wide proxy policies and how we handle connections made through proxies.<br />
<br />
==General Information==<br />
All connections made to the network are checked against various Domain Name Service Blacklists (DNSBLs) which can identify potential sources of abuse. Port scans may also be performed to check for active open proxies running on your IP address. If the IP address you are connecting from is detected as being a proxy, you will receive a private message from "ProxyGuard" notifying you of this and your hostname will be altered with one of the following appended to the end:<br />
<br />
*.dnsbl.proxy - IP address is on a blacklist that we check against<br />
*.tor.proxy - Tor Project exit node that allows connections to IRC ports<br />
<br />
If your IP address is on a blacklist, you will be given removal instructions via private message. Please follow these instructions to get your IP removed from the blacklist and reconnect to MIXXnet when the removal process is complete. If the removal process is successful, you should no longer be detected as a proxy and your normal hostname should be shown on the network.<br />
<br />
Channel operators have the option of banning some or all users that are detected as using a proxy. If you are detected and notified, please be aware that you may not be able to join certain channels on the network until you are removed from the blacklist. This is entirely a channel's decision and we as a network will not override this channel policy.<br />
<br />
MIXXnet reserves the right to impose temporary global limits or restrictions on proxied connections if a situation warrants.<br />
<br />
If you have any questions about or need help regarding connections through proxies, please ask in #help.<br />
<br />
==Channel Implementation==<br />
MIXXnet provides the ability for channels to restrict access to users using proxies which can help with potential abuse issues like bot floods or ban evasion. This is not enabled by default in any channels, however it can be set and removed at will by channel operators. Blocking proxied connections is handled through channel mode "b" (ban). The following is a list of hostmasks you can ban to block proxies from your channel:<br />
<br />
* *!*@*.dnsbl.proxy - Block users whose IP is blacklisted as an abusive IP (does not include Tor)<br />
* *!*@*.tor.proxy - Block users who are connecting through the Tor Project<br />
* *!*@*.proxy - Block all detected proxies<br />
<br />
If your channel blocks some or all of the above proxies and a user attempts to join, they will be notified that they are banned. We understand that this might not be the most desired behavior, however we have come up with a couple methods to help the user know why they are banned and how to fix it.<br />
<br />
1) Anytime a user is detected as being a proxy, they will receive a private message notifying them of this which provides a link to this article with the explanation above as well as instructions for removal if possible. This should hopefully clarify why they are banned from your channel, and once they are removed from the blacklist they will be allowed to join immediately upon reconnecting to IRC.<br />
<br />
2) Channel operators also have the option of setting a channel to redirect users to if they are banned and attempt to join. In this case, you should direct users who are banned due to using a proxy to #proxyhelp to receive further help on this issue. For example, to block all proxies and redirect proxied users to #proxyhelp:<br />
<br />
/mode #channel +b *!*@*.proxy#proxyhelp<br />
<br />
While false positives in our testing have been very low so far, we do recommend carefully thinking about your channel's normal proxy policy as banning based on detections through this system will be placing trust in third party blacklists to be accurate and responsible. <br />
<br />
For any help regarding restricting proxies in your channel, please ask in #help.</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=HostServ&diff=5059HostServ2009-10-02T01:49:29Z<p>MIXX941: Change #services to #help as channels are now merged</p>
<hr />
<div>'''HostServ''' is a MIXXnet [[Services|service]] that gives users a free vhost to hide their real IP address/hostname. A user can request a free vhost by asking in #help. The generic free vhost is in the form of: "registerednick.users.mixxnet.net". We do not currently provide custom vhosts except in very special cases.<br />
<br />
<br />
'''To request a vhost using our new automated system, join #help and type: !vhost assign'''<br />
<br />
<br />
==HostServ Commands==<br />
===ON===<br />
<br />
Syntax: /msg HostServ ON<br />
<br />
Activates the vhost currently assigned to the nick in use.<br />
When you use this command, any user who performs a /whois<br />
on you will see the vhost instead of your real IP address.<br />
<br />
===OFF===<br />
<br />
Syntax: /msg HostServ OFF<br />
<br />
Deactivates the vhost currently assigned to the nick in use.<br />
When you use this command any user who performs a /whois<br />
on you will see your real IP address.<br />
<br />
===GROUP===<br />
<br />
Syntax: /msg HostServ GROUP<br />
<br />
This command allows users to set the vhost of their<br />
CURRENT nick to be the vhost for all nicks in the same<br />
group.<br />
<br />
[[Category:Anope]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Channel&diff=5058Channel2009-08-25T22:12:27Z<p>MIXX941: Removed spam</p>
<hr />
<div><p>A '''channel''' is a virtual space on an IRC server. Users join channels and chat. IRC servers can have many channels. Messages sent to one channel are not seen in another.</p><br />
Taken from [http://www.mirc.co.uk/irc.html Intro to IRC]:<br />
<br />
<p>It is not uncommon for an IRC server to have dozens, hundreds or even thousands of chat channels open simultaneously. There are some more or less permanent channels, but others come and go. Although a channel's name usually reflects the general nature of the conversation within, each channel can also have a specific topic. Channel names tend to remain constant, while topics change continuously. For example, in a channel called "PC Users" the topic might be "Windows 95 Bug Fixes" one day and "How to Choose a High Speed Modem" the next day.</p><br />
<p>You'll notice that all channel names begin with #. One popular and longstanding channel, for instance, is #help. If you decide to wade in, just type: '/JOIN #chat' and voila, you're in. Type in some greetings and you'll see them appear on screen, along with whatever everyone else types.</p><br />
<br />
{{stub}}</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=Main_Page&diff=5057Main Page2009-08-25T22:10:17Z<p>MIXX941: Added vhost article</p>
<hr />
<div>Welcome to the MIXXnet Wiki. Here you will find user and staff contributed documents about [[MIXXnet]] and [[IRC]] in general. We encourage users to help out our documentation project by contributing information, however due to spam, editing can now only be done if you have registered and logged in.<br />
<br />
If you have any questions and need immediate help, log on to IRC: <br />
<br />
'''irc.mixxnet.net / #help'''<br />
<br />
You can use the search box to your left to search for articles that others have written or you can click [[Special:Allpages|here]] to browse all articles.<br />
<br />
== Getting Started ==<br />
Here are some articles that will help you get started on MIXXnet:<br />
<br />
* [[Channel_Start_Guide|Channel Start Guide - A complete guide to starting a channel]]<br />
* [[Channel_Modes|Channel Modes List]]<br />
* [[HostServ|vhost Information - Assign or remove a vhost on your nickname]]<br />
* [[SSL|SSL Information]]<br />
* [[IRC_client|Popular IRC Clients List]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=XChat&diff=5056XChat2009-08-24T01:38:52Z<p>MIXX941: /* Using SSL */ Changed link for SSL setup</p>
<hr />
<div>[[XChat]] is an open source graphical [[IRC Client]] created by Peter Zelenzy. <br />
==About XChat==<br />
It was originally made to run on UNIX/Linux systems using the X Windows system, but also runs on Windows and Mac OS X. It has been confirmed to work on the following operating systems:<br />
<br />
* GNU-Linux<br />
* FreeBSD<br />
* NetBSD<br />
* OpenBSD<br />
* Solaris<br />
* AIX<br />
* IRIX<br />
* DEC/Compaq Tru64 UNIX<br />
* HP-UX 10.20 and 11<br />
* Mac OS X<br />
* Windows 98/ME/NT/2000/XP<br />
<br />
The source code is released under the GPL and can be obtained for free from [http://www.xchat.org http://www.xchat.org]. Windows binaries are also available from several third party sources. Check [http://b0at.tx0.org/xchat/ here] for some free Windows binaries.<br />
<br />
[[Image:Xchat_screenshot.jpg|thumb]]<br />
<br />
==XChat Setup Guide==<br />
<br />
The following guide was written for the latest version of XChat, and applies to it on all operating systems. For a guide to old XChat versions including screenshots, see [http://www.mixxnet.net/xchat.php this].<br />
<br />
===1. Download and Install XChat===<br />
<br />
For Windows users I recommend the [http://silverex.info/ SilvereX build], although there are [http://b0at.tx0.org/xchat/ other free builds]. For *nix users, get the source tarball or binaries for your operating system via your package management system or through the [http://xchat.org official site].<br />
<br />
Once downloaded, install XChat for your operating system.<br />
<br />
===2. Configure User Details===<br />
<br />
Once you have XChat installed, launch it, and you will see a box like this:<br />
<br />
[[Image:Xchat_serverlist.jpg]]<br />
<br />
In the top box, enter a "Nickname" to use while on IRC. This is what you will be known as. In the Second and Third Choice boxes, enter alternate nicknames in case your primary nick is already taken. <br />
<br />
In the "User Name" box, put in your nickname again unless you have a specific reason to enter something else. You could also enter in your first name as your "User Name", but remember that the "Nickname" is what you will be signed in as. <br />
<br />
In the "Real Name" box, you can enter your full name or anything you want.<br />
<br />
At this point, you can connect to MIXXnet without setting any further options. Simply scroll down to "MIXXnet" on the server list, highlight it, and click "Connect". This will connect you to MIXXnet with no special options set. You may join channels manually by typing "/join #channelname", or if you would like a more detailed description on how to automatically join channels on connect, read on.<br />
<br />
===3. Configuring Server Options===<br />
<br />
In the "Networks" area of the "Server List" window, scroll down to MIXXnet. Highlight it, and then click the "Edit" button to the right. That will bring up this dialog box: <br />
<br />
[[Image:Xchat_edit_mixxnet.jpg]]<br />
<br />
The server "irc.mixxnet.net" should already be listed there. This is the round robin pool that is updated often with the most stable MIXXnet servers. Unless you need to use [[IPv6]] or [[SSL]], leave "irc.mixxnet.net" there at the top.<br />
<br />
Unless you have reasons to do otherwise, leave the "Use Global User Information" checkbox selected. <br />
<br />
In the bottom area, you have several options available to you:<br />
<br />
====Auto Connect to Network at Startup====<br />
Use this option if you want to connect to MIXXnet right away when starting XChat.<br />
<br />
====Use a Proxy Server====<br />
This option is for if you are connecting through a proxy server to get to MIXXnet. Uncheck this unless you know you need it on.<br />
<br />
====Using SSL====<br />
The next checkbox says "Use SSL for All Server on This Network". If you are familiar with SSL and want to use it, then check this box. If you would like to know more about SSL and how to set it up in XChat, please see the guide [[SSL#XChat|here]].<br />
<br />
====Joining Channels====<br />
If you want to automatically join channels when you connect to MIXXnet, type in the channels you want to join here separated by commas. Here is an example:<br />
<br />
#chat,#party107,#armind<br />
<br />
To see a list of some popular channels on MIXXnet, check out [http://denora.mixxnet.net/?m=c&p=list Denora's Channel List]<br />
<br />
If you do not want to set any channels up to join everytime you connect, you can leave this box blank. Just note that when you connect, you will have to join channels each time manually by using:<br />
<br />
/join #channel<br />
<br />
====Connect Command====<br />
This setting is for if you need XChat to do something upon connecting. For our purposes, we don't need to touch this option.<br />
<br />
====NickServ Password====<br />
Here is where you can enter in your [[NickServ]] password to automatically identify upon connecting. After you get familiar with IRC and the network, you can register your nickname with NickServ so that nobody else can use it. This is the area to enter your NickServ password when you do that. <br />
<br />
====Server Password====<br />
This section is not relevant to MIXXnet. <br />
<br />
===4. Connecting===<br />
Now it's time to connect. Click the "Close" button on the "Edit MIXXnet" window, and then "Connect" on the Server List.<br />
<br />
You are now connected to MIXXnet and if you specified any channels to join, they will be joined for you.<br />
<br />
If you have any more questions, please type: /join #help <br />
<br />
[[Category:IRC Clients]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=SSL&diff=5055SSL2009-08-24T01:35:47Z<p>MIXX941: Removed a couple irrelevant external links and changed link order</p>
<hr />
<div>'''Secure Sockets Layer''' ('''SSL''') is a cryptographic protocol which provides secure communication on the Internet.<br />
<br />
==General Information==<br />
Users may connect to the [[MIXXnet|MIXXnet IRC network]] using any server on the network. '''The default port is 6697 unless listed otherwise'''.<br />
<br />
When you use SSL, you are establishing a secure connection between you and the server. As of February 11, 2006, MIXXnet operates with full SSL support including client-to-server connections and server-to-server links.<br />
<br />
Users may download a copy of the CA certificate MIXXnet uses which can be imported into some clients to allow for a "trusted" connection. It is not necessary for you to do this, but the option is available to you. More information about installing MIXXnet's CA certificate can be found [[#CA_Certificate|here]].<br />
<br />
==User & Channel Information==<br />
===Identification===<br />
To check to see if a user is using SSL, simply whois that user. A secured user's whois would look something like:<br />
<br />
Chris is chris@staff.mixxnet.net * Chris<br />
Chris using [[anjuna.il.us.mixxnet.net]] Anjunabeats MIXXnet IRC Server<br />
'''Chris is using a Secure Connection'''<br />
Chirs End of /WHOIS list.<br />
<br />
This means that the user "Chris" is using SSL on anjuna.il.us.mixxnet.net.<br />
<br />
===Channel Protection===<br />
In a secure channel, all of the users must have SSL enabled for the channel to be secure. If one user isn't secure, then all the messages will go to that user unencrypted. '''SSL users and non-SSL users can co-exist on the same channel.''' If you wish to limit your channel to only people using SSL, you can set the channel mode +z (/mode #channel +z). The +z mode prevents non-SSL users from joining the channel. If a non-SSL user does try to join, (s)he will see this message:<br />
<br />
<nowiki>#channel unable to join channel (not using secure connection)</nowiki><br />
<br />
==Client Setup==<br />
===XChat===<br />
To use SSL in [[XChat]], click '''XChat->Network List'''. Next, click on MIXXnet and '''Edit'''. Then select the two check boxes that say '''Use SSL for all servers on this network''' and '''Accept invalid SSL certificate''' as shown below.<br />
[[Image:ssl_setup_xchat.png|thumb|250px|Screenshot of X-Chat with SSL enabled.]]<br />
<br />
<br />
<br />
===mIRC===<br />
[[mIRC]] requires that you have the Windows version of OpenSSL installed on your system. You can download OpenSSL for Windows at [http://www.shininglightpro.com/products/Win32OpenSSL.html this website]. More information on how to install OpenSSL for Windows is beyond the scope of this document. To check if you've installed OpenSSL correctly, look for the '''SSL''' button in the '''mIRC Options''' window as shown below.<br />
[[Image:ssl_setup_mirc.png|thumb|250px|Screenshot of mIRC with SSL enabled.]]<br />
If you have SSL enabled, choose a server from the '''Servers''' section above. Type: /server servername.xx.xx.mixnet.net +6697. The '+' sign is important because it tells mIRC to use SSL.<br />
<br />
When trying to connect to a SSL enabled server, you may be presented with a dialog that says the SSL certificate is invalid. As long as the certificate has not expired and the domain name matches, the certificate is OK. The reason you are seeing this dialog is because MIXXnet acts as its own certificate authority.<br />
<br />
===Irssi===<br />
The use of SSL in Irssi is ''very'' simple. All you need to do is type the following commands into the status window:<br><br />
/set use_ssl on<br><br />
/set ssl_verify on<br><br />
/save<br><br />
After you have done these, you need to pass the -ssl flag to /connect when connecting to an SSL enabled server. For example:<br><br />
/connect -ssl anjuna.il.us.mixxnet.net 6697<br />
<br />
===Other Clients===<br />
Other clients that support SSL include [http://www.bitchx.org BitchX], [http://weechat.flashtux.org/ WeeChat], [http://www.kvirc.de/ KVirc], [http://pidgin.im Pidgin], [http://colloquy.info/ Colloquy], [http://www.opera.com Opera], [http://www.ircle.com/ Ircle], and [http://www.snak.com/ Snak] to name a few.<br />
<br />
==CA Certificate==<br />
If you would like to install MIXXnet's CA certificate for use in your IRC client to establish a trusted connection and avoid having to accept an "invalid" SSL certificate, please follow the steps below.<br />
<br />
===Windows===<br />
For clients that use OpenSSL (XChat, mIRC), download MIXXnet's [http://mixxnet.net/mixxnet.crt CA Certificate] to your computer and move it to the following directory (creating the directory structure if it does not already exist): '''C:\usr\local\ssl\certs\'''<br />
<br />
When mixxnet.crt is in that directory, rename it to the following (the ".0" at the end is required): '''6730e552.0'''<br />
<br />
'''NOTE:''' If you are using the SilvereX Windows build of XChat 2.8.6-1 or 2.8.6-2, the path is different due to a bug. The correct path is: '''C:\some\openssl\dir\ssl\certs\6730e552.0'''<br />
<br />
===Mac OS X===<br />
Download MIXXnet's [http://mixxnet.net/mixxnet.crt CA Certificate] and rename it from mixxnet.crt to '''6730e552.0'''. Then move that file to '''/System/Library/OpenSSL/certs/'''<br />
<br />
===Linux/BSD===<br />
Download and move MIXXnet's [http://mixxnet.net/mixxnet.crt CA Certificate] to the path where OpenSSL is configured to look for trusted certificates. This directory varies by Linux distribution or BSD version, however common paths include: /etc/ssl/certs/, /usr/local/openssl/certs/, /usr/share/ssl/certs/, and /usr/local/ssl/certs/.<br />
<br />
Once the CA cert is moved to that directory, make a symlink with the cert's fingerprint and ".0" appended at the end so that OpenSSL can properly detect the certificate:<br />
<br />
ln -s mixxnet.crt 6730e552.0<br />
<br />
Tip: The filename above was derived from the command: $ openssl x509 -in mixxnet.crt -noout -hash<br />
<br />
==External Links==<br />
*[http://en.wikipedia.org/wiki/Transport_Layer_Security SSL Wikipedia Page]<br />
*[http://www.openssl.org/ OpenSSL Website]<br />
*[http://www.mirc.co.uk/ssl.html Using SSL with mIRC]<br />
<br />
[[Category:Services]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=HostServ&diff=5054HostServ2009-08-16T18:36:27Z<p>MIXX941: Change "request" to "assign" per the in-channel help</p>
<hr />
<div>'''HostServ''' is a MIXXnet [[Services|service]] that gives users a free vhost to hide their real IP address/hostname. A user can request a free vhost by asking in #services. The generic free vhost is in the form of: "registerednick.users.mixxnet.net". We do not currently provide custom vhosts except in very special cases.<br />
<br />
<br />
'''To request a vhost using our new automated system, join #services and type: !vhost assign'''<br />
<br />
<br />
==HostServ Commands==<br />
===ON===<br />
<br />
Syntax: /msg HostServ ON<br />
<br />
Activates the vhost currently assigned to the nick in use.<br />
When you use this command, any user who performs a /whois<br />
on you will see the vhost instead of your real IP address.<br />
<br />
===OFF===<br />
<br />
Syntax: /msg HostServ OFF<br />
<br />
Deactivates the vhost currently assigned to the nick in use.<br />
When you use this command any user who performs a /whois<br />
on you will see your real IP address.<br />
<br />
===GROUP===<br />
<br />
Syntax: /msg HostServ GROUP<br />
<br />
This command allows users to set the vhost of their<br />
CURRENT nick to be the vhost for all nicks in the same<br />
group.<br />
<br />
[[Category:Anope]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=SSL&diff=5052SSL2009-08-07T21:25:55Z<p>MIXX941: /* Linux/BSD */ s/copied/moved</p>
<hr />
<div>'''Secure Sockets Layer''' ('''SSL''') is a cryptographic protocol which provides secure communication on the Internet.<br />
<br />
==General Information==<br />
Users may connect to the [[MIXXnet|MIXXnet IRC network]] using any server on the network. '''The default port is 6697 unless listed otherwise'''.<br />
<br />
When you use SSL, you are establishing a secure connection between you and the server. As of February 11, 2006, MIXXnet operates with full SSL support including client-to-server connections and server-to-server links.<br />
<br />
Users may download a copy of the CA certificate MIXXnet uses which can be imported into some clients to allow for a "trusted" connection. It is not necessary for you to do this, but the option is available to you. More information about installing MIXXnet's CA certificate can be found [[#CA_Certificate|here]].<br />
<br />
==User & Channel Information==<br />
===Identification===<br />
To check to see if a user is using SSL, simply whois that user. A secured user's whois would look something like:<br />
<br />
Chris is chris@staff.mixxnet.net * Chris<br />
Chris using [[anjuna.il.us.mixxnet.net]] Anjunabeats MIXXnet IRC Server<br />
'''Chris is using a Secure Connection'''<br />
Chirs End of /WHOIS list.<br />
<br />
This means that the user "Chris" is using SSL on anjuna.il.us.mixxnet.net.<br />
<br />
===Channel Protection===<br />
In a secure channel, all of the users must have SSL enabled for the channel to be secure. If one user isn't secure, then all the messages will go to that user unencrypted. '''SSL users and non-SSL users can co-exist on the same channel.''' If you wish to limit your channel to only people using SSL, you can set the channel mode +z (/mode #channel +z). The +z mode prevents non-SSL users from joining the channel. If a non-SSL user does try to join, (s)he will see this message:<br />
<br />
<nowiki>#channel unable to join channel (not using secure connection)</nowiki><br />
<br />
==Client Setup==<br />
===XChat===<br />
To use SSL in [[XChat]], click '''XChat->Network List'''. Next, click on MIXXnet and '''Edit'''. Then select the two check boxes that say '''Use SSL for all servers on this network''' and '''Accept invalid SSL certificate''' as shown below.<br />
[[Image:ssl_setup_xchat.png|thumb|250px|Screenshot of X-Chat with SSL enabled.]]<br />
<br />
<br />
<br />
===mIRC===<br />
[[mIRC]] requires that you have the Windows version of OpenSSL installed on your system. You can download OpenSSL for Windows at [http://www.shininglightpro.com/products/Win32OpenSSL.html this website]. More information on how to install OpenSSL for Windows is beyond the scope of this document. To check if you've installed OpenSSL correctly, look for the '''SSL''' button in the '''mIRC Options''' window as shown below.<br />
[[Image:ssl_setup_mirc.png|thumb|250px|Screenshot of mIRC with SSL enabled.]]<br />
If you have SSL enabled, choose a server from the '''Servers''' section above. Type: /server servername.xx.xx.mixnet.net +6697. The '+' sign is important because it tells mIRC to use SSL.<br />
<br />
When trying to connect to a SSL enabled server, you may be presented with a dialog that says the SSL certificate is invalid. As long as the certificate has not expired and the domain name matches, the certificate is OK. The reason you are seeing this dialog is because MIXXnet acts as its own certificate authority.<br />
<br />
===Irssi===<br />
The use of SSL in Irssi is ''very'' simple. All you need to do is type the following commands into the status window:<br><br />
/set use_ssl on<br><br />
/set ssl_verify on<br><br />
/save<br><br />
After you have done these, you need to pass the -ssl flag to /connect when connecting to an SSL enabled server. For example:<br><br />
/connect -ssl anjuna.il.us.mixxnet.net 6697<br />
<br />
===Other Clients===<br />
Other clients that support SSL include [http://www.bitchx.org BitchX], [http://weechat.flashtux.org/ WeeChat], [http://www.kvirc.de/ KVirc], [http://pidgin.im Pidgin], [http://colloquy.info/ Colloquy], [http://www.opera.com Opera], [http://www.ircle.com/ Ircle], and [http://www.snak.com/ Snak] to name a few.<br />
<br />
==CA Certificate==<br />
If you would like to install MIXXnet's CA certificate for use in your IRC client to establish a trusted connection and avoid having to accept an "invalid" SSL certificate, please follow the steps below.<br />
<br />
===Windows===<br />
For clients that use OpenSSL (XChat, mIRC), download MIXXnet's [http://mixxnet.net/mixxnet.crt CA Certificate] to your computer and move it to the following directory (creating the directory structure if it does not already exist): '''C:\usr\local\ssl\certs\'''<br />
<br />
When mixxnet.crt is in that directory, rename it to the following (the ".0" at the end is required): '''6730e552.0'''<br />
<br />
'''NOTE:''' If you are using the SilvereX Windows build of XChat 2.8.6-1 or 2.8.6-2, the path is different due to a bug. The correct path is: '''C:\some\openssl\dir\ssl\certs\6730e552.0'''<br />
<br />
===Mac OS X===<br />
Download MIXXnet's [http://mixxnet.net/mixxnet.crt CA Certificate] and rename it from mixxnet.crt to '''6730e552.0'''. Then move that file to '''/System/Library/OpenSSL/certs/'''<br />
<br />
===Linux/BSD===<br />
Download and move MIXXnet's [http://mixxnet.net/mixxnet.crt CA Certificate] to the path where OpenSSL is configured to look for trusted certificates. This directory varies by Linux distribution or BSD version, however common paths include: /etc/ssl/certs/, /usr/local/openssl/certs/, /usr/share/ssl/certs/, and /usr/local/ssl/certs/.<br />
<br />
Once the CA cert is moved to that directory, make a symlink with the cert's fingerprint and ".0" appended at the end so that OpenSSL can properly detect the certificate:<br />
<br />
ln -s mixxnet.crt 6730e552.0<br />
<br />
==External Links==<br />
*[http://www.openssl.org/ OpenSSL Website]<br />
*[http://www.bodhost.com/web-hosting/index.php/2007/09/01/difference-between-shared-ssl-and-dedicated-ssl/ Using SSL as a Option]<br />
*[http://www.mirc.co.uk/ssl.html Using SSL with mIRC]<br />
*[http://irssi.org irssi Website]<br />
*[http://en.wikipedia.org/wiki/Transport_Layer_Security SSL Wikipedia Page]<br />
<br />
[[Category:Services]]</div>MIXX941https://www.mixxnet.net/wiki/index.php?title=SSL&diff=5051SSL2009-08-07T20:50:33Z<p>MIXX941: s/copy/move</p>
<hr />
<div>'''Secure Sockets Layer''' ('''SSL''') is a cryptographic protocol which provides secure communication on the Internet.<br />
<br />
==General Information==<br />
Users may connect to the [[MIXXnet|MIXXnet IRC network]] using any server on the network. '''The default port is 6697 unless listed otherwise'''.<br />
<br />
When you use SSL, you are establishing a secure connection between you and the server. As of February 11, 2006, MIXXnet operates with full SSL support including client-to-server connections and server-to-server links.<br />
<br />
Users may download a copy of the CA certificate MIXXnet uses which can be imported into some clients to allow for a "trusted" connection. It is not necessary for you to do this, but the option is available to you. More information about installing MIXXnet's CA certificate can be found [[#CA_Certificate|here]].<br />
<br />
==User & Channel Information==<br />
===Identification===<br />
To check to see if a user is using SSL, simply whois that user. A secured user's whois would look something like:<br />
<br />
Chris is chris@staff.mixxnet.net * Chris<br />
Chris using [[anjuna.il.us.mixxnet.net]] Anjunabeats MIXXnet IRC Server<br />
'''Chris is using a Secure Connection'''<br />
Chirs End of /WHOIS list.<br />
<br />
This means that the user "Chris" is using SSL on anjuna.il.us.mixxnet.net.<br />
<br />
===Channel Protection===<br />
In a secure channel, all of the users must have SSL enabled for the channel to be secure. If one user isn't secure, then all the messages will go to that user unencrypted. '''SSL users and non-SSL users can co-exist on the same channel.''' If you wish to limit your channel to only people using SSL, you can set the channel mode +z (/mode #channel +z). The +z mode prevents non-SSL users from joining the channel. If a non-SSL user does try to join, (s)he will see this message:<br />
<br />
<nowiki>#channel unable to join channel (not using secure connection)</nowiki><br />
<br />
==Client Setup==<br />
===XChat===<br />
To use SSL in [[XChat]], click '''XChat->Network List'''. Next, click on MIXXnet and '''Edit'''. Then select the two check boxes that say '''Use SSL for all servers on this network''' and '''Accept invalid SSL certificate''' as shown below.<br />
[[Image:ssl_setup_xchat.png|thumb|250px|Screenshot of X-Chat with SSL enabled.]]<br />
<br />
<br />
<br />
===mIRC===<br />
[[mIRC]] requires that you have the Windows version of OpenSSL installed on your system. You can download OpenSSL for Windows at [http://www.shininglightpro.com/products/Win32OpenSSL.html this website]. More information on how to install OpenSSL for Windows is beyond the scope of this document. To check if you've installed OpenSSL correctly, look for the '''SSL''' button in the '''mIRC Options''' window as shown below.<br />
[[Image:ssl_setup_mirc.png|thumb|250px|Screenshot of mIRC with SSL enabled.]]<br />
If you have SSL enabled, choose a server from the '''Servers''' section above. Type: /server servername.xx.xx.mixnet.net +6697. The '+' sign is important because it tells mIRC to use SSL.<br />
<br />
When trying to connect to a SSL enabled server, you may be presented with a dialog that says the SSL certificate is invalid. As long as the certificate has not expired and the domain name matches, the certificate is OK. The reason you are seeing this dialog is because MIXXnet acts as its own certificate authority.<br />
<br />
===Irssi===<br />
The use of SSL in Irssi is ''very'' simple. All you need to do is type the following commands into the status window:<br><br />
/set use_ssl on<br><br />
/set ssl_verify on<br><br />
/save<br><br />
After you have done these, you need to pass the -ssl flag to /connect when connecting to an SSL enabled server. For example:<br><br />
/connect -ssl anjuna.il.us.mixxnet.net 6697<br />
<br />
===Other Clients===<br />
Other clients that support SSL include [http://www.bitchx.org BitchX], [http://weechat.flashtux.org/ WeeChat], [http://www.kvirc.de/ KVirc], [http://pidgin.im Pidgin], [http://colloquy.info/ Colloquy], [http://www.opera.com Opera], [http://www.ircle.com/ Ircle], and [http://www.snak.com/ Snak] to name a few.<br />
<br />
==CA Certificate==<br />
If you would like to install MIXXnet's CA certificate for use in your IRC client to establish a trusted connection and avoid having to accept an "invalid" SSL certificate, please follow the steps below.<br />
<br />
===Windows===<br />
For clients that use OpenSSL (XChat, mIRC), download MIXXnet's [http://mixxnet.net/mixxnet.crt CA Certificate] to your computer and move it to the following directory (creating the directory structure if it does not already exist): '''C:\usr\local\ssl\certs\'''<br />
<br />
When mixxnet.crt is in that directory, rename it to the following (the ".0" at the end is required): '''6730e552.0'''<br />
<br />
'''NOTE:''' If you are using the SilvereX Windows build of XChat 2.8.6-1 or 2.8.6-2, the path is different due to a bug. The correct path is: '''C:\some\openssl\dir\ssl\certs\6730e552.0'''<br />
<br />
===Mac OS X===<br />
Download MIXXnet's [http://mixxnet.net/mixxnet.crt CA Certificate] and rename it from mixxnet.crt to '''6730e552.0'''. Then move that file to '''/System/Library/OpenSSL/certs/'''<br />
<br />
===Linux/BSD===<br />
Download and move MIXXnet's [http://mixxnet.net/mixxnet.crt CA Certificate] to the path where OpenSSL is configured to look for trusted certificates. This directory varies by Linux distribution or BSD version, however common paths include: /etc/ssl/certs/, /usr/local/openssl/certs/, /usr/share/ssl/certs/, and /usr/local/ssl/certs/.<br />
<br />
Once the CA cert is copied to that directory, make a symlink with the cert's fingerprint and ".0" appended at the end so that OpenSSL can properly detect the certificate:<br />
<br />
ln -s mixxnet.crt 6730e552.0<br />
<br />
==External Links==<br />
*[http://www.openssl.org/ OpenSSL Website]<br />
*[http://www.bodhost.com/web-hosting/index.php/2007/09/01/difference-between-shared-ssl-and-dedicated-ssl/ Using SSL as a Option]<br />
*[http://www.mirc.co.uk/ssl.html Using SSL with mIRC]<br />
*[http://irssi.org irssi Website]<br />
*[http://en.wikipedia.org/wiki/Transport_Layer_Security SSL Wikipedia Page]<br />
<br />
[[Category:Services]]</div>MIXX941