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