Idea: Having #opers and &status channel

[pcho]

Is there a possibility for default and disabled for any unprivileged users #opers channel? With option to enable it in ircd.yaml as not everyone needs it, but with more opers then one it would be nice to auto join them there when they oper up.

Second idea is to have some kind of special status channel for IRC operators that will persistently store all of the SNOMASKS information that normally displays in server status window. Which is great and should still be like this, but not so much for operators that disconnect for few days, have other problems with their IRC client or VPS, and still want to know what happened under their absence.

[slingamn]

Definitely worth considering if it can help persuade people to abandon their terminal clients or bouncers :-)

Joining the channel would be gated on having the snomasks operator capability (the ability to add and remove arbitrary snomasks).

[slingamn]

Via @Mikaela : possibly global notices too?

[Mikaela]

For us #opers is the normal network support channel, so I would hope this to not suddenly get forced on us.

On snotices, I think #services would be traditional channel at least for previous Atheme users.

[pcho]

For us #opers is the normal network support channel, so I would hope this to not suddenly get forced on us.

Agree, this should be an option to switch on or off depending on needs.

[tacerus]

Partially related: #1492

[benharri]

inspircd uses +O to make a channel oper-only which is better than hardcoding a particular channel name

[FiskFan1999]

For the oper-only channel, I don't think it is necessary to add any hard-coded channel because you can make a secret invite-only channel with invite-masks for operator hostmasks set in the opers: block of ircd.yaml. As for the services channel, that could be done by a bot, which could log it in some channel or somewhere else, so it may be worth considering leaving this to the netops to handle as they please.