Received: with LISTAR (v1.0.0; list gopher); Mon, 15 Jan 2001 00:05:50 -0600 (CST) Return-Path: Delivered-To: gopher@complete.org Received: from stockholm.ptloma.edu (stockholm.ptloma.edu [199.106.86.50]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id B6DA63B912 for ; Mon, 15 Jan 2001 00:05:47 -0600 (CST) Received: (from spectre@localhost) by stockholm.ptloma.edu (8.9.1/8.9.1) id WAA11358 for gopher@complete.org; Sun, 14 Jan 2001 22:03:56 -0800 From: Cameron Kaiser Message-Id: <200101150603.WAA11358@stockholm.ptloma.edu> Subject: [gopher] Re: Gopher "robots.txt" In-Reply-To: <20010115004043.A29080@mothra> from David Allen at "Jan 15, 1 00:40:43 am" To: gopher@complete.org Date: Sun, 14 Jan 2001 22:03:56 -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-archive-position: 101 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: spectre@stockholm.ptloma.edu Precedence: bulk Reply-to: gopher@complete.org X-list: gopher > > Also, this doesn't solve the problem adequately for those *servers* > > which are not gopher+ compliant, or certain subsets of indexed search > > servers that can't or don't make gopher+ compliant responses (I can think > > of several immediately). > Hm. Well, I can agree with this, but at the same time, what is to > become of gopher+? You can either merge it with the original gopher > and say "this is what gopher is, and we'll write software > accordingly", or you can throw out gopher+ and stick only with gopher, > but having gopher+ sitting around as something that might be supported > and might not be seems like a pain. Gopher+ has some decent > abilities, and I don't see why you shouldn't use them in this > situation. So maybe we should be asking if gopher+ is something that > should continue to be sometimes-supported, or if it should be taken in > or thrown out. Let's stick with the smaller issue first :-) I think Emanuel's idea is great for encoding that information in Gopher+ attributes; it just seems to leave non-G+ servers out and those aren't just going to disappear. If people want an official stopgap-only solution, fine -- I just need to know what the bot should support that will work for the widest range of servers *now*, since I need to get it running again soon. -- ----------------------------- personal page: http://www.armory.com/~spectre/ -- Cameron Kaiser, Point Loma Nazarene University * ckaiser@stockholm.ptloma.edu -- Really???? WOW!!!!! I'm shallow TOO!!!!! -----------------------------------