On Sun, 2004-01-18 at 13:26, Jessy Côté wrote:
> What's happen with "muh" and the new version of ircu (.06)? We can't rejoin
> channel when we reconnected to "muh". Something wrong?
Though I have no idea what "muh" is, I would suggest that it does not
properly implement RFC 1459. You should re
Okay, thanks.
At 15:08 04-01-18, you wrote:
Jessy Côté wrote:
What's happen with "muh" and the new version of ircu (.06)? We can't
rejoin channel when we reconnected to "muh". Something wrong?
At a guess, muh's parsing of JOIN messages from the server is broken, talk
to the muh author about the
Jessy Côté wrote:
What's happen with "muh" and the new version of ircu (.06)? We can't
rejoin channel when we reconnected to "muh". Something wrong?
At a guess, muh's parsing of JOIN messages from the server is broken,
talk to the muh author about their broken use of requiring a ":" before
a JO
What's happen with "muh" and the new version of ircu (.06)? We can't rejoin
channel when we reconnected to "muh". Something wrong?
Regards,
LeRebel
--
Ce message Envoi est certifie sans virus connu.
Analyse effectuee par Anti-virus AVG (http://www.grisoft.com).
Version: 7.0.211 / Base de donnees
On Sun, 2004-01-18 at 04:54, Aki Tossavainen wrote:
> > > MODE #channel +b -b *host*
> > > should disregard *host*
The original ircd from which ircu branched, ages and ages ago, had this
peculiar behavior. Although not specified in the RFC, we have opted to,
for now at least, support this non-st
As requested by our dev-team.
On Sat, 17 Jan 2004, Joe Cise wrote:
> On Sat, Jan 17, 2004 at 06:22:02PM +0200, Aki Tossavainen wrote:
> > Here it is:
> >
> > I checked RFC and noticed that if you read the RFC, the MODE line parsing
> > should not include flags that are separated by whitespace:
>
