+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<HTML>
- <HEAD>
- <TITLE> [IRCServices] [Suggestion for next versions] Topiclock and last channels
- </TITLE>
- <LINK REL="Index" HREF="index.html" >
- <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">
- <META NAME="robots" CONTENT="index,nofollow">
- <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <LINK REL="Previous" HREF="002737.html">
- <LINK REL="Next" HREF="002744.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[IRCServices] [Suggestion for next versions] Topiclock and last channels</H1>
- <B>Jollino</B>
- <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"
- TITLE="[IRCServices] [Suggestion for next versions] Topiclock and last channels">jollino at sogno.net
- </A><BR>
- <I>Sun Feb 3 01:30:01 PST 2002</I>
- <P><UL>
- <LI>Previous message: <A HREF="002737.html">[IRCServices] [Suggestion for next versions] Topiclock and last channels
-</A></li>
- <LI>Next message: <A HREF="002744.html">[IRCServices] [Suggestion for next versions] Topiclock and last channels
-</A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#2739">[ date ]</a>
- <a href="thread.html#2739">[ thread ]</a>
- <a href="subject.html#2739">[ subject ]</a>
- <a href="author.html#2739">[ author ]</a>
- </LI>
- </UL>
- <HR>
-<!--beginarticle-->
-<PRE>Sabato, febbraio 2, 2002, alle 06:23 , Andrew Church ha scritto:
-
->><i> 1) Topiclock. [...]
-</I>><i>
-</I>><i> I like the idea of moving it to a separate command (/cs topic);
-</I>><i> I'll
-</I>><i> consider it for version 5.0.
-</I>My idea was to act like this:
-- foo changes topic on #bar (via plain /topic)
-- chanserv checks whether topiclock is set
-- if topiclock is set to (e.g.) aop, chanserv checks whether foo has
-aop - or higher - access on #foo
-- if foo is >= aop, cs just does nothing; if he's not, cs will reset the
-topic to the last one.
-if the user used /cs topic, instead, cs would just do the check about
-the topiclock level and refuse or accept to change the topic.
-allowing to use the old /topic command would, IMO, be more transparent
-to the end user.
-
->><i> 2) Last channels. [...]
-</I>><i>
-</I>><i> I don't see that this is worth the trouble of adding it (and also
-</I>><i> adding all the other auxiliary stuff like HIDE LASTCHANS), since the
-</I>><i> user
-</I>><i> isn't online and thus you can't talk to them anyway, and if they were
-</I>><i> online you could just use /whois; and in any case you can always send
-</I>><i> memos.
-</I>It would be much like an extended /whowas command, which would return
-the channels the user was, the same way a /whois returns the channels
-the user is :)
-
-
-Regards
- Daniele
---
-Jollino [jollino at sogno dot net - jollino at chieti dot ch]
-IRC Operator on irc.discussioni.org
-Webmaster of <A HREF="http://www.sogno.net">http://www.sogno.net</A> and related services
-Active content provider of <A HREF="http://www.chieti.ch">http://www.chieti.ch</A>
-Italian Dreamer no. 2305 (www.italiandreamers.net)
-Longe vivu la verda stelo de Esperanto!
-Eg atart agapüen...
-
-
-</PRE>
-
-<!--endarticle-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="002737.html">[IRCServices] [Suggestion for next versions] Topiclock and last channels
-</A></li>
- <LI>Next message: <A HREF="002744.html">[IRCServices] [Suggestion for next versions] Topiclock and last channels
-</A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#2739">[ date ]</a>
- <a href="thread.html#2739">[ thread ]</a>
- <a href="subject.html#2739">[ subject ]</a>
- <a href="author.html#2739">[ author ]</a>
- </LI>
- </UL>
-
-</body></html>
projects / irc.git / blobdiff