1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] [Suggestion for next versions] Topiclock and last channels
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20%5BSuggestion%20for%20next%20versions%5D%20Topiclock%20and%20last%20channels&In-Reply-To=3c5c2101.10343%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=
"002737.html">
11 <LINK REL=
"Next" HREF=
"002744.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] [Suggestion for next versions] Topiclock and last channels
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20%5BSuggestion%20for%20next%20versions%5D%20Topiclock%20and%20last%20channels&In-Reply-To=3c5c2101.10343%40achurch.org"
17 TITLE=
"[IRCServices] [Suggestion for next versions] Topiclock and last channels">jollino at sogno.net
19 <I>Sun Feb
3 01:
30:
01 PST
2002</I>
21 <LI>Previous message:
<A HREF=
"002737.html">[IRCServices] [Suggestion for next versions] Topiclock and last channels
23 <LI>Next message:
<A HREF=
"002744.html">[IRCServices] [Suggestion for next versions] Topiclock and last channels
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#2739">[ date ]
</a>
27 <a href=
"thread.html#2739">[ thread ]
</a>
28 <a href=
"subject.html#2739">[ subject ]
</a>
29 <a href=
"author.html#2739">[ author ]
</a>
34 <PRE>Sabato, febbraio
2,
2002, alle
06:
23 , Andrew Church ha scritto:
36 >><i> 1) Topiclock. [...]
38 </I>><i> I like the idea of moving it to a separate command (/cs topic);
40 </I>><i> consider it for version
5.0.
41 </I>My idea was to act like this:
42 - foo changes topic on #bar (via plain /topic)
43 - chanserv checks whether topiclock is set
44 - if topiclock is set to (e.g.) aop, chanserv checks whether foo has
45 aop - or higher - access on #foo
46 - if foo is
>= aop, cs just does nothing; if he's not, cs will reset the
47 topic to the last one.
48 if the user used /cs topic, instead, cs would just do the check about
49 the topiclock level and refuse or accept to change the topic.
50 allowing to use the old /topic command would, IMO, be more transparent
53 >><i> 2) Last channels. [...]
55 </I>><i> I don't see that this is worth the trouble of adding it (and also
56 </I>><i> adding all the other auxiliary stuff like HIDE LASTCHANS), since the
58 </I>><i> isn't online and thus you can't talk to them anyway, and if they were
59 </I>><i> online you could just use /whois; and in any case you can always send
61 </I>It would be much like an extended /whowas command, which would return
62 the channels the user was, the same way a /whois returns the channels
69 Jollino [jollino at sogno dot net - jollino at chieti dot ch]
70 IRC Operator on irc.discussioni.org
71 Webmaster of
<A HREF=
"http://www.sogno.net">http://www.sogno.net
</A> and related services
72 Active content provider of
<A HREF=
"http://www.chieti.ch">http://www.chieti.ch
</A>
73 Italian Dreamer no.
2305 (www.italiandreamers.net)
74 Longe vivu la verda stelo de Esperanto!
75 Eg atart agap
üen...
84 <LI>Previous message:
<A HREF=
"002737.html">[IRCServices] [Suggestion for next versions] Topiclock and last channels
86 <LI>Next message:
<A HREF=
"002744.html">[IRCServices] [Suggestion for next versions] Topiclock and last channels
88 <LI> <B>Messages sorted by:
</B>
89 <a href=
"date.html#2739">[ date ]
</a>
90 <a href=
"thread.html#2739">[ thread ]
</a>
91 <a href=
"subject.html#2739">[ subject ]
</a>
92 <a href=
"author.html#2739">[ author ]
</a>