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