1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> AW: [IRCServices Coding]
5.0a33
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%20Coding%5D%205.0a33&In-Reply-To=00ab01c1fe2c%24b8ff9be0%240300000a%40asi200">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"000702.html">
11 <LINK REL=
"Next" HREF=
"000703.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>AW: [IRCServices Coding]
5.0a33
</H1>
15 <B>Yusuf Iskenderoglu
</B>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%20Coding%5D%205.0a33&In-Reply-To=00ab01c1fe2c%24b8ff9be0%240300000a%40asi200"
17 TITLE=
"AW: [IRCServices Coding] 5.0a33">uhc0 at rz.uni-karlsruhe.de
19 <I>Sat May
18 06:
54:
12 PDT
2002</I>
21 <LI>Previous message:
<A HREF=
"000702.html">[IRCServices Coding]
5.0a33
23 <LI>Next message:
<A HREF=
"000703.html">[IRCServices Coding] Two Suggestions
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#712">[ date ]
</a>
27 <a href=
"thread.html#712">[ thread ]
</a>
28 <a href=
"subject.html#712">[ subject ]
</a>
29 <a href=
"author.html#712">[ author ]
</a>
38 ><i> 1) Upon registering a nickname that has not been completly
39 </I>><i> AUTH'd, your
40 </I>><i> email address shows up in a /ns INFO report. At this point,
41 </I>><i> you cannot set
42 </I>><i> HIDE email on. Possibly a privacy issue.
44 In the example-modules.conf you will see:
46 # Sets the default options for newly registered nicks. Note
48 # changing these options will have no effect on nicks which are
49 # already registered. Options not listed here will be unset on
53 # If both NSDefKill and NSDefKillQuick are given, NSDefKillQuick
54 # takes precedence. KILL IMMED cannot be specified as a
66 Where you can set NSDefHideEmail, and newly registered nicknames will
67 have hidden email addresses. So your case does not really exist, and
68 there is no privacy issue with it ;-)
70 ><i> 2) I would have a
"NSIsOp
",
"CSIsOp
" etc. to say whether or
71 </I>><i> not you want
72 </I>><i> services' pseudo-clients to have the +o flag after
73 </I>><i> registration. Maybe I'm
74 </I>><i> just nitpicking, i'd rather not see robots in /who
0 o.
76 Question: After which registration ?
77 Information: Some commands services clients generate, can get rejected
79 the server, if these do not have operator flags. Example:
80 If OperServ were not +o, you could not KILL noone.
81 This does not necessarily apply to U:Line capable servers, though.
94 <LI>Previous message:
<A HREF=
"000702.html">[IRCServices Coding]
5.0a33
96 <LI>Next message:
<A HREF=
"000703.html">[IRCServices Coding] Two Suggestions
98 <LI> <B>Messages sorted by:
</B>
99 <a href=
"date.html#712">[ date ]
</a>
100 <a href=
"thread.html#712">[ thread ]
</a>
101 <a href=
"subject.html#712">[ subject ]
</a>
102 <a href=
"author.html#712">[ author ]
</a>