Received: with ECARTIS (v1.0.0; list gopher); Wed, 16 Jan 2008 14:36:30 -0600 (CST) Received: from floodgap.com ([66.159.214.137] ident=elvis) by glockenspiel.complete.org with esmtp (Exim 4.63) id 1JFEzs-0006Nz-BE for gopher@complete.org; Wed, 16 Jan 2008 14:36:30 -0600 Received: (from spectre@localhost) by floodgap.com (6.6.6.666.1/2007.10.21) id m0GKaQne019854 for gopher@complete.org; Wed, 16 Jan 2008 12:36:26 -0800 From: Cameron Kaiser <spectre@floodgap.com> Message-Id: <200801162036.m0GKaQne019854@floodgap.com> Subject: [gopher] Re: Strategy: end of Gopher in Mozilla In-Reply-To: <20080116202537.GA29738@pongonova.net> from "brian@pongonova.net" at "Jan 16, 8 02:25:37 pm" To: gopher@complete.org Date: Wed, 16 Jan 2008 12:36:26 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-Spam-Status: No (score 0.0): AWL=0.004 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Wed, 16 Jan 2008 14:36:30 -0600 X-archive-position: 1798 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: spectre@floodgap.com Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-Id: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

> > Other comments? > > I'm going to continue working and enhancing the WikkaGopher proxy > (http://www.wikkawiki.org/WikkaGopher). Wikka has a strong userbase > among the more savvy wiki users (the ones who realize MediaWiki and > the like are quite overbloated and heavyweight), and the idea of an > easily-installed proxy module might appeal to some wiki operators and > encourage others to set up gopher proxies.

That sounds awesome. If you get any public proxies together, we should be collecting this.

Incidentally, the rbfh.de host I was concerned about is actually itself a proxy, too -- that was where the activity was coming from (web robots mistakenly crawling it). All is fixed, but more germane to this discussion, we have at least two public proxies I know of and I'm sure there are others.

> I think a multi-targeted approach (standalone clients, FF plug-ins, > proxies, etc.) is the best approach and utilizes the greatest amount > of leverage within the gopher talent pool.

That's exactly where I'm at too. It's just making sure that we have a measured approach for transition rather than a haphazard lurch.

Btw, writing a Mozilla *extension* (not a Core element) for continuing gopher:// support is turning out to be easier than I had surmised. I already have some rudimentary code together just hacking a bit during the morning. It is very primitive, but some things are already working.

Before people ask why I didn't do *that* for 388195, the reason is simple: if we could keep it in Core without having to require people get a plugin, that would have been better. But since we're condemned to plugins for FF4, might as well enjoy it.

-- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com -- BOND THEME NOW PLAYING: "The Living Daylights" -----------------------------