Received: with ECARTIS (v1.0.0; list gopher); Tue, 11 Oct 2005 07:25:25 -0500 (CDT) Received: from c-24-1-225-166.hsd1.tx.comcast.net ([24.1.225.166] helo=turquoise.pongonova.net) by glockenspiel.complete.org with esmtp (Exim 4.50) id 1EPJC3-0007vP-1A for gopher@complete.org; Tue, 11 Oct 2005 07:25:24 -0500 Received: by turquoise.pongonova.net (Postfix, from userid 1000) id 44B5062C; Tue, 11 Oct 2005 06:24:41 -0500 (CDT) Date: Tue, 11 Oct 2005 06:24:41 -0500 From: brian@pongonova.net To: gopher@complete.org Subject: [gopher] Re: New Gopher Releases Message-ID: <20051011112441.GC16152@pongonova.net> References: <20050922162328.GA23428@katherina.lan.complete.org> <20050926183102.GA8536@complete.org> <433860F6.9010800@route-add.net> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1i X-Spam-Status: No (score 2.0): AWL=-0.007, FORGED_RCVD_HELO=0.05, NO_REAL_NAME=0.178, RCVD_IN_NJABL_DUL=1.655, RCVD_IN_SORBS_DUL=0.137 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Tue, 11 Oct 2005 07:25:24 -0500 Content-Transfer-Encoding: 8bit X-archive-position: 1102 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: brian@pongonova.net Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher On Tue, Oct 11, 2005 at 09:41:58AM +0200, Deadsmile wrote: > Also, a question : Why are you using a mailing list instead of > news:comp.infosystems.gopher ? This newsgroup is almost dead, moving > conversations on it should offer a better public access to newbies. > Just a suggestion... Because a mailing list is more convenient? Because folks can choose to archive the list in whatever way makes sense to them? Because most newsgroups aren't worth the time spent to filter through low S/N ratios? Just some of my guesses... Here's a suggestion: Why not post subscription instructions to *this* m/l on the newsgroup? Best of both worlds...