From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 6BB22BC57 for ; Tue, 5 Oct 2010 20:09:37 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAJsGq0xQRFuw/2dsb2JhbACiPnHGF4VHBA X-IronPort-AV: E=Sophos;i="4.57,285,1283724000"; d="scan'208";a="72791146" Received: from furbychan.cocan.org ([80.68.91.176]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/AES256-SHA; 05 Oct 2010 20:09:37 +0200 Received: from rich by furbychan.cocan.org with local (Exim 4.63) (envelope-from ) id 1P3BxF-0001MS-0w; Tue, 05 Oct 2010 19:09:33 +0100 Date: Tue, 5 Oct 2010 19:09:33 +0100 To: Gareth Smith Cc: caml-list@yquem.inria.fr Subject: Re: [Caml-list] Bans in #ocaml IRC channel Message-ID: <20101005180932.GB2150@annexia.org> References: <20101005170625.GA2150@annexia.org> <4CAB664D.5000509@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CAB664D.5000509@gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) From: Richard Jones X-Spam: no; 0.00; ocaml:01 0100,:01 ocaml:01 wrote:01 wrote:01 caml-list:01 fix:05 tue:06 channel:06 channel:06 red:92 i'm:09 although:11 banned:87 i've:12 On Tue, Oct 05, 2010 at 06:54:21PM +0100, Gareth Smith wrote: > On 05/10/10 18:06, Richard Jones wrote: > > [I'm sorry this isn't really the right place to bring this up, but > > since I can't communicate on IRC, there wasn't much alternative] > > > > I've been banned from #ocaml for some time, for no reason that I know > > of. So have some other people. Can whoever did this un-ban me (and > > the others). > > > > 18:03 < rwmjones> [I said something here] > > 18:03 -!- #ocaml Cannot send to channel > > > > Rich. > > > > > It could be that you just need to register with nickserv. Thanks, it turned out this is the case, at least for #ocaml although not for other FreeNode channels. I think we are looking at how to fix this. Rich. -- Richard Jones Red Hat