projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices Coding] RE: IRCServices-Coding Digest, Vol 33, Issue 1 | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20RE%3A%20IRCServices-Coding%20Digest%2C%20Vol%2033%2C%20Issue%201&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="003299.html"> | |
| 11 | <LINK REL="Next" HREF="003293.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] RE: IRCServices-Coding Digest, Vol 33, Issue 1</H1> | |
| 15 | <B>Nick Bent</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20RE%3A%20IRCServices-Coding%20Digest%2C%20Vol%2033%2C%20Issue%201&In-Reply-To=" | |
| 17 | TITLE="[IRCServices Coding] RE: IRCServices-Coding Digest, Vol 33, Issue 1">bender_54 at msn.com | |
| 18 | </A><BR> | |
| 19 | <I>Thu May 17 01:07:12 PDT 2007</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="003299.html">[IRCServices Coding] md5 licensing | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="003293.html">[IRCServices Coding] RE: IRCServices-Coding Digest, Vol 33, | |
| 24 | Issue 1 | |
| 25 | </A></li> | |
| 26 | <LI> <B>Messages sorted by:</B> | |
| 27 | <a href="date.html#3292">[ date ]</a> | |
| 28 | <a href="thread.html#3292">[ thread ]</a> | |
| 29 | <a href="subject.html#3292">[ subject ]</a> | |
| 30 | <a href="author.html#3292">[ author ]</a> | |
| 31 | </LI> | |
| 32 | </UL> | |
| 33 | <HR> | |
| 34 | <!--beginarticle--> | |
| 35 | <PRE>Skipped content of type multipart/alternative-------------- next part -------------- | |
| 36 | ><i> Message: 6 | |
| 37 | </I>><i> Date: Tue, 17 Apr 2007 15:53:22 JST | |
| 38 | </I>><i> From: <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A> (Andrew Church) | |
| 39 | </I>><i> Subject: Re: [IRCServices Coding] Feature Suggestions | |
| 40 | </I>><i> To: <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A> | |
| 41 | </I>><i> Message-ID: <<A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">4624733c.06344 at msgid.achurch.org</A>> | |
| 42 | </I>><i> Content-Type: text/plain; charset=ISO-2022-JP | |
| 43 | </I>><i> | |
| 44 | </I>><i> To the original poster: Don't use HTML mail on this list. | |
| 45 | </I>><i> | |
| 46 | </I>><i> >> 1. /ns set autoop [on|off] - Just like Anope | |
| 47 | </I>><i> > | |
| 48 | </I>><i> >If this is what I think it is, which is that the nick in question | |
| 49 | </I>><i> >won't be auto-opped on any channel (next time please elaborate on what | |
| 50 | </I>><i> >Anope does), I believe that Andrew may have been considering this at | |
| 51 | </I>><i> >one point (I think it was in one of the TODO lists). That being said, | |
| 52 | </I>><i> >I haven't seen this in 5.1, so it may have been dropped or thrown out. | |
| 53 | </I>><i> | |
| 54 | </I>><i> I've never seen the point to this option (if you don't want auto-ops, | |
| 55 | </I>><i> don't have people give you auto-op access), so I won't be adding it. | |
| 56 | </I> | |
| 57 | You can't stop people from giving you access. This is an attitude thing, | |
| 58 | where a user has chosen to only give themselves staus when they need it. | |
| 59 | ||
| 60 | ><i> | |
| 61 | </I>><i> >> 6. When someone does /cs info #channel, and it shows the mode lock, make it | |
| 62 | </I>><i> >> show the locked mode paramaters too. | |
| 63 | </I>><i> > | |
| 64 | </I>><i> >Bad idea. I'm sure that no-one wants to see their channel key | |
| 65 | </I>><i> >displayed in this manner. :) | |
| 66 | </I>><i> | |
| 67 | </I>><i> Exactly. As for other modes, just look at the channel's current mode | |
| 68 | </I>><i> set, which will naturally be the same as what's set in the mode lock. | |
| 69 | </I>><i> | |
| 70 | </I>><i> --Andrew Church | |
| 71 | </I> | |
| 72 | Perhaps show parameters for all modes but k? Using one command instead of two to | |
| 73 | see the full mode lock would be nice. | |
| 74 | ||
| 75 | Nick | |
| 76 | </PRE> | |
| 77 | ||
| 78 | ||
| 79 | ||
| 80 | ||
| 81 | ||
| 82 | ||
| 83 | ||
| 84 | <!--endarticle--> | |
| 85 | <HR> | |
| 86 | <P><UL> | |
| 87 | <!--threads--> | |
| 88 | <LI>Previous message: <A HREF="003299.html">[IRCServices Coding] md5 licensing | |
| 89 | </A></li> | |
| 90 | <LI>Next message: <A HREF="003293.html">[IRCServices Coding] RE: IRCServices-Coding Digest, Vol 33, | |
| 91 | Issue 1 | |
| 92 | </A></li> | |
| 93 | <LI> <B>Messages sorted by:</B> | |
| 94 | <a href="date.html#3292">[ date ]</a> | |
| 95 | <a href="thread.html#3292">[ thread ]</a> | |
| 96 | <a href="subject.html#3292">[ subject ]</a> | |
| 97 | <a href="author.html#3292">[ author ]</a> | |
| 98 | </LI> | |
| 99 | </UL> | |
| 100 | ||
| 101 | </body></html> |