[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2004 / 003051.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices Coding] operserv - reverse wildcard lookup?
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20operserv%20-%20reverse%20wildcard%20lookup%3F&In-Reply-To=1089912233.40f6bda98f14f%40webmailapp4.cc.utexas.edu">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="003045.html">
   <LINK REL="Next"  HREF="003046.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices Coding] operserv - reverse wildcard lookup?</H1>
    <B>Andrew Church</B> 
    <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20operserv%20-%20reverse%20wildcard%20lookup%3F&In-Reply-To=1089912233.40f6bda98f14f%40webmailapp4.cc.utexas.edu"
       TITLE="[IRCServices Coding] operserv - reverse wildcard lookup?">achurch at achurch.org
       </A><BR>
    <I>Fri Jul 16 10:30:39 PDT 2004</I>
    <P><UL>
        <LI>Previous message: <A HREF="003045.html">[IRCServices Coding] operserv - reverse wildcard lookup?
</A></li>
        <LI>Next message: <A HREF="003046.html">[IRCServices Coding] Help
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#3051">[ date ]</a>
              <a href="thread.html#3051">[ thread ]</a>
              <a href="subject.html#3051">[ subject ]</a>
              <a href="author.html#3051">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>     Good idea--I'll see about adding it to 5.1.

  --Andrew Church
    <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
    <A HREF="http://achurch.org/">http://achurch.org/</A>

&gt;<i>Hi, lowly oper on one of Espernet's servers, here; might make a server of my own
</I>&gt;<i>after moving to Japan soon for JET, depending on available connection and
</I>&gt;<i>computer parts. New to this list. Anyway, enough for introductions, on to why I
</I>&gt;<i>joined:
</I>&gt;<i>
</I>&gt;<i>Can operserv be made to (optionally, at each command) perform 'akill view' and
</I>&gt;<i>'akill list' commands using the wildcard evaluation in reverse?
</I>&gt;<i>
</I>&gt;<i>What I mean is: I type in &quot;/msg operserv akill list-r <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">malak at 218.22.22.40</A>&quot; and
</I>&gt;<i>operserv tells me &quot;sup. you've got an akill phrased like '*@218.22.*', and
</I>&gt;<i>that's what's killing him.&quot;
</I>&gt;<i>
</I>&gt;<i>This would alleviate the issue of, upon seeing a user presenting his address and
</I>&gt;<i>asking why he's akilled, an oper having to /guess/ what part of the address is
</I>&gt;<i>in the set akill. In other words, this:...
</I>&gt;<i>
</I>&gt;<i>[11:53:44] -&gt; *operserv* akill list *218.22.22.40*
</I>&gt;<i>[11:53:45] -OperServ- Current AKILL list:
</I>&gt;<i>[11:53:47] -&gt; *operserv* akill list *218.22.22.*
</I>&gt;<i>[11:53:48] -OperServ- Current AKILL list:
</I>&gt;<i>[11:53:51] -&gt; *operserv* akill list *218.22*
</I>&gt;<i>[11:53:52] -OperServ- Current AKILL list:
</I>&gt;<i>
</I>&gt;<i>...wouldn't need to happen.
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>I don't know how the innards of the coding are set up, but it strikes me as
</I>&gt;<i>likely that there's probably a single function somewhere that takes in two
</I>&gt;<i>strings and returns a bool based on whether the first string matches the
</I>&gt;<i>wildcard structure of the second string. If I'm right about that, then the
</I>&gt;<i>whole code for 'akill list' could be duplicated, with the only change (aside
</I>&gt;<i>from the name) being reversing the order in which the two strings go into that
</I>&gt;<i>function when it's called. (Unless I'm missing something--it admittedly has
</I>&gt;<i>been a couple years since I coded.)
</I>&gt;<i>
</I>&gt;<i>I apologize if this idea has been brought up before--I skimmed through the list
</I>&gt;<i>of changes to 5.0 on the website and didn't see anything that looked like what
</I>&gt;<i>I am thinking.
</I>&gt;<i>
</I>&gt;<i>Thanks for your time,
</I>&gt;<i>Rob Hamilton
</I>&gt;<i>'Chimerasame'
</I>&gt;<i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">chime at mail.utexas.edu</A> / <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">chime at esper.net</A>
</I>&gt;<i>
</I>&gt;<i>------------------------------------------------------------------
</I>&gt;<i>To unsubscribe or change your subscription options, visit:
</I>&gt;<i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
</I>

</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="003045.html">[IRCServices Coding] operserv - reverse wildcard lookup?
</A></li>
	<LI>Next message: <A HREF="003046.html">[IRCServices Coding] Help
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#3051">[ date ]</a>
              <a href="thread.html#3051">[ thread ]</a>
              <a href="subject.html#3051">[ subject ]</a>
              <a href="author.html#3051">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices Coding] operserv - reverse wildcard lookup?
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20operserv%20-%20reverse%20wildcard%20lookup%3F&In-Reply-To=1089912233.40f6bda98f14f%40webmailapp4.cc.utexas.edu">
	8	<META NAME="robots" CONTENT="index,nofollow">
	9	<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
	10	<LINK REL="Previous" HREF="003045.html">
	11	<LINK REL="Next" HREF="003046.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices Coding] operserv - reverse wildcard lookup?</H1>
	15	<B>Andrew Church</B>
	16	<A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20operserv%20-%20reverse%20wildcard%20lookup%3F&In-Reply-To=1089912233.40f6bda98f14f%40webmailapp4.cc.utexas.edu"
	17	TITLE="[IRCServices Coding] operserv - reverse wildcard lookup?">achurch at achurch.org
	18	</A><BR>
	19	<I>Fri Jul 16 10:30:39 PDT 2004</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="003045.html">[IRCServices Coding] operserv - reverse wildcard lookup?
	22	</A></li>
	23	<LI>Next message: <A HREF="003046.html">[IRCServices Coding] Help
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#3051">[ date ]</a>
	27	<a href="thread.html#3051">[ thread ]</a>
	28	<a href="subject.html#3051">[ subject ]</a>
	29	<a href="author.html#3051">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE> Good idea--I'll see about adding it to 5.1.
	35
	36	--Andrew Church
	37	<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
	38	<A HREF="http://achurch.org/">http://achurch.org/</A>
	39
	40	><i>Hi, lowly oper on one of Espernet's servers, here; might make a server of my own
	41	</I>><i>after moving to Japan soon for JET, depending on available connection and
	42	</I>><i>computer parts. New to this list. Anyway, enough for introductions, on to why I
	43	</I>><i>joined:
	44	</I>><i>
	45	</I>><i>Can operserv be made to (optionally, at each command) perform 'akill view' and
	46	</I>><i>'akill list' commands using the wildcard evaluation in reverse?
	47	</I>><i>
	48	</I>><i>What I mean is: I type in "/msg operserv akill list-r <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">malak at 218.22.22.40</A>" and
	49	</I>><i>operserv tells me "sup. you've got an akill phrased like '@218.22.', and
	50	</I>><i>that's what's killing him."
	51	</I>><i>
	52	</I>><i>This would alleviate the issue of, upon seeing a user presenting his address and
	53	</I>><i>asking why he's akilled, an oper having to /guess/ what part of the address is
	54	</I>><i>in the set akill. In other words, this:...
	55	</I>><i>
	56	</I>><i>[11:53:44] -> operserv akill list 218.22.22.40
	57	</I>><i>[11:53:45] -OperServ- Current AKILL list:
	58	</I>><i>[11:53:47] -> operserv akill list 218.22.22.
	59	</I>><i>[11:53:48] -OperServ- Current AKILL list:
	60	</I>><i>[11:53:51] -> operserv akill list 218.22
	61	</I>><i>[11:53:52] -OperServ- Current AKILL list:
	62	</I>><i>
	63	</I>><i>...wouldn't need to happen.
	64	</I>><i>
65	</I>><i>
66	</I>><i>
67	</I>><i>I don't know how the innards of the coding are set up, but it strikes me as
68	</I>><i>likely that there's probably a single function somewhere that takes in two
69	</I>><i>strings and returns a bool based on whether the first string matches the
70	</I>><i>wildcard structure of the second string. If I'm right about that, then the
71	</I>><i>whole code for 'akill list' could be duplicated, with the only change (aside
72	</I>><i>from the name) being reversing the order in which the two strings go into that
73	</I>><i>function when it's called. (Unless I'm missing something--it admittedly has
74	</I>><i>been a couple years since I coded.)
75	</I>><i>
76	</I>><i>I apologize if this idea has been brought up before--I skimmed through the list
77	</I>><i>of changes to 5.0 on the website and didn't see anything that looked like what
78	</I>><i>I am thinking.
79	</I>><i>
80	</I>><i>Thanks for your time,
81	</I>><i>Rob Hamilton
82	</I>><i>'Chimerasame'
83	</I>><i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">chime at mail.utexas.edu</A> / <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">chime at esper.net</A>
84	</I>><i>
85	</I>><i>------------------------------------------------------------------
86	</I>><i>To unsubscribe or change your subscription options, visit:
87	</I>><i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
88	</I>
89
90	</PRE>
91
92	<!--endarticle-->
93	<HR>
94	<P><UL>
95	<!--threads-->
96	<LI>Previous message: <A HREF="003045.html">[IRCServices Coding] operserv - reverse wildcard lookup?
97	</A></li>
98	<LI>Next message: <A HREF="003046.html">[IRCServices Coding] Help
99	</A></li>
100	<LI> <B>Messages sorted by:</B>
101	<a href="date.html#3051">[ date ]</a>
102	<a href="thread.html#3051">[ thread ]</a>
103	<a href="subject.html#3051">[ subject ]</a>
104	<a href="author.html#3051">[ author ]</a>
105	</LI>
106	</UL>
107
108	</body></html>