Anonymous user
Forum:Establishing Requests for IRC op/chatmod rights: Difference between revisions
Forum:Establishing Requests for IRC op/chatmod rights (edit)
Revision as of 05:20, 17 January 2013
, 11 years agono edit summary
imported>Lost Labyrinth No edit summary |
imported>MrBenC No edit summary |
||
Line 24:
'''Minor comment''' - Just a heads-up, if we do decide to go ahead with this then we lose the ability to <code>/msg memoserv sendops #wikia-sims <message></code> should we need to send important stuff to all administrators at once (such as twitter logins/passwords, vandalism data etc.). I'm not sure how much of an impact losing that would be but I felt that it's worth noting. {{LabSig}} 22:36, January 15, 2013 (UTC)
'''About Topics (for anyone unaware), and other considerations: '''Topic Lock is enabled in the channel, so anyone without the +t flag is unable to update the topic (ChanServ will revert the topic back to what it was before).
However, Lab is incorrect about a few things he mentioned. +o does grant the ability to voice anyone, but it's +f that grants the ability to have ChanServ auto-voice someone. Anyone with an @ prefix can simply type ''/mode +v SomeNickHere'' or ''/mode #channel +v SomeNickHere'' (depending on your IRC client) to grant temporary voice to someone. The only thing ChanServ flag +v allows someone to do is to use ''/cs voice #channel SomeNick'' . Ergo, if you grant +o, you may as well grant +v (or not). I had to point this out because I'm one of (I believe?) three or four individuals with extensive IRC experience (please note that I could very well be wrong about this). I believe this leads well into my next points.
The minute someone is granted Op, they are in my mind a member of the channel staff. As the #wikia-sims channel is run to support TSW, by extension they become a member of the TSW staff. Generally speaking, this means being granted powers that, if granted to the wrong person, can be abused. Therefore, anyone granted these powers must simply agree to certain things, such as not voicing users. This is technically a proposal to create another staff position (albeit one that would not be a prerequisite to any other position such as Admin).
There is one more thing I'd like to point out. On most IRC networks, if someone with the @ prefix before their nick asks you to stop doing something, then generally you know that you must stop it. If they do not possess that prefix, there may incorrectly believe they are free to continue with the bad behavior. Therefore, I recommend the following flags: '''+AOiorv''' You will notice that I left +t out of it, which in combination with the Topic Lock, means such individuals may not change the topic. I did include the +i flag because all that allows someone to do is use ChanServ to invite themselves to the channel in the event the channel has channel mode +i (usually unneeded, but just in case, they can still let themselves in).
That and if ChanServ goes down, which it has and does from time to time, remember that anyone who doesn't have an @ at the time is powerless, creating the opless channel problem.
However, I do understand the concern of too many @'s, so perhaps there may be a way to balance this. Then again, I'm making my recommendation based on the assumption that only a small number of people will be granted this, if this entire thing moves forward.
One more thing. Note that many of us use the ZNC IRC bouncer software, which has the ability to log all activity in the channel, whether you are connected to the bouncer or not. Therefore, there is accountability if it comes to that.
I hope everyone finds my two cents to be useful.
[[User:MrBenC|Ben]] ([[User talk:MrBenC|talk]]) 05:20, January 17, 2013 (UTC)
| |||