[IRCServices] Services Suggestion(s)

[Kevin Conlin]

OK, well

I only have one problem, with IRCservices, after a user identifies, he has to cycle the chan to get ops, now this can cause problems either with revolving door banning bots, or users being annoyed of having to cycel endless channels just to get ops, after identifiction, any way services can op a user on the channel after they identify?

Thanks
  ----- Original Message ----- 
  From: Craig Wood 
  To: ircservices at ircservices.za.net 
  Sent: Monday, April 09, 2001 7:29 AM
  Subject: Re: [IRCServices] Services Suggestion(s)


  a) I cant really see the point in a sendpass, if people lose there pw, they normally approch an oper in person then they can use /getpass or /setpass, i personally in 3years of being an oper have *NEVER* had an e-mail asking for a password. But if you feel the feature is needed, i have no objections ;)
  b) Please give operserv levels! it will make life on my net sooo much easier ;)
  c) I dont feel services need 'cool' names.
  d) cant u get the bot to /vhost on connect?
  e) -
  f) if u want a service in a channel, just /operserv raw :<SERVICE> join <CHANNEL> (Dont forget the services else yer server will seg-fault ;)

  but some of those commands if they existed looked pritty good ;)

  Heres a suggestion from me, an operserv 'auto' command :)
  what it will do it automatically op/half-op/voice a id'd nickname in all the channels it is in. if its de opped/hopd/voiced, that would b useful for opers and bots that r designed to keep the channel open.


    ----- Original Message -----
    From: ViPeR
    Sent: 09 April 2001 02:43
    To: IRCServices at ircservices.za.net
    Subject: [IRCServices] Services Suggestion(s)


    would it be possible to see any of these features in the services at any
    time?

    a) a getpass-like command (sendpass?) that emails the user their password
    (email program probably setup during services configuration/compilation)
    b) a 'operserv level' option in the services.conf for commands like getpass,
    maybe using levels like 1,2,3 for oper, admin, root -- some way that one
    would restrict certain commands (such as not allowing service opers to
    retrieve plain passwords.)
    c) the ability to create additional names for the same bot, while keeping
    the *serv's for compatibility. (i was thinking along the lines of just
    having cooler-sounding names for bots when in channels)
    d) a services command to create bot aliases (like /operserv alias add
    chanserv TheBouncer ident name email host at mask) that also updates existing
    aliases. This command could include the ability to create the user with all
    forms of identification visible to the user, such as nick, ident, name,
    email, and hostmask.
    e) a services command to remove bot aliases (like /operserv alias del
    TheBouncer)
    f) an additional option with chanserv 'set join' to pick the name of a
    chanserv alias to join.
    g) a services command to force an alias to join a channel (i know this can
    be done with raws, but a command would be nicer)

    Well, that turned out longer than I expect. Any comments or suggestions are
    appreciated.

    -ViPeRzPiT
    viper at wcalliance.com


    -----------------------------------------------------------
    To unsubscribe, mail ircservices-request at ircservices.za.net
    with the word UNSUBSCRIBE in the subject of the mail.
    http://www.ircservices.za.net/mailman/listinfo/ircservices




------------------------------------------------------------------------------
  Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: ../attachments/20010409/5f17e99e/attachment.htm