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] NICKSERV suggestion. | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20NICKSERV%20suggestion.&In-Reply-To=43230fb6.66515%40msgid.achurch.org"> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="005026.html"> | |
| 11 | <LINK REL="Next" HREF="005028.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices] NICKSERV suggestion.</H1> | |
| 15 | <B>Bergee</B> | |
| 16 | <A HREF="mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20NICKSERV%20suggestion.&In-Reply-To=43230fb6.66515%40msgid.achurch.org" | |
| 17 | TITLE="[IRCServices] NICKSERV suggestion.">lordbergee at comcast.net | |
| 18 | </A><BR> | |
| 19 | <I>Sat Sep 10 10:53:19 PDT 2005</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="005026.html">[IRCServices] NICKSERV suggestion. | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="005028.html">[IRCServices] NICKSERV suggestion. | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#5027">[ date ]</a> | |
| 27 | <a href="thread.html#5027">[ thread ]</a> | |
| 28 | <a href="subject.html#5027">[ subject ]</a> | |
| 29 | <a href="author.html#5027">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE> Our network runs with LIST and LISTEMAIL restricted to admins only... | |
| 35 | so personally I like LISTLINKS the way that it is. I think you're right | |
| 36 | that someone might not want the fact that they go by several nicknames | |
| 37 | intentionally exposed. | |
| 38 | Although what might be useful is a command to confirm if two nicknames | |
| 39 | are linked. If you have a channel registered, you can already do this | |
| 40 | in a rather roundabout fashion. Let's say that a user has NicknameA, | |
| 41 | NicknameB and NicknameC linked, with the main nickname being NicknameA. | |
| 42 | I (as another regular user) want to know if NicknameB and NicknameC are | |
| 43 | linked. I can just add NicknameB to my channel's access list at some | |
| 44 | level, and then list the access list. ChanServ will then tell me the | |
| 45 | access level of NicknameA, so I can see that NicknameA and NicknameB are | |
| 46 | linked. And then of course, I can tell ChanServ to remove NicknameC | |
| 47 | from the access list (which will of course work, and NicknameA will no | |
| 48 | longer appear.) So then I know that those three nicknames are linked | |
| 49 | together... if that explanation made any sense at all. :) | |
| 50 | I guess after writing that, I feel like maybe it isn't worth trying to | |
| 51 | hide nickname links, since there are ways a determined user can find out | |
| 52 | anyway... | |
| 53 | ||
| 54 | Bergee | |
| 55 | ||
| 56 | Andrew Church wrote: | |
| 57 | >><i>The main thing that makes me wonder is that LIST and LISTEMAIL aren't | |
| 58 | </I>>><i>restricted to staff, so: | |
| 59 | </I>><i> | |
| 60 | </I>><i> But nicks (nickgroups, technically) also have a PRIVATE option, | |
| 61 | </I>><i> allowing them to select whether their nicks are shown in the list or not. | |
| 62 | </I>><i> Linked nicks all share the same flags, so you can't decide whether to allow | |
| 63 | </I>><i> certain links to be shown or not. | |
| 64 | </I>><i> | |
| 65 | </I>><i> Though now that you bring it up, I could see an argument for allowing | |
| 66 | </I>><i> LISTLINKS on a user without PRIVATE set. Comments from the audience? | |
| 67 | </I>><i> | |
| 68 | </I>><i> --Andrew Church | |
| 69 | </I>><i> <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A> | |
| 70 | </I>><i> <A HREF="http://achurch.org/">http://achurch.org/</A> | |
| 71 | </I></PRE> | |
| 72 | ||
| 73 | ||
| 74 | ||
| 75 | <!--endarticle--> | |
| 76 | <HR> | |
| 77 | <P><UL> | |
| 78 | <!--threads--> | |
| 79 | <LI>Previous message: <A HREF="005026.html">[IRCServices] NICKSERV suggestion. | |
| 80 | </A></li> | |
| 81 | <LI>Next message: <A HREF="005028.html">[IRCServices] NICKSERV suggestion. | |
| 82 | </A></li> | |
| 83 | <LI> <B>Messages sorted by:</B> | |
| 84 | <a href="date.html#5027">[ date ]</a> | |
| 85 | <a href="thread.html#5027">[ thread ]</a> | |
| 86 | <a href="subject.html#5027">[ subject ]</a> | |
| 87 | <a href="author.html#5027">[ author ]</a> | |
| 88 | </LI> | |
| 89 | </UL> | |
| 90 | ||
| 91 | </body></html> |