[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001478.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices] Services Suggestion - NickServ
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20Suggestion%20-%20NickServ&In-Reply-To=3A945934.7266840C%40expres.ro">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001474.html">
   <LINK REL="Next"  HREF="001479.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices] Services Suggestion - NickServ</H1>
    <B>Mark Hetherington (Eurocom)</B> 
    <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20Suggestion%20-%20NickServ&In-Reply-To=3A945934.7266840C%40expres.ro"
       TITLE="[IRCServices] Services Suggestion - NickServ">markh at eurodltd.co.uk
       </A><BR>
    <I>Thu Feb 22 21:50:03 PST 2001</I>
    <P><UL>
        <LI>Previous message: <A HREF="001474.html">[IRCServices] nickserv
</A></li>
        <LI>Next message: <A HREF="001479.html">AW: [IRCServices] Services Suggestion - NickServ
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1478">[ date ]</a>
              <a href="thread.html#1478">[ thread ]</a>
              <a href="subject.html#1478">[ subject ]</a>
              <a href="author.html#1478">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>We have a number of users that come from Java clients. As is the nature of
many java based IRC interfaces they have a &quot;default&quot; nickname and use an
incrementing numerical suffix to maintain some form of unique nicknames.  A
majority of users of this service tend to use the default despite a number
of encouragements to choose their own nickname first. It was &quot;interesting&quot;
to see how many people actually joined a chat called TypeYourNameHere...
hehe.

The problem comes when one of these visitors registers the nickname. E.g.
JavaGuest. The next JavaGuest coming in with that name will get forcibly
changed to Guestnnn by Nickserv.

NS now seems to correctly prevent the registration of it's own internal
Guest names and there appears to be an appropriate flag to detect that a
nick is &quot;guested&quot; so working from this base, I see two possible solutions:

1) The current NS supports suspension and forbidding of nicknames. Add a new
state that does not forbid the use of the nickname but forbids registration
of it. This however would be limited in application since each name
generation by the JavaChat program would have to be set to this status
creating a human workload that services is largely designed to remove.

2) Add in support for multiple user defined &quot;guest&quot; nickname types. This
way, anyone whose nick is say JavaChatnnnn could be handled by the same code
which handles services native guest names. Although probably easier as a
configuration file change (as with the native current guest prefix), a
registration mechanism with NS would be preferable. For the purpose of NS
processing it could maybe use the new status value described above but
merely stores a prefix in the database rather than an explicit nickname and
the nick be flagged to be processed as a guest nick type. Maybe a new
command /NS REGISTERGUEST &lt;JavaChatPrefix&gt; &lt;PrefixOwnerEmail&gt;.


Mark.
CTCP Networks.


</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001474.html">[IRCServices] nickserv
</A></li>
	<LI>Next message: <A HREF="001479.html">AW: [IRCServices] Services Suggestion - NickServ
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1478">[ date ]</a>
              <a href="thread.html#1478">[ thread ]</a>
              <a href="subject.html#1478">[ subject ]</a>
              <a href="author.html#1478">[ 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] Services Suggestion - NickServ
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20Suggestion%20-%20NickServ&In-Reply-To=3A945934.7266840C%40expres.ro">
	8	<META NAME="robots" CONTENT="index,nofollow">
	9	<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
	10	<LINK REL="Previous" HREF="001474.html">
	11	<LINK REL="Next" HREF="001479.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices] Services Suggestion - NickServ</H1>
	15	<B>Mark Hetherington (Eurocom)</B>
	16	<A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%20Suggestion%20-%20NickServ&In-Reply-To=3A945934.7266840C%40expres.ro"
	17	TITLE="[IRCServices] Services Suggestion - NickServ">markh at eurodltd.co.uk
	18	</A><BR>
	19	<I>Thu Feb 22 21:50:03 PST 2001</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="001474.html">[IRCServices] nickserv
	22	</A></li>
	23	<LI>Next message: <A HREF="001479.html">AW: [IRCServices] Services Suggestion - NickServ
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#1478">[ date ]</a>
	27	<a href="thread.html#1478">[ thread ]</a>
	28	<a href="subject.html#1478">[ subject ]</a>
	29	<a href="author.html#1478">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>We have a number of users that come from Java clients. As is the nature of
	35	many java based IRC interfaces they have a "default" nickname and use an
	36	incrementing numerical suffix to maintain some form of unique nicknames. A
	37	majority of users of this service tend to use the default despite a number
	38	of encouragements to choose their own nickname first. It was "interesting"
	39	to see how many people actually joined a chat called TypeYourNameHere...
	40	hehe.
	41
	42	The problem comes when one of these visitors registers the nickname. E.g.
	43	JavaGuest. The next JavaGuest coming in with that name will get forcibly
	44	changed to Guestnnn by Nickserv.
	45
	46	NS now seems to correctly prevent the registration of it's own internal
	47	Guest names and there appears to be an appropriate flag to detect that a
	48	nick is "guested" so working from this base, I see two possible solutions:
	49
	50	1) The current NS supports suspension and forbidding of nicknames. Add a new
	51	state that does not forbid the use of the nickname but forbids registration
	52	of it. This however would be limited in application since each name
	53	generation by the JavaChat program would have to be set to this status
	54	creating a human workload that services is largely designed to remove.
	55
	56	2) Add in support for multiple user defined "guest" nickname types. This
	57	way, anyone whose nick is say JavaChatnnnn could be handled by the same code
	58	which handles services native guest names. Although probably easier as a
	59	configuration file change (as with the native current guest prefix), a
	60	registration mechanism with NS would be preferable. For the purpose of NS
	61	processing it could maybe use the new status value described above but
	62	merely stores a prefix in the database rather than an explicit nickname and
	63	the nick be flagged to be processed as a guest nick type. Maybe a new
	64	command /NS REGISTERGUEST <JavaChatPrefix> <PrefixOwnerEmail>.
65
66
67	Mark.
68	CTCP Networks.
69
70
71
72	</PRE>
73
74	<!--endarticle-->
75	<HR>
76	<P><UL>
77	<!--threads-->
78	<LI>Previous message: <A HREF="001474.html">[IRCServices] nickserv
79	</A></li>
80	<LI>Next message: <A HREF="001479.html">AW: [IRCServices] Services Suggestion - NickServ
81	</A></li>
82	<LI> <B>Messages sorted by:</B>
83	<a href="date.html#1478">[ date ]</a>
84	<a href="thread.html#1478">[ thread ]</a>
85	<a href="subject.html#1478">[ subject ]</a>
86	<a href="author.html#1478">[ author ]</a>
87	</LI>
88	</UL>
89
90	</body></html>