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] Feature Suggestion | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Feature%20Suggestion&In-Reply-To=1055675222.2141.8.camel%40dreadnought.hadiko.de"> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="003860.html"> | |
| 11 | <LINK REL="Next" HREF="003862.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices] Feature Suggestion</H1> | |
| 15 | <B>Andrew Church</B> | |
| 16 | <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Feature%20Suggestion&In-Reply-To=1055675222.2141.8.camel%40dreadnought.hadiko.de" | |
| 17 | TITLE="[IRCServices] Feature Suggestion">achurch at achurch.org | |
| 18 | </A><BR> | |
| 19 | <I>Sun Jun 15 20:59:44 PDT 2003</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="003860.html">[IRCServices] Feature Suggestion | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="003862.html">[IRCServices] Suggestion | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#3861">[ date ]</a> | |
| 27 | <a href="thread.html#3861">[ thread ]</a> | |
| 28 | <a href="subject.html#3861">[ subject ]</a> | |
| 29 | <a href="author.html#3861">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE> Identification is only remembered for the purpose of avoiding | |
| 35 | re-identification for IDENTIFY and password entering for RECOVER/RELEASE/ | |
| 36 | GHOST. It is intentionally not used for channel access levels because of | |
| 37 | the ambiguity that would result. (In your example, what if "haha" was on | |
| 38 | the channel access list with level 100? level 30? level -1?) | |
| 39 | ||
| 40 | --Andrew Church | |
| 41 | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
| 42 | <A HREF="http://achurch.org/">http://achurch.org/</A> | |
| 43 | ||
| 44 | ><i>Well; | |
| 45 | </I>><i> | |
| 46 | </I>><i>--- You are now known as testnick | |
| 47 | </I>><i>-NickServ- This nickname is registered and protected. If it is your | |
| 48 | </I>><i>nickname, type /msg NickServ IDENTIFY password. Otherwise, please | |
| 49 | </I>><i>choose a different nickname. | |
| 50 | </I>><i>-NickServ- Password accepted -- you are now recognized. | |
| 51 | </I>><i>--- You are now known as haha | |
| 52 | </I>><i>--> You are now talking on #test | |
| 53 | </I>><i>--- testserv.time.net sets modes [#test +Tn] | |
| 54 | </I>><i>--- services.time.net has changed the topic to: | |
| 55 | </I>><i>--- ChanServ sets modes [#test +ntr-o haha] | |
| 56 | </I>><i> | |
| 57 | </I>><i>The channel's access list contains aop for the nick "testnick" | |
| 58 | </I>><i>-ChanServ- Access list for #test: | |
| 59 | </I>><i>-ChanServ- Num Lev Nickname | |
| 60 | </I>><i>-ChanServ- 1 50 testnick | |
| 61 | </I>><i> | |
| 62 | </I>><i>But ChanServ is still deopping. | |
| 63 | </I>><i>The nickname "haha" is also a registered nickname. | |
| 64 | </I>><i> | |
| 65 | </I>><i>Conclusion: your solution does not work. Since I hope that you read and | |
| 66 | </I>><i>understood my email, I think then this is a bug of services ? | |
| 67 | </I>><i> | |
| 68 | </I>><i>yusuf. | |
| 69 | </I>><i> | |
| 70 | </I>><i>On Sun, 2003-06-15 at 09:03, Andrew Church wrote: | |
| 71 | </I>>><i> /nick OtherNick | |
| 72 | </I>>><i> /ns identify OtherPass | |
| 73 | </I>>><i> /nick FirstNick | |
| 74 | </I>>><i> | |
| 75 | </I>>><i> No to the rest. | |
| 76 | </I>>><i> | |
| 77 | </I>>><i> --Andrew Church | |
| 78 | </I>>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
| 79 | </I>>><i> <A HREF="http://achurch.org/">http://achurch.org/</A> | |
| 80 | </I>>><i> | |
| 81 | </I>>><i> >Hello; | |
| 82 | </I>>><i> > | |
| 83 | </I>>><i> >This time I wanted to tell you a feature suggestion: | |
| 84 | </I>>><i> > | |
| 85 | </I>>><i> >Currently, the nickname link system allows a user to use different | |
| 86 | </I>>><i> >nicknames, as if they are the same nick for services, in case the user | |
| 87 | </I>>><i> >gets an access for a certain nick, they actually get it for the main | |
| 88 | </I>>><i> >nick. | |
| 89 | </I>>><i> > | |
| 90 | </I>>><i> >My suggestion is the expansion of this to nicknames, which are not | |
| 91 | </I>>><i> >linked to their nicknames, in other words, identifying another nickname. | |
| 92 | </I>>><i> > | |
| 93 | </I>>><i> >This way, a user would have the ability to identify a certain nick for a | |
| 94 | </I>>><i> >period (max until signoff), and they would not remain identified to that | |
| 95 | </I>>><i> >nick for all time, since it is not linked. | |
| 96 | </I>>><i> > | |
| 97 | </I>>><i> >This might be used, if a certain nickname is about to be shared by | |
| 98 | </I>>><i> >multiple persons; | |
| 99 | </I>>><i> >- for example identifying to a Bot's nickname, while testing a bot | |
| 100 | </I>>><i> >software | |
| 101 | </I>>><i> >- a shared services operator system; where only few nicknames with | |
| 102 | </I>>><i> >certain OperServ rights exist, and the normal operators identify the | |
| 103 | </I>>><i> >nickname of the services operator. | |
| 104 | </I>>><i> >- Surprise effect: A user, who is also the founder of a channel, is | |
| 105 | </I>>><i> >willing to chat without being continously identified as the founder, and | |
| 106 | </I>>><i> >is willing to detect if the operators are "nice" to normal users, and | |
| 107 | </I>>><i> >chats with them, and then wants to remove their access, and does this by | |
| 108 | </I>>><i> >identifying to the founders nickname and issuing access del... | |
| 109 | </I>>><i> > | |
| 110 | </I>>><i> >Among this feature, the following commands look reasonable: | |
| 111 | </I>>><i> >NS IDENTIFY password [nickname] | |
| 112 | </I>>><i> >NS UNIDENTIFY nickname | |
| 113 | </I>>><i> >CS WHY #channel nickname | |
| 114 | </I>>><i> > | |
| 115 | </I>>><i> >The last command would show information like | |
| 116 | </I>>><i> >-is operator on #channel, because identified to blah's nickname | |
| 117 | </I>>><i> >-is voiced on #channel, because autovoice level is 0 | |
| 118 | </I>>><i> >-is halfopped on #channel, because using a identified to their own | |
| 119 | </I>>><i> >nickname | |
| 120 | </I>>><i> >-is not on #channel | |
| 121 | </I>>><i> >-is not opped on #channel, because the nickname is not identified | |
| 122 | </I>>><i> >-is not opped on #channel, because the nickname is not registered | |
| 123 | </I>>><i> > | |
| 124 | </I>>><i> >I am not insisting that this feature must be implemented, I am just | |
| 125 | </I>>><i> >interested in the possible replies. | |
| 126 | </I>>><i> > | |
| 127 | </I>>><i> >Best regards; | |
| 128 | </I>>><i> >yusuf | |
| 129 | </I>>><i> > | |
| 130 | </I>>><i> >-- | |
| 131 | </I>>><i> >------------------------------------------------------------------ | |
| 132 | </I>>><i> >| Yusuf Iskenderoglu | You get to meet all sorts, | | |
| 133 | </I>>><i> >| eMail - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at stud.uni-karlsruhe.de</A>| in this line of work... | | |
| 134 | </I>>><i> >| eMail - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">s_iskend at ira.uka.de</A> | | | |
| 135 | </I>>><i> >| ICQ UIN : 20587464 \ TimeMr14C | | | |
| 136 | </I>>><i> >------------------------------------------------------------------ | |
| 137 | </I>>><i> > | |
| 138 | </I>>><i> >------------------------------------------------------------------ | |
| 139 | </I>>><i> >To unsubscribe or change your subscription options, visit: | |
| 140 | </I>>><i> ><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
| 141 | </I>>><i> ------------------------------------------------------------------ | |
| 142 | </I>>><i> To unsubscribe or change your subscription options, visit: | |
| 143 | </I>>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
| 144 | </I>><i>-- | |
| 145 | </I>><i>------------------------------------------------------------------ | |
| 146 | </I>>|<i> Yusuf Iskenderoglu | You get to meet all sorts, | | |
| 147 | </I>>|<i> eMail - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at stud.uni-karlsruhe.de</A>| in this line of work... | | |
| 148 | </I>>|<i> eMail - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">s_iskend at ira.uka.de</A> | | | |
| 149 | </I>>|<i> ICQ UIN : 20587464 \ TimeMr14C | | | |
| 150 | </I>><i>------------------------------------------------------------------ | |
| 151 | </I>><i> | |
| 152 | </I>><i>------------------------------------------------------------------ | |
| 153 | </I>><i>To unsubscribe or change your subscription options, visit: | |
| 154 | </I>><i><A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices</A> | |
| 155 | </I></PRE> | |
| 156 | ||
| 157 | <!--endarticle--> | |
| 158 | <HR> | |
| 159 | <P><UL> | |
| 160 | <!--threads--> | |
| 161 | <LI>Previous message: <A HREF="003860.html">[IRCServices] Feature Suggestion | |
| 162 | </A></li> | |
| 163 | <LI>Next message: <A HREF="003862.html">[IRCServices] Suggestion | |
| 164 | </A></li> | |
| 165 | <LI> <B>Messages sorted by:</B> | |
| 166 | <a href="date.html#3861">[ date ]</a> | |
| 167 | <a href="thread.html#3861">[ thread ]</a> | |
| 168 | <a href="subject.html#3861">[ subject ]</a> | |
| 169 | <a href="author.html#3861">[ author ]</a> | |
| 170 | </LI> | |
| 171 | </UL> | |
| 172 | ||
| 173 | </body></html> |