Re: [Coder-com] Problem with delayed

2005-10-31 Thread Andrew Miller
Michael Poole wrote: >Andrew Miller writes: > > > >>Progs wrote: >> >> >> >>>Hi, >>> >>>If I have two servers, AA and AB, with A and ABAAA on #foo, a +D channel. >>>A is delayed on #foo and ABAAA is +d. >>>There are only A and ABAAA in #foo. >>>When A speaks on #foo, ABAAA is

Re: [Coder-com] Problem with delayed

2005-10-30 Thread Michael Poole
Aaron Kaufman writes: > It's probably bad form to explain on an open list how to use a bug to map > out the network... : ) There is [EMAIL PROTECTED] if one is so inclined. When one thinks there is a bug, it is generally useful to convince at least one of the maintainers that the behavior in que

RE: [Coder-com] Problem with delayed

2005-10-30 Thread Aaron Kaufman
r-com] Problem with delayed Andrew Miller writes: > Progs wrote: > >>Hi, >> >>If I have two servers, AA and AB, with A and ABAAA on #foo, a +D channel. >>A is delayed on #foo and ABAAA is +d. >>There are only A and ABAAA in #foo. >>When A sp

Re: [Coder-com] Problem with delayed

2005-10-30 Thread Michael Poole
Andrew Miller writes: > Progs wrote: > >>Hi, >> >>If I have two servers, AA and AB, with A and ABAAA on #foo, a +D channel. >>A is delayed on #foo and ABAAA is +d. >>There are only A and ABAAA in #foo. >>When A speaks on #foo, ABAAA is +d so AB doesn't receive message, so >>ABAAA

Re: [Coder-com] Problem with delayed

2005-10-28 Thread Richard
you missed one... how about processing the channels +D/+d state on a channel message before processing a users Deaf mode status? after all, it only needs to do this to decide if it needs to send a join to a Deaf user. personally I like the idea that a Deaf user would see all joins regardl

Re: [Coder-com] Problem with delayed

2005-10-28 Thread Wouter Coekaerts
On Friday 28 October 2005 14:40, Andrew Miller wrote: > Progs wrote: > >If I have two servers, AA and AB, with A and ABAAA on #foo, a +D > > channel. A is delayed on #foo and ABAAA is +d. > >There are only A and ABAAA in #foo. > >When A speaks on #foo, ABAAA is +d so AB doesn't rece

Re: [Coder-com] Problem with delayed

2005-10-28 Thread Joseph Bongaarts
Original Message > On Sat, 29 Oct 2005 01:40:56 +1300 > Andrew Miller <[EMAIL PROTECTED]> wrote: > > Fix B: Deaf users can't join +D or +d channels, and users in +D or + d > > channels can't become deaf. > > It's a bad solution. What about services ? > +d-k users should not

Re: [Coder-com] Problem with delayed

2005-10-28 Thread Andrew Miller
Progs wrote: >On Sat, 29 Oct 2005 01:40:56 +1300 >Andrew Miller <[EMAIL PROTECTED]> wrote: > > >>There are several fixes: >>Fix A: We need to globally synchronise delayed state, which means that >>we need to transmit it in BURST. We can then apply the "don't propagate >>WASDELAYED" because we ca

Re: [Coder-com] Problem with delayed

2005-10-28 Thread Andrew Miller
Andrew Miller wrote: >Progs wrote: > > > >>Hi, >> >>If I have two servers, AA and AB, with A and ABAAA on #foo, a +D channel. >>A is delayed on #foo and ABAAA is +d. >>There are only A and ABAAA in #foo. >>When A speaks on #foo, ABAAA is +d so AB doesn't receive message, so >>AB

Re: [Coder-com] Problem with delayed

2005-10-28 Thread Progs
On Sat, 29 Oct 2005 01:40:56 +1300 Andrew Miller <[EMAIL PROTECTED]> wrote: > > There are several fixes: > Fix A: We need to globally synchronise delayed state, which means that > we need to transmit it in BURST. We can then apply the "don't propagate > WASDELAYED" because we can track delayed sta

Re: [Coder-com] Problem with delayed

2005-10-28 Thread Andrew Miller
Progs wrote: >Hi, > >If I have two servers, AA and AB, with A and ABAAA on #foo, a +D channel. >A is delayed on #foo and ABAAA is +d. >There are only A and ABAAA in #foo. >When A speaks on #foo, ABAAA is +d so AB doesn't receive message, so ABAAA >doesn't see A's join. > >Bug

Re: [Coder-com] Problem with delayed

2005-10-27 Thread Richard
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 m

Re: [Coder-com] Problem with delayed

2005-10-27 Thread Progs
But if a service want to know who is delayed or not, and if it is +d, it can't. On Thu, 27 Oct 2005 18:04:29 +0200 Carlo Wood <[EMAIL PROTECTED]> wrote: > On Thu, Oct 27, 2005 at 04:16:52PM +0200, Progs wrote: > > If I have two servers, AA and AB, with A and ABAAA on #foo, a +D > > channel.

Re: [Coder-com] Problem with delayed

2005-10-27 Thread Carlo Wood
On Thu, Oct 27, 2005 at 04:16:52PM +0200, Progs wrote: > If I have two servers, AA and AB, with A and ABAAA on #foo, a +D channel. > A is delayed on #foo and ABAAA is +d. There is no such thing as being 'delayed'. In order to know where to send messages, the JOIN is propagated to all serve

Re: [Coder-com] Problem with delayed

2005-10-27 Thread Wouter Coekaerts
On Thursday 27 October 2005 16:16, Progs wrote: > If I have two servers, AA and AB, with A and ABAAA on #foo, a +D > channel. A is delayed on #foo and ABAAA is +d. > There are only A and ABAAA in #foo. > When A speaks on #foo, ABAAA is +d so AB doesn't receive message, so > ABAAA do

Re: [Coder-com] Problem with delayed

2005-10-27 Thread Progs
And with two servers, AA and AB, with A and ABAAA, and #foo a +D channel. There is only A on #foo and he is *not* delayed. When ABAAA join channel, he sees A as a delayed user. Is it correct ? Progs. On Thu, 27 Oct 2005 16:16:52 +0200 Progs <[EMAIL PROTECTED]> wrote: > Hi, > > If I

[Coder-com] Problem with delayed

2005-10-27 Thread Progs
Hi, If I have two servers, AA and AB, with A and ABAAA on #foo, a +D channel. A is delayed on #foo and ABAAA is +d. There are only A and ABAAA in #foo. When A speaks on #foo, ABAAA is +d so AB doesn't receive message, so ABAAA doesn't see A's join. Bug or feature ?:) Progs.