]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2001/001848.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2001 / 001848.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] /notice??
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20/notice%3F%3F&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="001847.html">
11 <LINK REL="Next" HREF="001849.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] /notice??</H1>
15 <B>ViPeR</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20/notice%3F%3F&In-Reply-To="
17 TITLE="[IRCServices] /notice??">viper at wcalliance.com
18 </A><BR>
19 <I>Wed May 9 03:27:02 PDT 2001</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001847.html">[IRCServices] /notice??
22 </A></li>
23 <LI>Next message: <A HREF="001849.html">[IRCServices] /notice??
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#1848">[ date ]</a>
27 <a href="thread.html#1848">[ thread ]</a>
28 <a href="subject.html#1848">[ subject ]</a>
29 <a href="author.html#1848">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>What you are talking about is more like a login system with 'email' aka
35 memos, that also happens to save a nickname for you. This idea sounds
36 pretty cool, as it could handle a person using their privileges under any
37 nick, allowing you to use any extension like [zzz] or [away] [afk] etc etc
38 and still be able to access your functions, all this without the hassle of
39 registering all the nicks and linking them to your primary nick. The idea
40 could work, but its a long way from the current IRCServices setup, and would
41 go more toward the idea of no access list for nicks, and nicks would become
42 more like logins. (ie the stuff Andrew discussed about version 5)
43
44 --ViPeRzPiT
45 viper at wcalliance dot com
46 ----- Original Message -----
47 From: &quot;Countersync&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">countersync at hotmail.com</A>&gt;
48 To: &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at ircservices.za.net</A>&gt;
49 Sent: Tuesday, May 08, 2001 9:02 PM
50 Subject: Re: [IRCServices] /notice??
51
52
53 &gt;<i> I think that what Adam was referring to is something similar to how you
54 </I>can
55 &gt;<i> link nicknames together so that you can attain the privileges that have
56 </I>been
57 &gt;<i> attached to any of them through any in the linkage set. However this
58 </I>would
59 &gt;<i> be different in that it would be limited to that session instead of a
60 </I>&gt;<i> permanent linkage. Or more simply put, identify to nickserv as being a
61 </I>user
62 &gt;<i> without actually holding that nickname. In fact the second description is
63 </I>&gt;<i> better because it doesn't necessarily mean that the nickname your using
64 </I>&gt;<i> needs to be registered or otherwise documented anywhere else within
65 </I>&gt;<i> services. Quite a handy method for escaping private message floods or
66 </I>just
67 &gt;<i> anyone who wants to talk with you.
68 </I>&gt;<i>
69 </I>&gt;<i> Though there would then be issues with memoserv. Perhaps modifying the
70 </I>&gt;<i> memoserv format (or allowing only one of two formats) to be used which
71 </I>would
72 &gt;<i> include a 'from' token as well as a to token. The memoserv feature alone
73 </I>&gt;<i> would be a good idea as it could be VERY useful to send messages from a
74 </I>&gt;<i> nickname without necessarily being that nickname, only linked to it.
75 </I>&gt;<i>
76 </I>&gt;<i> (For example if a user has a robot programmed to do something and they
77 </I>trust
78 &gt;<i> it; the bot could be linked to their nickname and send messages through
79 </I>that
80 &gt;<i> nickname. Or another example which would be more common; the user has
81 </I>many
82 &gt;<i> nicknames and is using one in one channel when they receive a memo.
83 </I>Without
84 &gt;<i> having to change their name to respond they could use the more familiar
85 </I>&gt;<i> nickname to send a reply back.)
86 </I>&gt;<i>
87 </I>&gt;<i> A second thought occurs though that services may only keep track of
88 </I>&gt;<i> registered names and otherwise operate in a way that would hinder the
89 </I>first
90 &gt;<i> idea. I don't know enough C/C++ to even think of reading the source to
91 </I>know
92 &gt;<i> for sure, but just the concept design seems like this might be difficult
93 </I>to
94 &gt;<i> pull off.
95 </I>&gt;<i> ----- Original Message -----
96 </I>&gt;<i> From: &quot;Strider&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">strider at chatcircuit.com</A>&gt;
97 </I>&gt;<i> Sent: Tuesday, May 08, 2001 23:27
98 </I>&gt;<i> &gt; This is something that has to be scripted into your client or programmed
99 </I>&gt;<i> &gt; into the ircd. This has nothing to do with services. UnrealIRCd comes
100 </I>with
101 &gt;<i> &gt; this features, and my irc script, well the one i use to use also had a
102 </I>&gt;<i> &gt; feature that redirected /nickserv to /msg nickserv. These 2 methods are
103 </I>&gt;<i> very
104 </I>&gt;<i> &gt; different however.
105 </I>&gt;<i> &gt;
106 </I>&gt;<i> &gt; Beau (Strider) Steward
107 </I>&gt;<i> &gt; ----- Original Message -----
108 </I>&gt;<i> &gt; From: &quot;Adam&quot; &lt;<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">korn_fan at dingoblue.net.au</A>&gt;
109 </I>&gt;<i> &gt; Sent: Tuesday, May 08, 2001 6:09 PM
110 </I>&gt;<i> &gt; &gt; Hey, i know its slightly off topic.. but why cant i use /nickserv
111 </I>&gt;<i> identify
112 </I>&gt;<i> &gt; &gt; &lt;nick&gt; &lt;password&gt;
113 </I>&gt;<i> &gt; &gt;
114 </I>&gt;<i> &gt; &gt; i think this is a very usefull feature and should be included. :-)
115 </I>&gt;<i> &gt; &gt;
116 </I>&gt;<i> &gt; &gt; Adam
117 </I>&gt;<i> -----------------------------------------------------------
118 </I>&gt;<i> To unsubscribe, mail <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net</A>
119 </I>&gt;<i> with the word UNSUBSCRIBE in the subject of the mail.
120 </I>&gt;<i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A>
121 </I>&gt;<i>
122 </I>
123
124 </PRE>
125
126 <!--endarticle-->
127 <HR>
128 <P><UL>
129 <!--threads-->
130 <LI>Previous message: <A HREF="001847.html">[IRCServices] /notice??
131 </A></li>
132 <LI>Next message: <A HREF="001849.html">[IRCServices] /notice??
133 </A></li>
134 <LI> <B>Messages sorted by:</B>
135 <a href="date.html#1848">[ date ]</a>
136 <a href="thread.html#1848">[ thread ]</a>
137 <a href="subject.html#1848">[ subject ]</a>
138 <a href="author.html#1848">[ author ]</a>
139 </LI>
140 </UL>
141
142 </body></html>