[srvx-devel] srvx 1.2 TODO tasks

[Entrope <en...@ga...>]

Here is the TODO list of things that I think we really should have in
srvx-1.2, from easy to hard:

  [BUG] ?modlog missing helpfile entry
  [BUG] "!help note types" doesn't show privileged note types to privileged users
  [FEATREQ] OpServ command to add/change an oper's access level
  [FEATREQ] Make the bad-word excepted channels global, not per-bad-word.
  [FEATREQ] ?csearch channel search command
  [FEATREQ] "Persistent auth" (servicestamp/ACCOUNT) support
  [FEATREQ] Cross-bot aliasing/command binding
  [FEATREQ] ServerSpy.net support

(The ServerSpy.net support code may or may not be put into the public
CVS branch.  I need to talk with the site's owner to figure that out.
It should probably be done after the cross-bot command binding,
anyway, to make it more modular.)

The following things are possibilities to add, depending on how hard they are:

  [FEATREQ] MemoServ (perhaps using a SQL backend?)
  [FEATREQ] make "/msg ChanServ access" show your infolines for all channels
  [FEATREQ] /msg AuthServ ghost my-old-nick
    - KILLs my-old-nick (but only if they are authed to your account)
  [FEATREQ] !set greet {0,1,2,3} where 0 is no greeting, 1 is only on userlist, 2 is all users except on userlist, 3 is all users
    - can probably fix or re-use !set greet/!set greetusers to do this
  [FEATREQ] Keep channel suspension history until unreg, so staff can see it
  [FEATREQ] Confirmation Of Channel Registration - Example Below
    <ChanServ> #Rowdy is now registered to account Rowdy
    <ChanServ> Please note, If you do not actively use this channel for 14 days, it will be
      unregistered.  Also note: This message can be customized in srvx.conf.
    <ChanServ> To acknowledge you understand and accept these things, and complete your registration, type "/msg ChanServ CONFIRM #Rowdy".  If you do NOT accept these things, type "/msg ChanServ REJECT #Rowdy".  If you do nothing, this registration will be cancelled in 10 minutes.
    - basically to make sure people know the AUP and channel guidelines in advance

If anybody wants to volunteer to do one of these, or has questions or
feedback or more things they'd like to see (in srvx 1.2 or 2.0),
please find one of the developers in #srvx on GamesNET.

Another option that I really want is a user mode or a account flag
that indicates willingness to receive (or desire to not receive)
oper-sent advertisements.  A lot of people would want to know about
big events, but some vocal people would not, and it does no good to
annoy them.  This may be best as a protocol-level command
(irc_advertise(), with the same signature as irc_privmsg()) that
either invokes the "smart" ircd-known command or iterates over all
users and sends to those who opted in or who did not opt out.

Hm...  I am not sure whether it is "better" on the whole to make such
advertisements opt-in or opt-out.  Any opinions?  (Anyone can answer,
even if they've never looked at the srvx code: the policy aspect is
much more important than the technical feasibility.)

-- Entrope