summaryrefslogtreecommitdiff
path: root/data/anope.example.conf
diff options
context:
space:
mode:
authorSadie Powell <sadie@witchery.services>2022-01-04 14:11:07 +0000
committerSadie Powell <sadie@witchery.services>2022-01-04 14:11:07 +0000
commit8eb6a4da717d7670995a47fbd1b5878df88dd206 (patch)
tree56fa17f935f75b18a6ca11c175b7751294694d8e /data/anope.example.conf
parentec7dfb3675973e0e0ec6df69c871797bc94e8413 (diff)
Update more IRCServices references to reflect the current project.
- If referring to the specific piece of software use "Anope". - If referring to services in general use "services".
Diffstat (limited to 'data/anope.example.conf')
-rw-r--r--data/anope.example.conf26
1 files changed, 13 insertions, 13 deletions
diff --git a/data/anope.example.conf b/data/anope.example.conf
index 5919ac1e6..0a475351a 100644
--- a/data/anope.example.conf
+++ b/data/anope.example.conf
@@ -1,7 +1,7 @@
/*
* Example configuration file for Anope. After making the appropriate
* changes to this file, place it in the Anope conf directory (as
- * specified in the "configure" script, default /home/username/anope/conf)
+ * specified in the "Config" script, default /home/username/anope/conf)
* under the name "anope.conf".
*
* The format of this file is fairly simple: three types of comments are supported:
@@ -120,7 +120,7 @@ define
* This section can be included multiple times, and Anope will attempt to
* connect to each server until it finally connects.
*
- * Each uplink IRCd should have a corresponding configuration to allow services
+ * Each uplink IRCd should have a corresponding configuration to allow Anope
* to link to it.
*
* An example configuration for InspIRCd that is compatible with the below uplink
@@ -202,7 +202,7 @@ uplink
serverinfo
{
/*
- * The hostname that services will be seen as, it must have no conflicts with any
+ * The hostname that Anope will be seen as, it must have no conflicts with any
* other server names on the rest of your IRC network. Note that it does not have
* to be an existing hostname, just one that isn't on your network already.
*/
@@ -215,8 +215,8 @@ serverinfo
description = "Anope IRC Services"
/*
- * The local address that services will bind to before connecting to the remote
- * server. This may be useful for multihomed hosts. If omitted, services will let
+ * The local address that Anope will bind to before connecting to the remote
+ * server. This may be useful for multihomed hosts. If omitted, Anope will let
* the Operating System choose the local address. This directive is optional.
*
* If you don't know what this means or don't need to use it, just leave this
@@ -297,19 +297,19 @@ networkinfo
/*
* Set this to the maximum allowed nick length on your network.
* Be sure to set this correctly, as setting this wrong can result in
- * services being disconnected from the network.
+ * Anope being disconnected from the network.
*/
nicklen = 31
/* Set this to the maximum allowed ident length on your network.
* Be sure to set this correctly, as setting this wrong can result in
- * services being disconnected from the network.
+ * Anope being disconnected from the network.
*/
userlen = 10
/* Set this to the maximum allowed hostname length on your network.
* Be sure to set this correctly, as setting this wrong can result in
- * services being disconnected from the network.
+ * Anope being disconnected from the network.
*/
hostlen = 64
@@ -325,7 +325,7 @@ networkinfo
/*
* Characters allowed in nicknames. This always includes the characters described
* in RFC1459, and so does not need to be set for normal behavior. Changing this to
- * include characters your IRCd doesn't support will cause your IRCd and/or services
+ * include characters your IRCd doesn't support will cause your IRCd and/or Anope
* to break. Multibyte characters are not supported, nor are escape sequences.
*
* It is recommended you DON'T change this.
@@ -337,7 +337,7 @@ networkinfo
* to services, such as BotServ bot hostnames and user vhosts. Changing this is not
* recommended unless you know for sure your IRCd supports whatever characters you are
* wanting to use. Telling services to set a vHost containing characters your IRCd
- * disallows could potentially break the IRCd and/or services.
+ * disallows could potentially break the IRCd and/or Anope.
*
* It is recommended you DON'T change this.
*/
@@ -377,7 +377,7 @@ options
/*
* The case mapping used by services. This must be set to a valid locale name
- * installed on your machine. Services use this case map to compare, with
+ * installed on your machine. Anope uses this case map to compare, with
* case insensitivity, things such as nick names, channel names, etc.
*
* We provide two special casemaps shipped with Anope, ascii and rfc1459.
@@ -484,14 +484,14 @@ options
#usestrictprivmsg = yes
/*
- * If set, services will only show /stats o to IRC Operators. This directive
+ * If set, Anope will only show /stats o to IRC Operators. This directive
* is optional.
*/
#hidestatso = yes
/*
* A space-separated list of U-lined servers on your network, it is assumed that
- * the servers in this list are allowed to set channel modes and services will
+ * the servers in this list are allowed to set channel modes and Anope will
* not attempt to reverse their mode changes.
*
* WARNING: Do NOT put your normal IRC user servers in this directive.