mikaela.github.io/blog/_posts/2015-01-24-getting_help_with_channel_issues.md

69 lines
2.8 KiB
Markdown
Raw Normal View History

---
layout: post
2015-02-14 10:51:09 +01:00
comments: true
2024-06-19 07:19:44 +02:00
title:
"Getting help from network operators with channel issues when ops are away"
category: [english]
tags: [irc, english]
2018-11-25 23:51:24 +01:00
redirect_from: /english/2015/01/24/getting_help_with_channel_issues.html
sitemap: true
robots: noai
---
2024-06-19 07:19:44 +02:00
In case you wish network operators to help you when your channel operators are
away, please authorize them to do so. You can do this simply by command
`/msg ChanServ flags #channel $oper +vhoirtAe`. _Note that this assumes that
your network uses Atheme with exttarget $oper loaded._
2024-06-19 07:19:44 +02:00
If you don't do this and there is trouble on your channel, it can be assumed
that you don't want network operators to intervene and they most likely take no
action. Taking action would also require using operator privileges such as
`/samode` which might not be so nice unless the flags are set.
2024-06-19 07:19:44 +02:00
I repeat that the commnd is `/msg ChanServ flags #channel $oper +vhoirtAe`. The
only thing that must be changed is `#channel`.
## Explanation of these flags
2023-02-22 19:28:38 +01:00
- v - allows using voice/devoice commands
- h - allows using halfop/dehalfop commands
- o - allows using op/deop commands
- i - allows using invite/getkey commands
- r - allows using kick/kickban/ban/unban commands
- t - allows using topic/topicappend commands
- A - allows seeing channel access lists and (MemoServ) sendops command
2024-06-19 07:19:44 +02:00
- most of our alerts seem to be coming from opers who are accidentally using
their priviledges and seeing access list of channel they have no access to.
2023-02-22 19:28:38 +01:00
- `<ChanServ> Mikaela ACCESS:LIST: #channel (oper override)`
- e - exempts from akick and allows unbanning yourself
**NOTE THAT FLAGS ARE CASE-SENSITIVE**
### Effects of misspelled flags
Some flags change their meaning if written with wrong case:
2023-02-22 19:28:38 +01:00
- V - automatic voice and allows using voice/devoice on yourself
- H - automatic halfop and allows using halfop/dehalfop on yourself
- O - automatic op and allows using op/deop on yourself
- R - allows using recover, sync and clear commands
2024-06-19 07:19:44 +02:00
- recover - deop everyone, remove key, invite yourself, add ban exception on
yourself, unban yourself, set modes +im (invite-only, only voiced users can
talk), op yourself and other fun...
2023-02-22 19:28:38 +01:00
- sync - sync the channel according to access list
2024-06-19 07:19:44 +02:00
- clear - allows clearing akicks (+b flags), bans, flags, users (=kick
everyone)
2023-02-22 19:28:38 +01:00
- a - allows using protect/deprotect commands
2024-06-19 07:19:44 +02:00
- protect is sometimes also known as admin and is higher than op, but lower
than owner/founder. Combine with +O to make it automatic.
2024-06-19 07:19:44 +02:00
So you don't want to accidentally confuse different letters. `+VHO` aren't so
dangerous and you can freely set them, but avoid confusing +r and +R and
2015-01-24 14:14:14 +01:00
avoiding confusing +A and +a can also be a good idea.
## One last note
2024-06-19 07:19:44 +02:00
`$oper` matches everyone who is opered and requires Atheme to have exttarget
$oper loaded. Some other networks use different ways to add opers to be on
access list.