This file is indexed.

/usr/share/doc/dancer-ircd/dancer-user-guide.html/channels.htm is in dancer-ircd-doc 1.0.36-8ubuntu1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Channel management</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="Users guide for the dancer IRC server"
HREF="index.htm"><LINK
REL="PREVIOUS"
TITLE="Users and umodes"
HREF="users.htm"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Users guide for the dancer IRC server</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="users.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
>&nbsp;</TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="CHANNELS"
></A
>Chapter 4. Channel management</H1
><P
>      It is strongly recommended that channels be registered on FN. To do this, become a channel
      operator somehow and "/msg chanserv register #channel password". You can access full online help
      for chanserv, as well as the other services, with "/msg chanserv help". The channel access list
      controls who can do what on the channel, and allows considerable flexibility. Use this rather than
      channel management bots, it's more reliable and avoids sillyness like IRC wars.
    </P
><P
>      Channel bans and quiets both prevent a person from talking on the channel, but it is recommended
      that you use quiets (+q) if you merely want to shut somebody up; bans are rather deprecated for
      this purpose and their semantics will change at some point in the future.  Generally you should
      assume that a ban means you don't want the person on the channel, while a quiet means you don't
      want them saying anything. Please don't kick people, it's rarely necessary or appropriate, and it
      generates needless noise (as well as raising the channel temperature).
    </P
><P
>      Hybrid (and therefore dancer) provides ban exceptions. If you have problems from an ISP which
      allows users to trivially change their IP addresses then you may find yourself forced to place a
      ban on the entire ISP. This often catches legitimate users. Set ban exceptions just like normal
      bans, but with mode +e (/mode #channel +e nick!user@host). These users will then be exempt from
      bans. You can then ban by host, but allow specific users by nick, should you need to.
    </P
><P
>      Another system available is the channel invex list. A channel which is set +i is invite-only, but
      masks can be added to the invex list with mode +I in the same manner, and the people on the list
      will be able to join without being invited. Note that services cannot (at present) maintain invex
      or exception lists. If a person needs permanent access, then add them to the channel access list in
      chanserv with a level that gives them CMDINVITE access; then can then /msg chanserv invite #channel
      and chanserv will invite them.
    </P
><P
>      Channels which have the +g umode set allow anybody to use the INVITE command; on channels where it
      is unset, only channel operators may use INVITE.
    </P
><P
>      The REMOVE command can be used exactly like the KICK command, only it sends out PART messages.
    </P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="users.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.htm"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Users and umodes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>