]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
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="001845.html"> | |
11 | <LINK REL="Next" HREF="001847.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices] /notice??</H1> | |
15 | <B>Countersync</B> | |
16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20/notice%3F%3F&In-Reply-To=" | |
17 | TITLE="[IRCServices] /notice??">countersync at hotmail.com | |
18 | </A><BR> | |
19 | <I>Wed May 9 03:16:01 PDT 2001</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001845.html">[IRCServices] /notice?? | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001847.html">[IRCServices] /notice?? | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1846">[ date ]</a> | |
27 | <a href="thread.html#1846">[ thread ]</a> | |
28 | <a href="subject.html#1846">[ subject ]</a> | |
29 | <a href="author.html#1846">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>I think that what Adam was referring to is something similar to how you can | |
35 | link nicknames together so that you can attain the privileges that have been | |
36 | attached to any of them through any in the linkage set. However this would | |
37 | be different in that it would be limited to that session instead of a | |
38 | permanent linkage. Or more simply put, identify to nickserv as being a user | |
39 | without actually holding that nickname. In fact the second description is | |
40 | better because it doesn't necessarily mean that the nickname your using | |
41 | needs to be registered or otherwise documented anywhere else within | |
42 | services. Quite a handy method for escaping private message floods or just | |
43 | anyone who wants to talk with you. | |
44 | ||
45 | Though there would then be issues with memoserv. Perhaps modifying the | |
46 | memoserv format (or allowing only one of two formats) to be used which would | |
47 | include a 'from' token as well as a to token. The memoserv feature alone | |
48 | would be a good idea as it could be VERY useful to send messages from a | |
49 | nickname without necessarily being that nickname, only linked to it. | |
50 | ||
51 | (For example if a user has a robot programmed to do something and they trust | |
52 | it; the bot could be linked to their nickname and send messages through that | |
53 | nickname. Or another example which would be more common; the user has many | |
54 | nicknames and is using one in one channel when they receive a memo. Without | |
55 | having to change their name to respond they could use the more familiar | |
56 | nickname to send a reply back.) | |
57 | ||
58 | A second thought occurs though that services may only keep track of | |
59 | registered names and otherwise operate in a way that would hinder the first | |
60 | idea. I don't know enough C/C++ to even think of reading the source to know | |
61 | for sure, but just the concept design seems like this might be difficult to | |
62 | pull off. | |
63 | ----- Original Message ----- | |
64 | From: "Strider" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">strider at chatcircuit.com</A>> | |
65 | Sent: Tuesday, May 08, 2001 23:27 | |
66 | ><i> This is something that has to be scripted into your client or programmed | |
67 | </I>><i> into the ircd. This has nothing to do with services. UnrealIRCd comes with | |
68 | </I>><i> this features, and my irc script, well the one i use to use also had a | |
69 | </I>><i> feature that redirected /nickserv to /msg nickserv. These 2 methods are | |
70 | </I>very | |
71 | ><i> different however. | |
72 | </I>><i> | |
73 | </I>><i> Beau (Strider) Steward | |
74 | </I>><i> ----- Original Message ----- | |
75 | </I>><i> From: "Adam" <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">korn_fan at dingoblue.net.au</A>> | |
76 | </I>><i> Sent: Tuesday, May 08, 2001 6:09 PM | |
77 | </I>><i> > Hey, i know its slightly off topic.. but why cant i use /nickserv | |
78 | </I>identify | |
79 | ><i> > <nick> <password> | |
80 | </I>><i> > | |
81 | </I>><i> > i think this is a very usefull feature and should be included. :-) | |
82 | </I>><i> > | |
83 | </I>><i> > Adam | |
84 | </I> | |
85 | </PRE> | |
86 | ||
87 | <!--endarticle--> | |
88 | <HR> | |
89 | <P><UL> | |
90 | <!--threads--> | |
91 | <LI>Previous message: <A HREF="001845.html">[IRCServices] /notice?? | |
92 | </A></li> | |
93 | <LI>Next message: <A HREF="001847.html">[IRCServices] /notice?? | |
94 | </A></li> | |
95 | <LI> <B>Messages sorted by:</B> | |
96 | <a href="date.html#1846">[ date ]</a> | |
97 | <a href="thread.html#1846">[ thread ]</a> | |
98 | <a href="subject.html#1846">[ subject ]</a> | |
99 | <a href="author.html#1846">[ author ]</a> | |
100 | </LI> | |
101 | </UL> | |
102 | ||
103 | </body></html> |