[IRCServices Coding] Teams: Idea
Aragon Gouveia
aragon at phat.za.net
Sat Aug 17 20:57:25 PDT 2002
Hi,
A few nice features, but too complex imho.
ircservices has 3 permission levels - oper, admin, super user. For us this
is perfect. We've modified how ircservices deals with each level too. For
example, all admins are automatically given channel founder access to any
registered channel.
One feature that stood out below was the ability to ban based on gecos. I'd
like to see a feature like this tied together with regex matching (gecos and
regular nick!ident at host matched together).
Something to manage GZLINEs would be nifty too (have a feeling I saw this in
version 5, can't remember now).
While I'm ranting about new features, the ability to search the akill db
by reason would be handy too. Add to that the ability to list akills grouped
by reason would also be cool.
-OperServ- There are 427 host masks on the AKILL list.
This is probably small by many standards and even it can be a pain to wade
through. :)
Regards,
Aragon
| By Jim Stratus <stratus at swcempire.com>
| [ 2002-08-18 04:10 +0200 ]
> Hello,
>
> Here is an idea for you that was going to be used on a version of Services called VorteX, but they lost their financial support so stopped programming it, so we are stuck with the bits and pieces, but the operserv help thing works, and this is an example of what it looks like.
>
> You see, they used teams for access instead of levels like Services Op and Services Admin. Other services I liked had Help Op, Services Op, Services Admin and Services Root Admin and one Services Master.
>
> This version I like, however, uses teams: Help Team, IRC Operators, K-Line Team, Closers Team, Coding Team, and Executive Board. (Coding Team had access to all teams automatically), and users can be assigned more than one team, and each team has a leader.
>
> -OperServ- OperServ allows MyIRC Operators to control and
> -
> -OperServ- maintain the IRC network.
> -
> -OperServ-
> -
> -OperServ- OperServ's commands are categorized into Team Levels, to use
> -
> -OperServ- them, /msg OperServ <command>.
> -
> -OperServ-
> -
> -OperServ- Commands available to All Users:
> -
> -OperServ- FIND Locate an IRC Operator for assistance
> -
> -OperServ-
> -
> -OperServ- Commands available to All IRC Operators:
> -
> -OperServ- INFO Display advanced info on a nick/channel
> -
> -OperServ- NEWS Add new network news
> -
> -OperServ- NOTICE Send a global network notice
> -
> -OperServ- SEARCH Perform a search on services logs
> -
> -OperServ- DIRECTORY List all teams and their ID numbers
> -
> -OperServ- LIST List a team, or what teams an oper is on
> -
> -OperServ-
> -
> -OperServ- Commands available to K:line Team Members:
> -
> -OperServ- AKILL Maintain Network Wide Auto-Kills
> -
> -OperServ- AUTOKILL Different from Akill, kills people on identify
> -
> -OperServ- GECOS Maintain bans set on Real Names
> -
> -OperServ- TRIGGER Maintain Clone Detection
> -
> -OperServ- ZLINE Maintain Network Wide IP Bans
> -
> -OperServ- AUTH Forcefully authorize a nickname
> -
> -OperServ- DELMAIL Ask user to re-authorize their nickname
> -
> -OperServ- FORBID Forbid a nickname from being used
> -
> -OperServ- HOLD Stop a nickname from expiring ever
> -
> -OperServ- LOCK Prevent oper intervention on a nickname
> -
> -OperServ- QLINE Prevent a nick from being used by
> non-opers
> -
> -OperServ- SENDPASS Generate and email a new password to a user
> -
> -OperServ-
> -
> -OperServ- Commands available to Closers Team Members:
> -
> -OperServ- ACCESS Check and remove channel access entries
> -
> -OperServ- CLEAR Clear a channel of bans, modes, or users
> -
> -OperServ- CLOSE Close a channel down until it expires
> -
> -OperServ- FORBID Prevent a channel from being used
> -
> -OperServ- FREEZE Stop ChanServ from interacting with a
> channel
> -
> -OperServ- HOLD Stop a channel from expiring ever
> -
> -OperServ- LOCK Prevent oper intervention on a channel
> -
> -OperServ- QLINE Prevent a channel being entered by non-opers
> -
> -OperServ- SETFOUNDER Change the foundership of a channel
> -
> -OperServ- SETTEAM Change the team level allowed in a channel
> -
> -OperServ- SUSPEND Suspend a channel for a period of time
> -
> -OperServ- WIPE Wipe channel access lists
> -
> -OperServ-
> -
> -OperServ- Commands available to Abuse Team Members:
> -
> -OperServ- DENY Deny a user/oper from services access
> -
> -OperServ- IGNORE Maintain Services Ignore lists
> -
> -OperServ- NOOPER Suspend the privledges of an Oper
> -
> -OperServ-
> -
> -OperServ- Commands available to Routing Team Members:
> -
> -OperServ- ADMIN Maintain Server Administrators list
> -
> -OperServ- DNS Add/Remove server from Dynamic DNS list
> -
> -OperServ- JUPE Prevent a server from linking
> -
> -OperServ-
> -
> -OperServ- Commands available to Services Root Administrators:
> -
> -OperServ- DELETE Remove registeration of a nick/channel
> -
> -OperServ- GLOBAL Send a memo to every registered nick
> --
> -OperServ- LEADER Set the team leader of a team
> -
> -OperServ- CHGNICK Force a users nick to be changed
> -
> -OperServ-
> -
> -OperServ- Commands available to Coding Team Members:
> -
> -OperServ- ADD Add a user to a team
> -
> -OperServ- DEL Remove a user from a team
> -
> -OperServ- DUMP Dump structs to /tmp/dump.txt
> -
> -OperServ- MEMUSAGE Display services memory usage
> -
> -OperServ- PROCLIST List SQL Processes
> --
> -OperServ- QUERY Perform a direct database query
> -
> -OperServ- RAW Send a RAW message to services uplink
> -
> -OperServ- SVSHOST Change the hostname of a user
> -
> -OperServ- SVSKILL Remove a user from the network
> -
> -OperServ- SVSMODE Change any user mode
> -
> -OperServ- SVSNICK Change any user nick
> -
> -OperServ-
> -
> -OperServ- Commands sent to OperServ are logged!
> -
> -OperServ-
> -
>
> What do you think? They used SQL-services, which I like, since you can have a web-interface for it too, which they did, for users to manage their stuff, but they lost all their data on that apparently.
>
> Jim Stratus
> irc.swcic.net