]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/001966.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2003 / 001966.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] Chanserv patch for reg chans only
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Chanserv%20patch%20for%20reg%20chans%20only&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="001965.html">
11 <LINK REL="Next" HREF="001967.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] Chanserv patch for reg chans only</H1>
15 <B>DeadNotBuried</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Chanserv%20patch%20for%20reg%20chans%20only&In-Reply-To="
17 TITLE="[IRCServices Coding] Chanserv patch for reg chans only">idontwantthisshit at hotmail.com
18 </A><BR>
19 <I>Wed Mar 12 19:36:52 PST 2003</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001965.html">[IRCServices Coding] Chanserv patch for reg chans only
22 </A></li>
23 <LI>Next message: <A HREF="001967.html">[IRCServices Coding] Chanserv patch for reg chans only
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1966">[ date ]</a>
27 <a href="thread.html#1966">[ thread ]</a>
28 <a href="subject.html#1966">[ subject ]</a>
29 <a href="author.html#1966">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>&gt;<i> Also, I can think of a pathological case where the +b *!*@* might be a
35 </I>&gt;<i> problem. It would show up if one oper joins an unregistered channel and
36 </I>&gt;<i> idles, then a normal user tries to join and services sets the +b. With
37 </I>&gt;<i> some servers (unreal), this will prevent other opers from joining that
38 </I>&gt;<i> channel, since opers can't break bans and they can't use chanserv to
39 </I>&gt;<i> remove them, since the channel isn't registered.
40 </I>
41 on unreal 3.2 opers can get around the ban by inviting themselves into the
42 channel
43 </PRE>
44
45 <!--endarticle-->
46 <HR>
47 <P><UL>
48 <!--threads-->
49 <LI>Previous message: <A HREF="001965.html">[IRCServices Coding] Chanserv patch for reg chans only
50 </A></li>
51 <LI>Next message: <A HREF="001967.html">[IRCServices Coding] Chanserv patch for reg chans only
52 </A></li>
53 <LI> <B>Messages sorted by:</B>
54 <a href="date.html#1966">[ date ]</a>
55 <a href="thread.html#1966">[ thread ]</a>
56 <a href="subject.html#1966">[ subject ]</a>
57 <a href="author.html#1966">[ author ]</a>
58 </LI>
59 </UL>
60
61 </body></html>