]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/001270.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2002 / 001270.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=004001c2465c%24b868b2c0%24487c0d82%40centerpoint">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="001269.html">
11 <LINK REL="Next" HREF="001271.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] Teams: Idea</H1>
15 <B>Aragon Gouveia</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Teams%3A%20Idea&In-Reply-To=004001c2465c%24b868b2c0%24487c0d82%40centerpoint"
17 TITLE="[IRCServices Coding] Teams: Idea">aragon at phat.za.net
18 </A><BR>
19 <I>Sat Aug 17 20:57:25 PDT 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001269.html">[IRCServices Coding] Teams: Idea
22 </A></li>
23 <LI>Next message: <A HREF="001271.html">[IRCServices Coding] Teams: Idea
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1270">[ date ]</a>
27 <a href="thread.html#1270">[ thread ]</a>
28 <a href="subject.html#1270">[ subject ]</a>
29 <a href="author.html#1270">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Hi,
35
36 A few nice features, but too complex imho.
37
38 ircservices has 3 permission levels - oper, admin, super user. For us this
39 is perfect. We've modified how ircservices deals with each level too. For
40 example, all admins are automatically given channel founder access to any
41 registered channel.
42
43 One feature that stood out below was the ability to ban based on gecos. I'd
44 like to see a feature like this tied together with regex matching (gecos and
45 regular nick!<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ident at host</A> matched together).
46
47 Something to manage GZLINEs would be nifty too (have a feeling I saw this in
48 version 5, can't remember now).
49
50 While I'm ranting about new features, the ability to search the akill db
51 by reason would be handy too. Add to that the ability to list akills grouped
52 by reason would also be cool.
53
54 -OperServ- There are 427 host masks on the AKILL list.
55
56 This is probably small by many standards and even it can be a pain to wade
57 through. :)
58
59
60 Regards,
61 Aragon
62
63
64
65 |<i> By Jim Stratus &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">stratus at swcempire.com</A>&gt;
66 </I>|<i> [ 2002-08-18 04:10 +0200 ]
67 </I>&gt;<i> Hello,
68 </I>&gt;<i>
69 </I>&gt;<i> 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.
70 </I>&gt;<i>
71 </I>&gt;<i> 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.
72 </I>&gt;<i>
73 </I>&gt;<i> 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.
74 </I>&gt;<i>
75 </I>&gt;<i> -OperServ- OperServ allows MyIRC Operators to control and
76 </I>&gt;<i> -
77 </I>&gt;<i> -OperServ- maintain the IRC network.
78 </I>&gt;<i> -
79 </I>&gt;<i> -OperServ-
80 </I>&gt;<i> -
81 </I>&gt;<i> -OperServ- OperServ's commands are categorized into Team Levels, to use
82 </I>&gt;<i> -
83 </I>&gt;<i> -OperServ- them, /msg OperServ &lt;command&gt;.
84 </I>&gt;<i> -
85 </I>&gt;<i> -OperServ-
86 </I>&gt;<i> -
87 </I>&gt;<i> -OperServ- Commands available to All Users:
88 </I>&gt;<i> -
89 </I>&gt;<i> -OperServ- FIND Locate an IRC Operator for assistance
90 </I>&gt;<i> -
91 </I>&gt;<i> -OperServ-
92 </I>&gt;<i> -
93 </I>&gt;<i> -OperServ- Commands available to All IRC Operators:
94 </I>&gt;<i> -
95 </I>&gt;<i> -OperServ- INFO Display advanced info on a nick/channel
96 </I>&gt;<i> -
97 </I>&gt;<i> -OperServ- NEWS Add new network news
98 </I>&gt;<i> -
99 </I>&gt;<i> -OperServ- NOTICE Send a global network notice
100 </I>&gt;<i> -
101 </I>&gt;<i> -OperServ- SEARCH Perform a search on services logs
102 </I>&gt;<i> -
103 </I>&gt;<i> -OperServ- DIRECTORY List all teams and their ID numbers
104 </I>&gt;<i> -
105 </I>&gt;<i> -OperServ- LIST List a team, or what teams an oper is on
106 </I>&gt;<i> -
107 </I>&gt;<i> -OperServ-
108 </I>&gt;<i> -
109 </I>&gt;<i> -OperServ- Commands available to K:line Team Members:
110 </I>&gt;<i> -
111 </I>&gt;<i> -OperServ- AKILL Maintain Network Wide Auto-Kills
112 </I>&gt;<i> -
113 </I>&gt;<i> -OperServ- AUTOKILL Different from Akill, kills people on identify
114 </I>&gt;<i> -
115 </I>&gt;<i> -OperServ- GECOS Maintain bans set on Real Names
116 </I>&gt;<i> -
117 </I>&gt;<i> -OperServ- TRIGGER Maintain Clone Detection
118 </I>&gt;<i> -
119 </I>&gt;<i> -OperServ- ZLINE Maintain Network Wide IP Bans
120 </I>&gt;<i> -
121 </I>&gt;<i> -OperServ- AUTH Forcefully authorize a nickname
122 </I>&gt;<i> -
123 </I>&gt;<i> -OperServ- DELMAIL Ask user to re-authorize their nickname
124 </I>&gt;<i> -
125 </I>&gt;<i> -OperServ- FORBID Forbid a nickname from being used
126 </I>&gt;<i> -
127 </I>&gt;<i> -OperServ- HOLD Stop a nickname from expiring ever
128 </I>&gt;<i> -
129 </I>&gt;<i> -OperServ- LOCK Prevent oper intervention on a nickname
130 </I>&gt;<i> -
131 </I>&gt;<i> -OperServ- QLINE Prevent a nick from being used by
132 </I>&gt;<i> non-opers
133 </I>&gt;<i> -
134 </I>&gt;<i> -OperServ- SENDPASS Generate and email a new password to a user
135 </I>&gt;<i> -
136 </I>&gt;<i> -OperServ-
137 </I>&gt;<i> -
138 </I>&gt;<i> -OperServ- Commands available to Closers Team Members:
139 </I>&gt;<i> -
140 </I>&gt;<i> -OperServ- ACCESS Check and remove channel access entries
141 </I>&gt;<i> -
142 </I>&gt;<i> -OperServ- CLEAR Clear a channel of bans, modes, or users
143 </I>&gt;<i> -
144 </I>&gt;<i> -OperServ- CLOSE Close a channel down until it expires
145 </I>&gt;<i> -
146 </I>&gt;<i> -OperServ- FORBID Prevent a channel from being used
147 </I>&gt;<i> -
148 </I>&gt;<i> -OperServ- FREEZE Stop ChanServ from interacting with a
149 </I>&gt;<i> channel
150 </I>&gt;<i> -
151 </I>&gt;<i> -OperServ- HOLD Stop a channel from expiring ever
152 </I>&gt;<i> -
153 </I>&gt;<i> -OperServ- LOCK Prevent oper intervention on a channel
154 </I>&gt;<i> -
155 </I>&gt;<i> -OperServ- QLINE Prevent a channel being entered by non-opers
156 </I>&gt;<i> -
157 </I>&gt;<i> -OperServ- SETFOUNDER Change the foundership of a channel
158 </I>&gt;<i> -
159 </I>&gt;<i> -OperServ- SETTEAM Change the team level allowed in a channel
160 </I>&gt;<i> -
161 </I>&gt;<i> -OperServ- SUSPEND Suspend a channel for a period of time
162 </I>&gt;<i> -
163 </I>&gt;<i> -OperServ- WIPE Wipe channel access lists
164 </I>&gt;<i> -
165 </I>&gt;<i> -OperServ-
166 </I>&gt;<i> -
167 </I>&gt;<i> -OperServ- Commands available to Abuse Team Members:
168 </I>&gt;<i> -
169 </I>&gt;<i> -OperServ- DENY Deny a user/oper from services access
170 </I>&gt;<i> -
171 </I>&gt;<i> -OperServ- IGNORE Maintain Services Ignore lists
172 </I>&gt;<i> -
173 </I>&gt;<i> -OperServ- NOOPER Suspend the privledges of an Oper
174 </I>&gt;<i> -
175 </I>&gt;<i> -OperServ-
176 </I>&gt;<i> -
177 </I>&gt;<i> -OperServ- Commands available to Routing Team Members:
178 </I>&gt;<i> -
179 </I>&gt;<i> -OperServ- ADMIN Maintain Server Administrators list
180 </I>&gt;<i> -
181 </I>&gt;<i> -OperServ- DNS Add/Remove server from Dynamic DNS list
182 </I>&gt;<i> -
183 </I>&gt;<i> -OperServ- JUPE Prevent a server from linking
184 </I>&gt;<i> -
185 </I>&gt;<i> -OperServ-
186 </I>&gt;<i> -
187 </I>&gt;<i> -OperServ- Commands available to Services Root Administrators:
188 </I>&gt;<i> -
189 </I>&gt;<i> -OperServ- DELETE Remove registeration of a nick/channel
190 </I>&gt;<i> -
191 </I>&gt;<i> -OperServ- GLOBAL Send a memo to every registered nick
192 </I>&gt;<i> --
193 </I>&gt;<i> -OperServ- LEADER Set the team leader of a team
194 </I>&gt;<i> -
195 </I>&gt;<i> -OperServ- CHGNICK Force a users nick to be changed
196 </I>&gt;<i> -
197 </I>&gt;<i> -OperServ-
198 </I>&gt;<i> -
199 </I>&gt;<i> -OperServ- Commands available to Coding Team Members:
200 </I>&gt;<i> -
201 </I>&gt;<i> -OperServ- ADD Add a user to a team
202 </I>&gt;<i> -
203 </I>&gt;<i> -OperServ- DEL Remove a user from a team
204 </I>&gt;<i> -
205 </I>&gt;<i> -OperServ- DUMP Dump structs to /tmp/dump.txt
206 </I>&gt;<i> -
207 </I>&gt;<i> -OperServ- MEMUSAGE Display services memory usage
208 </I>&gt;<i> -
209 </I>&gt;<i> -OperServ- PROCLIST List SQL Processes
210 </I>&gt;<i> --
211 </I>&gt;<i> -OperServ- QUERY Perform a direct database query
212 </I>&gt;<i> -
213 </I>&gt;<i> -OperServ- RAW Send a RAW message to services uplink
214 </I>&gt;<i> -
215 </I>&gt;<i> -OperServ- SVSHOST Change the hostname of a user
216 </I>&gt;<i> -
217 </I>&gt;<i> -OperServ- SVSKILL Remove a user from the network
218 </I>&gt;<i> -
219 </I>&gt;<i> -OperServ- SVSMODE Change any user mode
220 </I>&gt;<i> -
221 </I>&gt;<i> -OperServ- SVSNICK Change any user nick
222 </I>&gt;<i> -
223 </I>&gt;<i> -OperServ-
224 </I>&gt;<i> -
225 </I>&gt;<i> -OperServ- Commands sent to OperServ are logged!
226 </I>&gt;<i> -
227 </I>&gt;<i> -OperServ-
228 </I>&gt;<i> -
229 </I>&gt;<i>
230 </I>&gt;<i> 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.
231 </I>&gt;<i>
232 </I>&gt;<i> Jim Stratus
233 </I>&gt;<i> irc.swcic.net
234 </I>
235 </PRE>
236
237 <!--endarticle-->
238 <HR>
239 <P><UL>
240 <!--threads-->
241 <LI>Previous message: <A HREF="001269.html">[IRCServices Coding] Teams: Idea
242 </A></li>
243 <LI>Next message: <A HREF="001271.html">[IRCServices Coding] Teams: Idea
244 </A></li>
245 <LI> <B>Messages sorted by:</B>
246 <a href="date.html#1270">[ date ]</a>
247 <a href="thread.html#1270">[ thread ]</a>
248 <a href="subject.html#1270">[ subject ]</a>
249 <a href="author.html#1270">[ author ]</a>
250 </LI>
251 </UL>
252
253 </body></html>