]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2003/003613.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2003 / 003613.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Merging...
5 </TITLE>
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">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Merging...</H1>
15 <B>Arathorn</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Merging...&In-Reply-To="
17 TITLE="[IRCServices] Merging...">arathorn at theonering.net
18 </A><BR>
19 <I>Tue Feb 25 17:07:31 PST 2003</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="003611.html">[IRCServices] Merging...
22 </A></li>
23 <LI>Next message: <A HREF="003614.html">[IRCServices] Merging...
24 </A></li>
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>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE>Andrew Church wrote:
35
36 &gt;<i> &gt;When I upgraded to v5, a strategic temporary addition of email=0; to
37 </I>&gt;<i> &gt;modules/database/version4.c served to perform the same operation.
38 </I>However,
39 &gt;<i> &gt;we then found a somewhat undesired sideeffect - namely that because in v4
40 </I>&gt;<i> &gt;days, NSDefHideEmail had been commented out - old registered users
41 </I>migrating
42 &gt;<i> &gt;onto v5 were duly forced to enter valid e-mail addresses - **which were
43 </I>then
44 &gt;<i> &gt;visible for the whole world to see on a /msg nickserv info Nickname.**
45 </I>&gt;<i>
46 </I>&gt;<i> Seeing as this can be easily changed with a /ns set hide email on
47 </I>&gt;<i> immediately after identify -&gt; set email -&gt; auth, and unauthed addresses
48 </I>&gt;<i> aren't visible to normal users, I don't see this as a problem.
49 </I>
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
55 email.
56
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 ;)
63
64 my 2p, anyway
65
66 A.
67
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&#174;
71
72
73 </PRE>
74
75 <!--endarticle-->
76 <HR>
77 <P><UL>
78 <!--threads-->
79 <LI>Previous message: <A HREF="003611.html">[IRCServices] Merging...
80 </A></li>
81 <LI>Next message: <A HREF="003614.html">[IRCServices] Merging...
82 </A></li>
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>
88 </LI>
89 </UL>
90
91 </body></html>