]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] Services Suggestion(s) | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20Suggestion%28s%29&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="001736.html"> | |
11 | <LINK REL="Next" HREF="001738.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] Services Suggestion(s)</H1> | |
15 | <B>Kevin Conlin</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20Suggestion%28s%29&In-Reply-To=" | |
17 | TITLE="[IRCServices] Services Suggestion(s)">kevc978 at btinternet.com | |
18 | </A><BR> | |
19 | <I>Mon Apr 9 03:51:02 PDT 2001</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001736.html">[IRCServices] Services Suggestion(s) | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001738.html">[IRCServices] Services Suggestion(s) | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1737">[ date ]</a> | |
27 | <a href="thread.html#1737">[ thread ]</a> | |
28 | <a href="subject.html#1737">[ subject ]</a> | |
29 | <a href="author.html#1737">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>Please Read the README | |
35 | ||
36 | The coders will never code in anything to do with chanserv or any other bot | |
37 | for that matter, joining channels, no, not even to look after it. | |
38 | ||
39 | Also, as for aliases, i think it would be nice for messages sent to X, and | |
40 | then relayed o chanserv, to help users that came from Undernet, or RelicNet | |
41 | with different services bot names. | |
42 | ||
43 | Operators should be responsible enough, to know not to use getpass or | |
44 | anything even remotely like that, without needing to, if your opers arent | |
45 | that responible, i recommend new ones ;-) (SendPass sounds a good idea | |
46 | though) | |
47 | ||
48 | ||
49 | Kevin | |
50 | ----- Original Message ----- | |
51 | From: ViPeR <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">viper at wcalliance.com</A>> | |
52 | To: <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">IRCServices at ircservices.za.net</A>> | |
53 | Sent: Monday, April 09, 2001 2:38 AM | |
54 | Subject: [IRCServices] Services Suggestion(s) | |
55 | ||
56 | ||
57 | ><i> would it be possible to see any of these features in the services at any | |
58 | </I>><i> time? | |
59 | </I>><i> | |
60 | </I>><i> a) a getpass-like command (sendpass?) that emails the user their password | |
61 | </I>><i> (email program probably setup during services configuration/compilation) | |
62 | </I>><i> b) a 'operserv level' option in the services.conf for commands like | |
63 | </I>getpass, | |
64 | ><i> maybe using levels like 1,2,3 for oper, admin, root -- some way that one | |
65 | </I>><i> would restrict certain commands (such as not allowing service opers to | |
66 | </I>><i> retrieve plain passwords.) | |
67 | </I>><i> c) the ability to create additional names for the same bot, while keeping | |
68 | </I>><i> the *serv's for compatibility. (i was thinking along the lines of just | |
69 | </I>><i> having cooler-sounding names for bots when in channels) | |
70 | </I>><i> d) a services command to create bot aliases (like /operserv alias add | |
71 | </I>><i> chanserv TheBouncer ident name email <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">host at mask</A>) that also updates existing | |
72 | </I>><i> aliases. This command could include the ability to create the user with | |
73 | </I>all | |
74 | ><i> forms of identification visible to the user, such as nick, ident, name, | |
75 | </I>><i> email, and hostmask. | |
76 | </I>><i> e) a services command to remove bot aliases (like /operserv alias del | |
77 | </I>><i> TheBouncer) | |
78 | </I>><i> f) an additional option with chanserv 'set join' to pick the name of a | |
79 | </I>><i> chanserv alias to join. | |
80 | </I>><i> g) a services command to force an alias to join a channel (i know this can | |
81 | </I>><i> be done with raws, but a command would be nicer) | |
82 | </I>><i> | |
83 | </I>><i> Well, that turned out longer than I expect. Any comments or suggestions | |
84 | </I>are | |
85 | ><i> appreciated. | |
86 | </I>><i> | |
87 | </I>><i> -ViPeRzPiT | |
88 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">viper at wcalliance.com</A> | |
89 | </I>><i> | |
90 | </I>><i> | |
91 | </I>><i> ----------------------------------------------------------- | |
92 | </I>><i> To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A> | |
93 | </I>><i> with the word UNSUBSCRIBE in the subject of the mail. | |
94 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
95 | </I>><i> | |
96 | </I> | |
97 | ||
98 | ||
99 | </PRE> | |
100 | ||
101 | <!--endarticle--> | |
102 | <HR> | |
103 | <P><UL> | |
104 | <!--threads--> | |
105 | <LI>Previous message: <A HREF="001736.html">[IRCServices] Services Suggestion(s) | |
106 | </A></li> | |
107 | <LI>Next message: <A HREF="001738.html">[IRCServices] Services Suggestion(s) | |
108 | </A></li> | |
109 | <LI> <B>Messages sorted by:</B> | |
110 | <a href="date.html#1737">[ date ]</a> | |
111 | <a href="thread.html#1737">[ thread ]</a> | |
112 | <a href="subject.html#1737">[ subject ]</a> | |
113 | <a href="author.html#1737">[ author ]</a> | |
114 | </LI> | |
115 | </UL> | |
116 | ||
117 | </body></html> |