Received: with ECARTIS (v1.0.0; list gopher); Fri, 25 Jan 2008 07:53:20 -0600 (CST) Received: from wa-out-1112.google.com ([209.85.146.183]) by glockenspiel.complete.org with esmtp (Exim 4.63) id 1JIOzd-0002MM-H0 for gopher@complete.org; Fri, 25 Jan 2008 07:53:20 -0600 Received: by wa-out-1112.google.com with SMTP id l35so1074985waf.12 for <gopher@complete.org>; Fri, 25 Jan 2008 05:53:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=KTMI4MPbYfPlIFTibeFLrBnERjT5rS7QgCeihBt/G5U=; b=VsC6eQb1PHf1OZQRY+6/HjKAEAaC/WD/rTkXvJLlrUZ/k6CJHmobBK1/F7fHfEQ7H7mD0KGfNuQe9pUsI/4iDSciYupcr0oWhUDUFwoWufX2mAQgWaya0Yu/GVDUKBGhBnsqqaCwb2g4s/KILT28X0qd5S443UyU9dAZefC5ZD0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=wATuagKztfW6ZbUEl50PKB41B0ARlKwQXR776+0Mn0dpWAXbBGFOlymMEmVMwy8usZABAEe2a6i+JXo8nPaZxghOzsYf4YXWS7THgRTa8TDMIM3hz3iE2fK4Li2mjYczOjMWJUA7Yu+nPQfu5xph8V9bdTNz5GD1fRsJuAxqU10= Received: by 10.114.78.1 with SMTP id a1mr2351468wab.14.1201269194382; Fri, 25 Jan 2008 05:53:14 -0800 (PST) Received: by 10.114.134.8 with HTTP; Fri, 25 Jan 2008 05:53:14 -0800 (PST) Message-ID: <2a1386f80801250553i266b4fcau90f765fbd5b34d92@mail.gmail.com> Date: Fri, 25 Jan 2008 08:53:14 -0500 From: "Hugh Guiney" <hugh.guiney@gmail.com> To: gopher@complete.org Subject: [gopher] Re: Strategy: end of Gopher in Mozilla In-Reply-To: <200801160035.m0G0ZKkr011202@floodgap.com> MIME-Version: 1.0 Content-type: text/plain References: <200801160035.m0G0ZKkr011202@floodgap.com> X-Spam-Status: No (score 0.5): AWL=-0.472, HTML_10_20=0.945, HTML_MESSAGE=0.001 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Fri, 25 Jan 2008 07:53:20 -0600 Content-Transfer-Encoding: 8bit X-archive-position: 1816 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: hugh.guiney@gmail.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

Okay, so I'm not exactly current on these developments (last I heard this was still just a "bug" in the process of being "addressed") but am I correct in assuming that Gopher is out on only *official* Mozilla releases? If so, are [Moz-hosted] offshoots like SeaMonkey—which is supposed to be less memory-intensive and more feature-rich out-of-the-box than Firefox anyway—a viable option? It's a little obscure, but probably a lot less so than an entirely new client would be (not that I'm opposed to that idea, as it's a project I myself have wanted to undertake at some point in the future). I have no idea how the Moz dev community operates, but if it's a separate codebase/more niche-appreciative crowd, maybe Gopher support would fair better there. Just a thought.

On Jan 15, 2008 7:35 PM, Cameron Kaiser <spectre@floodgap.com> wrote:

> Brandon Eich has spoken on 388195 and has stated that gopher will > disappear > in Mozilla 2, which means Firefox 3 will be the final version with gopher > support. (And what a jerk he is. Wow. Did you read his comments on SOAP?) > This is a crushing blow. > > At this point strategy needs to be discussed to have a workable, > deployable > modern client in place for when FF 3 becomes EOLed in a couple years. > > As I see it, we have two options: > > - FF add-on. This has the advantages of integration, but we have to play > in their sandbox, including dumbing down features that don't work well in > a browser environment. However, a lot of work is done for us, and it is > cross-platform. We would need someone/ a team with good knowledge of how > to do this. > > - Separate application. Either via Mozilla Prism or Adobe AIR, or even a > cross-platform system like RealBASIC, as far as I'm concerned they'd still > have to download something, but at least this way it's a product custom > scoped for Gopher and can do things in a Gopher-like way. Downside is > reinventing the UI wheel, but that may not be completely bad. > > - Custom clients for various deployments. This means mastery on a > particular > platform, but may be limiting due to fractured development cycles. > > As far as I'm concerned, with pulling Gopher out of core, there is no > reason not to take our ball and play elsewhere, i.e., create a next-gen > Gopher client and leave Firefox/Mozilla out of the equation. However, I > can see advantages to either way, and neither option is exclusive. > > -- > ------------------------------------ personal: > http://www.cameronkaiser.com/ -- > Cameron Kaiser * Floodgap Systems * www.floodgap.com * > ckaiser@floodgap.com > -- In the end, everything is alright. -- Sarah Goldfarb, "Requiem for a > Dream" > > >