]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/001268.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 001268.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] Teams: Idea
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Teams%3A%20Idea&In-Reply-To=">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="001254.html">
11 <LINK REL="Next" HREF="001269.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] Teams: Idea</H1>
15 <B>Jim Stratus</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Teams%3A%20Idea&In-Reply-To="
17 TITLE="[IRCServices Coding] Teams: Idea">stratus at swcempire.com
18 </A><BR>
19 <I>Sat Aug 17 19:12:35 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001254.html">[IRCServices Coding] Services 5.0pre9 released
22 </A></li>
23 <LI>Next message: <A HREF="001269.html">[IRCServices Coding] Teams: Idea
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1268">[ date ]</a>
27 <a href="thread.html#1268">[ thread ]</a>
28 <a href="subject.html#1268">[ subject ]</a>
29 <a href="author.html#1268">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Hello,
35
36 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.
37
38 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.
39
40 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.
41
42 -OperServ- OperServ allows MyIRC Operators to control and
43 -
44 -OperServ- maintain the IRC network.
45 -
46 -OperServ-
47 -
48 -OperServ- OperServ's commands are categorized into Team Levels, to use
49 -
50 -OperServ- them, /msg OperServ &lt;command&gt;.
51 -
52 -OperServ-
53 -
54 -OperServ- Commands available to All Users:
55 -
56 -OperServ- FIND Locate an IRC Operator for assistance
57 -
58 -OperServ-
59 -
60 -OperServ- Commands available to All IRC Operators:
61 -
62 -OperServ- INFO Display advanced info on a nick/channel
63 -
64 -OperServ- NEWS Add new network news
65 -
66 -OperServ- NOTICE Send a global network notice
67 -
68 -OperServ- SEARCH Perform a search on services logs
69 -
70 -OperServ- DIRECTORY List all teams and their ID numbers
71 -
72 -OperServ- LIST List a team, or what teams an oper is on
73 -
74 -OperServ-
75 -
76 -OperServ- Commands available to K:line Team Members:
77 -
78 -OperServ- AKILL Maintain Network Wide Auto-Kills
79 -
80 -OperServ- AUTOKILL Different from Akill, kills people on identify
81 -
82 -OperServ- GECOS Maintain bans set on Real Names
83 -
84 -OperServ- TRIGGER Maintain Clone Detection
85 -
86 -OperServ- ZLINE Maintain Network Wide IP Bans
87 -
88 -OperServ- AUTH Forcefully authorize a nickname
89 -
90 -OperServ- DELMAIL Ask user to re-authorize their nickname
91 -
92 -OperServ- FORBID Forbid a nickname from being used
93 -
94 -OperServ- HOLD Stop a nickname from expiring ever
95 -
96 -OperServ- LOCK Prevent oper intervention on a nickname
97 -
98 -OperServ- QLINE Prevent a nick from being used by
99 non-opers
100 -
101 -OperServ- SENDPASS Generate and email a new password to a user
102 -
103 -OperServ-
104 -
105 -OperServ- Commands available to Closers Team Members:
106 -
107 -OperServ- ACCESS Check and remove channel access entries
108 -
109 -OperServ- CLEAR Clear a channel of bans, modes, or users
110 -
111 -OperServ- CLOSE Close a channel down until it expires
112 -
113 -OperServ- FORBID Prevent a channel from being used
114 -
115 -OperServ- FREEZE Stop ChanServ from interacting with a
116 channel
117 -
118 -OperServ- HOLD Stop a channel from expiring ever
119 -
120 -OperServ- LOCK Prevent oper intervention on a channel
121 -
122 -OperServ- QLINE Prevent a channel being entered by non-opers
123 -
124 -OperServ- SETFOUNDER Change the foundership of a channel
125 -
126 -OperServ- SETTEAM Change the team level allowed in a channel
127 -
128 -OperServ- SUSPEND Suspend a channel for a period of time
129 -
130 -OperServ- WIPE Wipe channel access lists
131 -
132 -OperServ-
133 -
134 -OperServ- Commands available to Abuse Team Members:
135 -
136 -OperServ- DENY Deny a user/oper from services access
137 -
138 -OperServ- IGNORE Maintain Services Ignore lists
139 -
140 -OperServ- NOOPER Suspend the privledges of an Oper
141 -
142 -OperServ-
143 -
144 -OperServ- Commands available to Routing Team Members:
145 -
146 -OperServ- ADMIN Maintain Server Administrators list
147 -
148 -OperServ- DNS Add/Remove server from Dynamic DNS list
149 -
150 -OperServ- JUPE Prevent a server from linking
151 -
152 -OperServ-
153 -
154 -OperServ- Commands available to Services Root Administrators:
155 -
156 -OperServ- DELETE Remove registeration of a nick/channel
157 -
158 -OperServ- GLOBAL Send a memo to every registered nick
159 --
160 -OperServ- LEADER Set the team leader of a team
161 -
162 -OperServ- CHGNICK Force a users nick to be changed
163 -
164 -OperServ-
165 -
166 -OperServ- Commands available to Coding Team Members:
167 -
168 -OperServ- ADD Add a user to a team
169 -
170 -OperServ- DEL Remove a user from a team
171 -
172 -OperServ- DUMP Dump structs to /tmp/dump.txt
173 -
174 -OperServ- MEMUSAGE Display services memory usage
175 -
176 -OperServ- PROCLIST List SQL Processes
177 --
178 -OperServ- QUERY Perform a direct database query
179 -
180 -OperServ- RAW Send a RAW message to services uplink
181 -
182 -OperServ- SVSHOST Change the hostname of a user
183 -
184 -OperServ- SVSKILL Remove a user from the network
185 -
186 -OperServ- SVSMODE Change any user mode
187 -
188 -OperServ- SVSNICK Change any user nick
189 -
190 -OperServ-
191 -
192 -OperServ- Commands sent to OperServ are logged!
193 -
194 -OperServ-
195 -
196
197 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.
198
199 Jim Stratus
200 irc.swcic.net
201 -------------- next part --------------
202 An HTML attachment was scrubbed...
203 URL: <A HREF="../attachments/20020817/f1378cea/attachment.html">../attachments/20020817/f1378cea/attachment.html</A>
204 </PRE>
205
206 <!--endarticle-->
207 <HR>
208 <P><UL>
209 <!--threads-->
210 <LI>Previous message: <A HREF="001254.html">[IRCServices Coding] Services 5.0pre9 released
211 </A></li>
212 <LI>Next message: <A HREF="001269.html">[IRCServices Coding] Teams: Idea
213 </A></li>
214 <LI> <B>Messages sorted by:</B>
215 <a href="date.html#1268">[ date ]</a>
216 <a href="thread.html#1268">[ thread ]</a>
217 <a href="subject.html#1268">[ subject ]</a>
218 <a href="author.html#1268">[ author ]</a>
219 </LI>
220 </UL>
221
222 </body></html>