1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] Merging...
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Merging...&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=
"003611.html">
11 <LINK REL=
"Next" HREF=
"003614.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] Merging...
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Merging...&In-Reply-To="
17 TITLE=
"[IRCServices] Merging...">arathorn at theonering.net
19 <I>Tue Feb
25 17:
07:
31 PST
2003</I>
21 <LI>Previous message:
<A HREF=
"003611.html">[IRCServices] Merging...
23 <LI>Next message:
<A HREF=
"003614.html">[IRCServices] Merging...
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#3613">[ date ]
</a>
27 <a href=
"thread.html#3613">[ thread ]
</a>
28 <a href=
"subject.html#3613">[ subject ]
</a>
29 <a href=
"author.html#3613">[ author ]
</a>
34 <PRE>Andrew Church wrote:
36 ><i> >When I upgraded to v5, a strategic temporary addition of email=
0; to
37 </I>><i> >modules/database/version4.c served to perform the same operation.
39 ><i> >we then found a somewhat undesired sideeffect - namely that because in v4
40 </I>><i> >days, NSDefHideEmail had been commented out - old registered users
42 ><i> >onto v5 were duly forced to enter valid e-mail addresses - **which were
44 ><i> >visible for the whole world to see on a /msg nickserv info Nickname.**
46 </I>><i> Seeing as this can be easily changed with a /ns set hide email on
47 </I>><i> immediately after identify -
> set email -
> auth, and unauthed addresses
48 </I>><i> aren't visible to normal users, I don't see this as a problem.
50 My concern is that your average clueless user isn't going to know to /ns set
51 hide email on - even if they're told to do it in bright red letters. My
52 experience in talking registered users through /ns set email and /ns auth
53 has been bad enough - and those are steps that the system corralled them
54 through - whereas there's no way to obviously force them to /ns set hide
57 And thus depending on the previous v4 config, there's a
50/
50 chance that
58 their mail might be left open in the public gaze, ripe for harvesting. It
59 just seems to be putting the users through a bit more trauma than is
60 strictly necessary. Of course, it could be that my users tend to be more
61 clueless than the average network's - but I'd feel slightly worried about
62 leaving their e-mail privacy in their own hands ;)
68 ________________________________________________________________
69 Matthew Hodgson
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">arathorn at theonering.net
</A> Tel: +
44 7968 722968
70 Arathorn: Co-Sysadmin, TheOneRing.net
®
79 <LI>Previous message:
<A HREF=
"003611.html">[IRCServices] Merging...
81 <LI>Next message:
<A HREF=
"003614.html">[IRCServices] Merging...
83 <LI> <B>Messages sorted by:
</B>
84 <a href=
"date.html#3613">[ date ]
</a>
85 <a href=
"thread.html#3613">[ thread ]
</a>
86 <a href=
"subject.html#3613">[ subject ]
</a>
87 <a href=
"author.html#3613">[ author ]
</a>