1166051 - Nobody can modify SOP list in #rust

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: Infrastructure: IRC, task)

Description

[Brian Anderson]

Neither I nor other SOPs in #rust can create other SOPs, even though I supposedly have 'founder-level' access to this channel. I'm running e.g. `/msg ChanServ sop #rust add Manishearth`.

As an SOP in #rust I have in the past been able to create other SOPs. It's not clear how we got into this situation, but *somebody* needs to have the power to create new SOPs. Today I had to make requests to #it to get it done.

#rust gets attacked pretty often and receives a lot of action from ircops. Some previous protections may have misconfigured things.

Comment 1

[Ryan S. Scheel [:havvy]]

The general rule is that SOP cannot add to the SOP list, only the founder can. It's possible that those who can auto-owner (mode +q) might also be able to add to the SOP list, but that depends on specifics of Inspired that I've never tested.

Comment 2

[Brian Anderson]

It does seem like +q might be the difference. In #rust and #rust-tools, two channels that I can't sop people in, chanserv gives me +ao when I enter. In #rust-internals, #rustc, and #rust-libs I get +qo.

Comment 3

[Dan Parsons [:lerxst]]

There's really no such thing as "founder-level access", you are either the founder, or you're not. #rust's founder is graydon, so this is the person you should talk to about adding other ops. brson's access level is SOP.

the ChanServ LEVELS command can possibly be used to create more granular access levels for #rust, but that is also something graydon would have to do.

Please re-open if there's anything else I can do.