OK this thread is making user mode +d and channel mode +d confusing,
since they are 2 very separate modes that do very different things.
Following the differences:
User mode +d stops channel text going to the user
Channel mode +D stop JOINs being seen (initially)
A service bot that is user mode +d will always still see JOINs from a
channel with mode +D set
A general user that is user mode +d on the other hand wont see the
JOIN's from a channel with mode +D set (initially)
As for channel mode +d that is an interim mode for when +D is
removed, JOINs will be seen by a general user
I see where Progs intended to go with this...
His first question is what happens to a general user that is user
mode +d when another user that is "delayed" speaks
Supposedly I guess they should still see the JOIN triggered by the
"delayed" user speaking, but not the user speaking, this detail only
needs to be handled by the user mode +d users server.
On 28/10/2005, at 05:12, Progs wrote:
But if a service want to know who is delayed or not, and if it is
+d, it can't.
As for this comment, Progs is correct, because the service bot that
is user mode +d gets all JOINs regardless of channel mode +D, and no
channel chat, a service bot's ability to know the difference becomes
limited, certainly workable on a +m channel (since a +m channel would
make only channel modes and kicking the only possible activation
point, allowing the service bot to track "delayed" users since it
sees everyone regardless).
In short the service bot would have to be user mode -d so that it can
then track the difference on a -m channel.
Which then leaves the question, why would anyone want a service bot
to know the difference between a "delayed" user, and a "fully joined"
user?
One possible thought might be to have the service bot to "force" all
"delayed" users to be joined when the channel is set -D (ie kill the
use of channel mode +d by means of a mode change or kick on those
users still "delayed")
Progs as far as I am aware a service bot can be set user mode -d, not
that it is recommended, since on a large network like Undernet this
is not a good idea (the service bot would probably get flooded).
My 2 cents turned into 20 cents, sorry. Hope this helps ;)
--
[EMAIL PROTECTED]
--
CAUTION: This communication is confidential and may be legally privileged.
If you have received it in error you must not use, disclose, copy or retain
it. Please immediately notify us by return email and then delete the email.
This message has been scanned for viruses and dangerous content by
MailScanner with McAfee UVScan, and is believed to be clean.
_______________________________________________
Coder-com mailing list
Coder-com@undernet.org
http://undernet.sbg.org/mailman/listinfo/coder-com
