Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a FTEMPLATE for opers to modify templates of a channel #37

Closed
blitmap opened this issue Aug 7, 2012 · 5 comments
Closed

Add a FTEMPLATE for opers to modify templates of a channel #37

blitmap opened this issue Aug 7, 2012 · 5 comments

Comments

@blitmap
Copy link

blitmap commented Aug 7, 2012

Currently I can't modify the templates of a channel as oper without taking over the channel, is there some other way? :>

If not, it would be nice to have this... /msg ChanServ ftemplate #some_channel some_template_name +some_modes...

Also the (fantasy?) form: !ftemplate some_template_name +some_modes...

Please and thank you :>

@alyx
Copy link
Member

alyx commented Aug 9, 2012

What is the point in this?

@mattwb65
Copy link

mattwb65 commented Aug 9, 2012

alyx++. I see no point in this, there aren't legitimate cases when an oper would need this.

@alyx
Copy link
Member

alyx commented Aug 9, 2012

Agreed. The situations I can see where this could be used are:

  • An operator wishes to control a channel without blatantly showing that they control the channel (Which isn't something that should happen, period).
  • An operator wishes to show off "Look at all the cool things I can do!!" (Once again, just shouldn't happen)
  • A channel owner is moderately dim-witted, and instead of the administrator going "Hey, you could just /msg ChanServ HELP TEMPLATE" or "Hey, you could just do /msg ChanServ TEMPLATE #channel +whatevertemplatesyntaxis", the administrator just decides "HERE I'LL POWER YOUR CHANNEL FOR YOU!" (This, once again, isn't something that should happen. Although this is slightly less malicious, there's still no good reason for it. TEMPLATE is just something to add syntactical sugar to FLAGS, so there's no legit need for it, and thus no legit reason an administrator should need to forcibly apply it)

@alyx
Copy link
Member

alyx commented Aug 9, 2012

Lastly, if this is wanted, it should go in modules/contrib.

@alyx alyx closed this as completed Aug 9, 2012
@blitmap
Copy link
Author

blitmap commented Aug 13, 2012

Didn't notice activity on this in time, whoops...

Anyway, I had a situation in a channel where I was close friends with the operating staff there but the actual channel owner is somewhat busy... all the time. Anyway, I wanted to add a new template for describing a certain class of user where they would only have voice and autovoice (vV) but not have A, because for some reason the VOP template on our network allows VOPs to see the access list.

I wanted to: !ftemplate grunt -*+vV

..and then add the user accordingly.

Mostly I've come to the conclusion (after talking with spb) that fcommands don't make sense, if it were up to me fflags would be removed and OperServ's override would be encouraged (along with showing up in OperServ's help text) after being renamed to "impersonate" or "personify". ANYWAY

Thanks for not adding this. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants