[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Anti-collide patch
- To: Michal *pht* Svoboda <svobodam@xxxxxxxxxx>
- Subject: Re: Anti-collide patch
- From: Piotr Kucharski <chopin@xxxxxxxxxx>
- Date: Mon, 11 Jan 1999 02:00:26 +0100
- Cc: ircd-users@xxxxxxx
- Delivered-to: ircd-users-out@irc.org
- Delivered-to: ircd-users@irc.org
- In-reply-to: <Pine.LNX.3.96.990111004748.11685A-100000@eva.vsp.cz>; from Michal *pht* Svoboda on Mon, Jan 11, 1999 at 12:48:54AM +0100
- Mail-followup-to: Michal *pht* Svoboda <svobodam@eva.vsp.cz>, ircd-users@irc.org
- References: <19990111004410.D20186@sgh.waw.pl> <Pine.LNX.3.96.990111004748.11685A-100000@eva.vsp.cz>
On Mon, Jan 11, 1999 at 12:48:54AM +0100, Michal *pht* Svoboda wrote:
> > > maybe i'm totally wrong but if clientA on server A will get collided by
> > > nick change clientC->clientA on server C, and server A will change the
> > > nick of it's clientA to clientC, what should go wrong?
> > It's not clientC->clientA. It's SOMENICK at C killing SOMENICK at A.
> > What do you mean by 'A changing SOMENICK to SOMENICK'?
> nah, i meant nick change collision. server A gets ':clientC NICK clientA'
> from serverC. so it puts ':clientA NICK clientC'. and collision should be
> over..
How would you pass it to servers behind A? They already know clientC and
clientA. There's no such command as 'SWAP NICK1 NICK2'.
Apart from that, with such "feature" in the evening you would leave
channel with Beeth!chopin@jantar, Vesa!ruokonen@umpahpah, Fusion!fusion@tyrell,
syrk!syrk@millennium to see in the morning Beeth!ruokonen@umpahpah,
Vesa!fusion@tyrell, Fusion!syrk@millennium and syrk!chopin@jantar or something
like that. Multiply it by 30000. Havoc, IMHO.
Piotr
ps. answer to list, not me privately