]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2005/003152.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2005 / 003152.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices Coding] Possible new callback on AUTH
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.esper.net?Subject=%5BIRCServices%20Coding%5D%20Possible%20new%20callback%20on%20AUTH&In-Reply-To=430aa519.12601%40msgid.achurch.org">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="003151.html">
11 <LINK REL="Next" HREF="003153.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices Coding] Possible new callback on AUTH</H1>
15 <B>Robin Burchell</B>
16 <A HREF="mailto:ircservices-coding%40ircservices.esper.net?Subject=%5BIRCServices%20Coding%5D%20Possible%20new%20callback%20on%20AUTH&In-Reply-To=430aa519.12601%40msgid.achurch.org"
17 TITLE="[IRCServices Coding] Possible new callback on AUTH">surreal.w00t at gmail.com
18 </A><BR>
19 <I>Mon Aug 22 21:36:24 PDT 2005</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="003151.html">[IRCServices Coding] Possible new callback on AUTH
22 </A></li>
23 <LI>Next message: <A HREF="003153.html">[IRCServices Coding] Possible new callback on AUTH
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#3152">[ date ]</a>
27 <a href="thread.html#3152">[ thread ]</a>
28 <a href="subject.html#3152">[ subject ]</a>
29 <a href="author.html#3152">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Andrew Church wrote:
35 &gt;&gt;&gt;<i>I'm working on a bit of a module to orient new users, but (with spambots
36 </I>&gt;&gt;&gt;<i>and stuff) it's a little inconvenient to do this with the register callback.
37 </I>&gt;&gt;&gt;<i>
38 </I>&gt;&gt;&gt;<i>Not wanting to fork the codebase, would it be at all possible to get a
39 </I>&gt;&gt;&gt;<i>new callback on NS AUTH?
40 </I>&gt;&gt;<i>
41 </I>&gt;&gt;<i> Ordinarily I'd want to wait for 5.1, but seeing as the 5.1 alpha is
42 </I>&gt;&gt;<i>already several lifetimes later than I'd hoped, why not? (: I'll add it
43 </I>&gt;&gt;<i>for the next 5.0 release.
44 </I>&gt;<i>
45 </I>&gt;<i>
46 </I>&gt;<i> Actually I guess I should ask: where do you need the callback? Is it
47 </I>&gt;<i> sufficient to have it called after all normal processing, or do you want to
48 </I>&gt;<i> replace part of the normal AUTH processing?
49 </I>&gt;<i>
50 </I>&gt;<i> --Andrew Church
51 </I>&gt;<i> <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
52 </I>&gt;<i> <A HREF="http://achurch.org/">http://achurch.org/</A>
53 </I>
54 (Not sure if this sent the first time, let's try again..)
55
56 After is what I'm needing-
57
58 What I'm doing is making sure a normal user passes all checks, and if
59 so, sending them information - doing this on register isn't a good idea,
60 because of the growing number of spambots that can simply register,
61 putting extra load on Services.
62 </PRE>
63
64
65 <!--endarticle-->
66 <HR>
67 <P><UL>
68 <!--threads-->
69 <LI>Previous message: <A HREF="003151.html">[IRCServices Coding] Possible new callback on AUTH
70 </A></li>
71 <LI>Next message: <A HREF="003153.html">[IRCServices Coding] Possible new callback on AUTH
72 </A></li>
73 <LI> <B>Messages sorted by:</B>
74 <a href="date.html#3152">[ date ]</a>
75 <a href="thread.html#3152">[ thread ]</a>
76 <a href="subject.html#3152">[ subject ]</a>
77 <a href="author.html#3152">[ author ]</a>
78 </LI>
79 </UL>
80
81 </body></html>