]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001738.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001738.html
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="001737.html">
11 <LINK REL="Next" HREF="001744.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Services Suggestion(s)</H1>
15 <B>ViPeR</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)">viper at wcalliance.com
18 </A><BR>
19 <I>Mon Apr 9 04:08:01 PDT 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001737.html">[IRCServices] Services Suggestion(s)
22 </A></li>
23 <LI>Next message: <A HREF="001744.html">AW: [IRCServices] Services Suggestion(s)
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1738">[ date ]</a>
27 <a href="thread.html#1738">[ thread ]</a>
28 <a href="subject.html#1738">[ subject ]</a>
29 <a href="author.html#1738">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Just to note, the FIRST suggestion is the only important one, other than
35 that read below:
36
37 The joining channels thing was just something to do with aliases, i read the
38 readme and know they wont join services to channels, but having an alias for
39 chanserv in your channel would be cool (thinking along the lines of 'X' in
40 daylight?)... that was a side issue.
41
42 the restrictions idea was my way of saying 'people arent perfect, and
43 revenge occurs in REMOTE situations.' i LOVE the fact that lower services
44 opers now cannot get an admin/root pass, and i like the 'su' command
45 implementation over one root, but I think that in some cases I would trust
46 some of my people with operserv access if not for 'raw' and the ability to
47 screw up services without meaning to. this is one case where levels could
48 help (seeing root-only raw commands?).
49
50 the MAIN focus of the entire suggestion was the first one, sendpass. I would
51 LOVE to see a sendpass command that takes advantage of the email address in
52 the nick/channel db. If i werent a horrible portable-code-writer I would
53 attempt to write this code, but I cant write portable code for squat and the
54 'temporary implementation' on my system is only for my system and _very_
55 shaky.
56
57 -ViPeRzPiT
58 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">viper at wcalliance.com</A>
59
60 ----- Original Message -----
61 From: &quot;Kevin Conlin&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">kevc978 at btinternet.com</A>&gt;
62 To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>&gt;
63 Sent: Sunday, April 08, 2001 9:47 PM
64 Subject: Re: [IRCServices] Services Suggestion(s)
65
66 &lt;&lt;SNIP&gt;&gt;
67
68
69
70 </PRE>
71
72 <!--endarticle-->
73 <HR>
74 <P><UL>
75 <!--threads-->
76 <LI>Previous message: <A HREF="001737.html">[IRCServices] Services Suggestion(s)
77 </A></li>
78 <LI>Next message: <A HREF="001744.html">AW: [IRCServices] Services Suggestion(s)
79 </A></li>
80 <LI> <B>Messages sorted by:</B>
81 <a href="date.html#1738">[ date ]</a>
82 <a href="thread.html#1738">[ thread ]</a>
83 <a href="subject.html#1738">[ subject ]</a>
84 <a href="author.html#1738">[ author ]</a>
85 </LI>
86 </UL>
87
88 </body></html>