]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
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=20030312192251.A3632%40mbay.net"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="001966.html"> | |
11 | <LINK REL="Next" HREF="001968.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices Coding] Chanserv patch for reg chans only</H1> | |
15 | <B>Andrew Church</B> | |
16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Chanserv%20patch%20for%20reg%20chans%20only&In-Reply-To=20030312192251.A3632%40mbay.net" | |
17 | TITLE="[IRCServices Coding] Chanserv patch for reg chans only">achurch at achurch.org | |
18 | </A><BR> | |
19 | <I>Thu Mar 13 13:09:56 PST 2003</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001966.html">[IRCServices Coding] Chanserv patch for reg chans only | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001968.html">[IRCServices Coding] None | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1967">[ date ]</a> | |
27 | <a href="thread.html#1967">[ thread ]</a> | |
28 | <a href="subject.html#1967">[ subject ]</a> | |
29 | <a href="author.html#1967">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE> Thanks for the suggestion. I generally try to avoid adding features | |
35 | into a stable branch, but I'll consider it. | |
36 | ||
37 | ><i>The other question I had was if I should depend on the result from | |
38 | </I>><i>get_channelinfo() or get_channel() to determine if a channel is | |
39 | </I>><i>registered. I found the code for get_channelinfo() in tools/convert-db.c, | |
40 | </I>><i>and it seems to be a good bet for this, but I can't find the code for | |
41 | </I>><i>get_channel() anywhere. The text shows up in channels.o, but I can't | |
42 | </I>><i>find the code in channels.c. I feel a bit silly about this - I always | |
43 | </I>><i>thought I was fairly good at C. | |
44 | </I> | |
45 | Both get_channel() and get_channelinfo() are defined by macros in | |
46 | hash.h (the get_channelinfo() in convert-db.c is designed for the | |
47 | convert-db tool and is not included in the main program). get_channel() | |
48 | looks up channels on the network, while get_channelinfo() looks them up in | |
49 | the Services database, so you'll want to use the latter. | |
50 | ||
51 | ><i>This is a fairly unusual situation, but it might be more consistant if | |
52 | </I>><i>the ban wasn't set. However, does this open services up for a DOS from | |
53 | </I>><i>a user repeatedly trying to join and getting kicked by chanserv? | |
54 | </I> | |
55 | Unlikely, since the ircd would probably drop them for flooding before | |
56 | Services took any serious performance hit. | |
57 | ||
58 | --Andrew Church | |
59 | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A> | |
60 | <A HREF="http://achurch.org/">http://achurch.org/</A> | |
61 | </PRE> | |
62 | ||
63 | <!--endarticle--> | |
64 | <HR> | |
65 | <P><UL> | |
66 | <!--threads--> | |
67 | <LI>Previous message: <A HREF="001966.html">[IRCServices Coding] Chanserv patch for reg chans only | |
68 | </A></li> | |
69 | <LI>Next message: <A HREF="001968.html">[IRCServices Coding] None | |
70 | </A></li> | |
71 | <LI> <B>Messages sorted by:</B> | |
72 | <a href="date.html#1967">[ date ]</a> | |
73 | <a href="thread.html#1967">[ thread ]</a> | |
74 | <a href="subject.html#1967">[ subject ]</a> | |
75 | <a href="author.html#1967">[ author ]</a> | |
76 | </LI> | |
77 | </UL> | |
78 | ||
79 | </body></html> |