1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] ircservices should enforce +R
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20ircservices%20should%20enforce%20%2BR&In-Reply-To=422426DC.6060809%40gmx.at">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"004862.html">
11 <LINK REL=
"Next" HREF=
"004864.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] ircservices should enforce +R
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.esper.net?Subject=%5BIRCServices%5D%20ircservices%20should%20enforce%20%2BR&In-Reply-To=422426DC.6060809%40gmx.at"
17 TITLE=
"[IRCServices] ircservices should enforce +R">lordbergee at comcast.net
19 <I>Tue Mar
1 08:
32:
55 PST
2005</I>
21 <LI>Previous message:
<A HREF=
"004862.html">[IRCServices] ircservices should enforce +R
23 <LI>Next message:
<A HREF=
"004864.html">[IRCServices] ircservices should enforce +R
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#4863">[ date ]
</a>
27 <a href=
"thread.html#4863">[ thread ]
</a>
28 <a href=
"subject.html#4863">[ subject ]
</a>
29 <a href=
"author.html#4863">[ author ]
</a>
34 <PRE> Either I've misunderstood you and Dionisios K. or I think he meant
35 something different from what you're talking about. I think he is
36 suggesting that IRCServices should treat +R like it treats +A or +O.
37 That is to say, right now, if a channel is +O then IRCServices will kick
38 anyone that joins the channel that is not a global IRCop. So what I
39 took his suggestion to mean is that he wants IRCServices to kick the
40 user out of the channel if they don't have a registered nickname and +R
41 is set on the channel.
42 If this is indeed what he is suggesting, then I would say that it might
43 be worth considering. I guess that's useful really in two situations.
44 First if a user is the first one to join a channel and +R is mode locked
45 on, because the IRCd would then not enforce +R because of course the
46 channel did not exist at the time. Secondly I suppose would be on syncs
47 from netsplits where one side did not have +R and say some spam bots
48 managed to get in on on a split server. I guess in general I think it
49 is worth enforcing the mode simply for consistency in IRCServices since
50 +A, +O and +z on Unreal are already enforced.
51 And if this isn't what you meant Dionisios, then I suggest what I
52 thought you meant. What does everyone else on the list think of that? :)
57 ><i> I'd say keep this in user's decision. Since each of the mentioned modes
58 </I>><i> means different settings you should not bind them together. Especially
59 </I>><i> at +AO -since users capable of using those channelmodes (so called opers
60 </I>><i> ;) ) should have sufficient knowledge about irc-stuff to decide by
61 </I>><i> themselves if +R is mandatory or not (on my side I think it's not...)
62 </I>><i> there are several seperate modes invented to produce numerous
63 </I>><i> combinations of settings, just like a users likes it / thinks it's
64 </I>><i> necessary....
66 </I>><i> just my
2 cents...
69 </I>><i> Dionisios K. wrote:
71 </I>>><i> on many ircds +R chmode is supported by now. I thing
72 </I>>><i> services should enforce it on
1st user joins the
73 </I>>><i> channel like +OA and +z on Unrealircd
76 </I>>><i> Dionisios K. - ToXiC On HellenicNet
85 <LI>Previous message:
<A HREF=
"004862.html">[IRCServices] ircservices should enforce +R
87 <LI>Next message:
<A HREF=
"004864.html">[IRCServices] ircservices should enforce +R
89 <LI> <B>Messages sorted by:
</B>
90 <a href=
"date.html#4863">[ date ]
</a>
91 <a href=
"thread.html#4863">[ thread ]
</a>
92 <a href=
"subject.html#4863">[ subject ]
</a>
93 <a href=
"author.html#4863">[ author ]
</a>