]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices] Re: NS AJOIN and CS SET RESTRICTED | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Re%3A%20NS%20AJOIN%20and%20CS%20SET%20RESTRICTED&In-Reply-To=b19eae4e0701061053s6fe64a36k74a7f3d546271b50%40mail.gmail.com"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="005206.html"> | |
11 | <LINK REL="Next" HREF="005204.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] Re: NS AJOIN and CS SET RESTRICTED</H1> | |
15 | <B>Andrew Church</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Re%3A%20NS%20AJOIN%20and%20CS%20SET%20RESTRICTED&In-Reply-To=b19eae4e0701061053s6fe64a36k74a7f3d546271b50%40mail.gmail.com" | |
17 | TITLE="[IRCServices] Re: NS AJOIN and CS SET RESTRICTED">achurch at achurch.org | |
18 | </A><BR> | |
19 | <I>Sun Jan 7 06:35:00 PST 2007</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="005206.html">[IRCServices] Re: NS AJOIN and CS SET RESTRICTED | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="005204.html">[IRCServices] NS AJOIN and CS SET RESTRICTED | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#5207">[ date ]</a> | |
27 | <a href="thread.html#5207">[ thread ]</a> | |
28 | <a href="subject.html#5207">[ subject ]</a> | |
29 | <a href="author.html#5207">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>><i>Is there any point allowing AJOIN to a restricted channel if you're | |
35 | </I>><i>not on the access list though? That seems like it could be used to | |
36 | </I>><i>create joinfloods of a sort. | |
37 | </I> | |
38 | I suppose it could be useful to have AJOIN report potential problems, | |
39 | but on the other hand that wouldn't do anything about the case where the | |
40 | channel is set to RESTRICTED afterwards. And if a user wants to flood the | |
41 | network, there are plenty of easier ways--spam /ns HELP, for example. (: | |
42 | ||
43 | --Andrew Church | |
44 | <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
45 | <A HREF="http://achurch.org/">http://achurch.org/</A> | |
46 | </PRE> | |
47 | ||
48 | <!--endarticle--> | |
49 | <HR> | |
50 | <P><UL> | |
51 | <!--threads--> | |
52 | <LI>Previous message: <A HREF="005206.html">[IRCServices] Re: NS AJOIN and CS SET RESTRICTED | |
53 | </A></li> | |
54 | <LI>Next message: <A HREF="005204.html">[IRCServices] NS AJOIN and CS SET RESTRICTED | |
55 | </A></li> | |
56 | <LI> <B>Messages sorted by:</B> | |
57 | <a href="date.html#5207">[ date ]</a> | |
58 | <a href="thread.html#5207">[ thread ]</a> | |
59 | <a href="subject.html#5207">[ subject ]</a> | |
60 | <a href="author.html#5207">[ author ]</a> | |
61 | </LI> | |
62 | </UL> | |
63 | ||
64 | </body></html> |