1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] Question on usage of ChanServ ACCESS LIST
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Question%20on%20usage%20of%20ChanServ%20ACCESS%20LIST&In-Reply-To=4137f96b.61105%40achurch.org">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"004621.html">
11 <LINK REL=
"Next" HREF=
"004623.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] Question on usage of ChanServ ACCESS LIST
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Question%20on%20usage%20of%20ChanServ%20ACCESS%20LIST&In-Reply-To=4137f96b.61105%40achurch.org"
17 TITLE=
"[IRCServices] Question on usage of ChanServ ACCESS LIST">phan70m at gmail.com
19 <I>Fri Sep
3 01:
40:
08 PDT
2004</I>
21 <LI>Previous message:
<A HREF=
"004621.html">[IRCServices] Question on usage of ChanServ ACCESS LIST
23 <LI>Next message:
<A HREF=
"004623.html">[IRCServices] Question on usage of ChanServ ACCESS LIST
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#4620">[ date ]
</a>
27 <a href=
"thread.html#4620">[ thread ]
</a>
28 <a href=
"subject.html#4620">[ subject ]
</a>
29 <a href=
"author.html#4620">[ author ]
</a>
34 <PRE>On my network users who seek information from AKICK list will usually
35 request the full list or some kind of wildcard, almost none use
36 numbers for this command.
37 The access list command is commonly accessed by numbers but is access
39 The os_akill command usually being accesses by wildcards to find
40 something specific but if an admin wants to view all results he may
41 use numbers to see next range, this may be replaced by some
"next
"
43 The nickserv/chanserv list commands i think should be used the same
44 way (wildcards + first/prev/next/last commands), numbers in this case
45 may help not loose track when jumping between many pages and may also
46 help if new features will be developed (like dropnick with nick number
47 instead of the nickname, although this may be dangerous).
48 same goes for listemail.
50 I think since I use numbers mostly for navigation an alternative
51 method would eliminate the need for numbers.
56 On Fri,
03 Sep
2004 13:
26:
19 JST, Andrew Church
<<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A>> wrote:
57 ><i> I'm currently working on unifying the usage formats of the various
58 </I>><i> LIST-type commands available in Services (LIST, ACCESS LIST, AKILL LIST,
59 </I>><i> etc.), and I'd like to get some information about how the commands,
60 </I>><i> ChanServ's ACCESS (and AKICK) LIST in particular, are currently being used.
62 </I>><i> In Services
5.0, there are three different styles of LIST command:
64 </I>><i> - NickServ ACCESS LIST:
65 </I>><i> LIST (no parameters, unlimited)
66 </I>><i> - NickServ LIST/LISTEMAIL, ChanServ LIST, OperServ AKILL/EXCLUDE/SxLINE LIST:
67 </I>><i> LIST
<wildcard-mask
> (limited to NSListMax, CSListMax, or
50 entries)
68 </I>><i> - ChanServ ACCESS/AKICK LIST, OperServ EXCEPTION LIST:
69 </I>><i> LIST {
<wildcard-mask
> |
<number-list
>}
71 </I>><i> I won't go into detail since discussion of development versions is
72 </I>><i> off-topic for this list, but I'm working on merging all of these into a
73 </I>><i> common format. The major issue is how to handle numbered and numberless
74 </I>><i> lists; the easiest thing to do is simply to drop support for using a number
75 </I>><i> list with the LIST command, but I don't want to do that if it's a
76 </I>><i> frequently-used feature. So:
78 </I>><i> (
1) How do you (or your users, if you're an admin and aware of usage
79 </I>><i> patterns) usually use the ChanServ ACCESS LIST and AKICK LIST commands:
80 </I>><i> just plain LIST, LIST with a wildcard, or LIST with a list/range of
83 </I>><i> (
2) Would you object to having the ability to use numbers with the
84 </I>><i> LIST command removed? (The numbers would still be usable with DEL.)
86 </I>><i> As a side note, the issue of whether to add numbers to lists that
87 </I>><i> don't currently have them--nickname access lists, autokill lists, and so
88 </I>><i> on--has been brought up before. I haven't decided yet whether to do that,
89 </I>><i> but it's a separate issue from this one, so please don't discuss it in
90 </I>><i> this thread.
92 </I>><i> --Andrew Church
93 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A>
94 </I>><i> <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
96 </I>><i> ------------------------------------------------------------------
97 </I>><i> To unsubscribe or change your subscription options, visit:
98 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
108 <LI>Previous message:
<A HREF=
"004621.html">[IRCServices] Question on usage of ChanServ ACCESS LIST
110 <LI>Next message:
<A HREF=
"004623.html">[IRCServices] Question on usage of ChanServ ACCESS LIST
112 <LI> <B>Messages sorted by:
</B>
113 <a href=
"date.html#4620">[ date ]
</a>
114 <a href=
"thread.html#4620">[ thread ]
</a>
115 <a href=
"subject.html#4620">[ subject ]
</a>
116 <a href=
"author.html#4620">[ author ]
</a>
projects / irc.git / blob