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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices Coding] The case of the non-existant user
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20The%20case%20of%20the%20non-existant%20user&In-Reply-To=">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="000368.html">
   <LINK REL="Next"  HREF="000370.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices Coding] The case of the non-existant user</H1>
    <B>Mark Hetherington</B> 
    <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20The%20case%20of%20the%20non-existant%20user&In-Reply-To="
       TITLE="[IRCServices Coding] The case of the non-existant user">mark at ctcp.net
       </A><BR>
    <I>Sat Mar  2 18:31:16 PST 2002</I>
    <P><UL>
        <LI>Previous message: <A HREF="000368.html">[IRCServices Coding] Services 5.0 +S user bug
</A></li>
        <LI>Next message: <A HREF="000370.html">[IRCServices Coding] The case of the non-existant user
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#369">[ date ]</a>
              <a href="thread.html#369">[ thread ]</a>
              <a href="subject.html#369">[ subject ]</a>
              <a href="author.html#369">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Odd scenario, and I am not sure whether services should/could support it, 
but since it seems to be the cause of a particular chain of log messages, 
it could well be something for the FAQ if it is not something that 
should/could be supported.

A user logs on to IRC, identifies to NickServ then joins a channel that he 
has auto-op rights on. He then immediately changes nickname to another 
nickname (registered or not). Services logs the fact that a mode change was 
requested for a nonexistant user. The nicknames in the example are not 
linked. 

&gt;<i>From logs:
</I>
[channel]
[14:38] Damon (<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">damon at xxxx</A>) joined #channel.
[14:38] Nick change: Damon -&gt; Memphis

[Services.log]
[Mar 02 14:38:59 2002] nickserv/main: Damon!<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">damon at xxxx</A> identified for nick 
Damon
[Mar 02 14:38:59 2002] channel: MODE #channel +o for nonexistent user Damon
[Mar 02 14:39:13 2002] nickserv/main: Memphis!<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">damon at xxxx</A> identified for 
nick Memphis

I have not managed to be quick enough to reproduce this 100% hence my lack 
of knowledge on whether this affects linked nicknames, but in my defence it 
is kinda late here and the timing is somewhat critical :). I suspect that 
it may apply to linked nicknames as well but assuming that services logs an 
error returned by the attempt to set a mode, I imagine the linked nick 
would trigger another test which may make mitigate the problem from a 
user's perspective.

I guess it would quite complex for services to track the user and supress 
the error as well as leading to potential circular lockup, so maybe just 
one for the FAQ. 


-- 
Mark.


</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="000368.html">[IRCServices Coding] Services 5.0 +S user bug
</A></li>
	<LI>Next message: <A HREF="000370.html">[IRCServices Coding] The case of the non-existant user
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#369">[ date ]</a>
              <a href="thread.html#369">[ thread ]</a>
              <a href="subject.html#369">[ subject ]</a>
              <a href="author.html#369">[ 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] The case of the non-existant user
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20The%20case%20of%20the%20non-existant%20user&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="000368.html">
	11	<LINK REL="Next" HREF="000370.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices Coding] The case of the non-existant user</H1>
	15	<B>Mark Hetherington</B>
	16	<A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20The%20case%20of%20the%20non-existant%20user&In-Reply-To="
	17	TITLE="[IRCServices Coding] The case of the non-existant user">mark at ctcp.net
	18	</A><BR>
	19	<I>Sat Mar 2 18:31:16 PST 2002</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="000368.html">[IRCServices Coding] Services 5.0 +S user bug
	22	</A></li>
	23	<LI>Next message: <A HREF="000370.html">[IRCServices Coding] The case of the non-existant user
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#369">[ date ]</a>
	27	<a href="thread.html#369">[ thread ]</a>
	28	<a href="subject.html#369">[ subject ]</a>
	29	<a href="author.html#369">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>Odd scenario, and I am not sure whether services should/could support it,
	35	but since it seems to be the cause of a particular chain of log messages,
	36	it could well be something for the FAQ if it is not something that
	37	should/could be supported.
	38
	39	A user logs on to IRC, identifies to NickServ then joins a channel that he
	40	has auto-op rights on. He then immediately changes nickname to another
	41	nickname (registered or not). Services logs the fact that a mode change was
	42	requested for a nonexistant user. The nicknames in the example are not
	43	linked.
	44
	45	><i>From logs:
	46	</I>
	47	[channel]
	48	[14:38] Damon (<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">damon at xxxx</A>) joined #channel.
	49	[14:38] Nick change: Damon -> Memphis
	50
	51	[Services.log]
	52	[Mar 02 14:38:59 2002] nickserv/main: Damon!<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">damon at xxxx</A> identified for nick
	53	Damon
	54	[Mar 02 14:38:59 2002] channel: MODE #channel +o for nonexistent user Damon
	55	[Mar 02 14:39:13 2002] nickserv/main: Memphis!<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">damon at xxxx</A> identified for
	56	nick Memphis
	57
	58	I have not managed to be quick enough to reproduce this 100% hence my lack
	59	of knowledge on whether this affects linked nicknames, but in my defence it
	60	is kinda late here and the timing is somewhat critical :). I suspect that
	61	it may apply to linked nicknames as well but assuming that services logs an
	62	error returned by the attempt to set a mode, I imagine the linked nick
	63	would trigger another test which may make mitigate the problem from a
	64	user's perspective.
65
66	I guess it would quite complex for services to track the user and supress
67	the error as well as leading to potential circular lockup, so maybe just
68	one for the FAQ.
69
70
71	--
72	Mark.
73
74
75
76	</PRE>
77
78	<!--endarticle-->
79	<HR>
80	<P><UL>
81	<!--threads-->
82	<LI>Previous message: <A HREF="000368.html">[IRCServices Coding] Services 5.0 +S user bug
83	</A></li>
84	<LI>Next message: <A HREF="000370.html">[IRCServices Coding] The case of the non-existant user
85	</A></li>
86	<LI> <B>Messages sorted by:</B>
87	<a href="date.html#369">[ date ]</a>
88	<a href="thread.html#369">[ thread ]</a>
89	<a href="subject.html#369">[ subject ]</a>
90	<a href="author.html#369">[ author ]</a>
91	</LI>
92	</UL>
93
94	</body></html>