Skip to content

Commit d065350

Browse files
authored
Add mentions of cs OP (#162)
* Add mentions of cs OP * Mention ChanServ SECURE preventing temp op/voice
1 parent 5c3818e commit d065350

File tree

1 file changed

+38
-10
lines changed

1 file changed

+38
-10
lines changed

content/_guides/creatingchannels.md

Lines changed: 38 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -90,14 +90,22 @@ Congratulations on your new Libera.Chat channel!
9090

9191
### Troubleshooting
9292

93-
If you do not get the Operator status on join, it could be because there are
94-
people already in the channel. You will need to ask them to leave while you
95-
set it up. If they do not cooperate, you will likely need to pick a new name.
93+
If you do not get the Operator status, but believe you already registered
94+
this channel during a previous session, try using `ChanServ OP`:
9695

97-
If the channel is already registered but not in use, or there are no active
98-
Operators, it may be subject to [expiry](/policies#channels), depending on the
99-
type of namespace it belongs to. As part of the expiry process, staff will
100-
take input from both you and any existing channel members.
96+
```irc
97+
/msg ChanServ OP <#channel>
98+
```
99+
100+
If you did not previously attempt to register, and you do not get the
101+
Operator status on join, it could be because there are people already in the
102+
channel. You will need to ask them to leave while you set it up. If they do
103+
not cooperate, you will likely need to pick a new name.
104+
105+
If the channel is already registered by someone else, but not in use, or there
106+
are no active Operators, it may be subject to [expiry](/policies#channels),
107+
depending on the type of namespace it belongs to. As part of the expiry
108+
process, staff will take input from both you and any existing channel members.
101109

102110
If you are a representative of a project and you wish to use a channel that is
103111
already registered, you can ask staff about a [group registration](/chanreg).
@@ -186,16 +194,36 @@ The permissions you can give are outlined in the output of
186194
`/msg ChanServ HELP FLAGS`, along with instructions about the use of
187195
`TEMPLATE` functionality.
188196

197+
If your channel is **not** set `SECURE`, then you can trial new Operators by
198+
_temporarily_ giving them the Operator status.
199+
200+
```irc
201+
/msg ChanServ OP <#channel> [nickname]
202+
```
203+
204+
Substitute `DEOP` in place of `OP` to remove their status if you don't like
205+
their performance. `VOICE` and `DEVOICE` are the equivalents for giving and
206+
taking Voiced status.
207+
208+
The `SECURE` channel flag limits `OP|DEOP|VOICE|DEVOICE` functionality to
209+
only those who possess the corresponding `ChanServ` flags, which will prevent
210+
people from receiving these statuses on a temporary basis.
211+
189212
**Be very careful who you grant the `F` flag to. They will have full
190213
permissions on the channel and will be able to remove your own `F`.** The `f`
191-
flag will allow them to assign permissions they already have and is thus a
192-
safer option.
214+
flag will allow them to assign or unassign permissions they already have and
215+
is thus a safer option.
193216

194217
Unless the channel is assigned to a registered group you are listed as a Group
195218
Contact (GC) of, you will not have
196219
[GC permissions](#special-instructions-for-group-contacts) and
197220
will not be able to get the channel back without their cooperation or by
198-
[registering as a group](/chanreg)
221+
[registering as a group](/chanreg).
222+
223+
We also recommend against using `+O` or `+V` as these flags mean people will
224+
be given Operator or Voiced status on joining a channel. See
225+
[the catalyst guide](/guides/catalyst#only-be-opped-up-when-necessary)
226+
for the philosophy behind this.
199227

200228
## Other channel settings
201229

0 commit comments

Comments
 (0)