Received: with ECARTIS (v1.0.0; list gopher); Sun, 29 May 2005 15:36:09 -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 1DcUW0-0004VV-Lc for gopher@complete.org; Sun, 29 May 2005 15:36:09 -0500 Received: by turquoise.pongonova.net (Postfix, from userid 1000) id 0DE5D644; Sun, 29 May 2005 14:36:13 -0500 (CDT) Date: Sun, 29 May 2005 14:36:12 -0500 From: brian@pongonova.net To: gopher@complete.org Subject: [gopher] Gopher block! Message-ID: <20050529193612.GL12306@pongonova.net> References: <20050529063117.GA10967@pongonova.net> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050529063117.GA10967@pongonova.net> User-Agent: Mutt/1.4.2.1i X-Spam-Status: No (score 2.0): 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 Sun, 29 May 2005 15:36:09 -0500 Content-Transfer-Encoding: 8bit X-archive-position: 1036 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: <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

If this is a dupe, I apologize...I don't believe I posted this the first time around from a subscribed e-mail address...

====================================================================

OK, I have a gopher server up and running...problem is, I really don't know where to start! Sure, I've read the pygopherd documentation, but I don't have a clear picture of what a typical gopher file looks like (formatting of selectors, layout, etc.).

Would someone be willing to offer up a file or two to help get me started? Once I have a starting point, I'll be good to go. (I've checked out the gophermap example in the pygopherd distro, but I'm looking for a bit more detail...)

BTW, I'm doing this solely for sentimental reasons, and because I can. Alessandro put it quite eloquently in an earlier post, much better than I could ever dream of doing, about a world "that is no more...little or no more of on-line command-line dungeon games, telnet logins, talk sessions, gopher sites..."

Like Alessandro, I too miss the simpler times. I often wonder where technology went wrong when it turned down the path of what I call "prerequisite complexity," something I see quite often in my IT life: The idea that technology requires ever-increasing complexity, whether or not the problem that is being solved actually warrants it.

Many IT "problems" today could be easily solved by using simpler approaches, but for the fact that there is no money to be made in IT unless there is "innovation" to excite company shareholders and VCs. Complexity produces a self-perpetuating IT industry that ensures its continued survival by coming up with advanced technologies that require ever-increasing sums of capital to support these "innovations," capital which is generated by massive marketing machines that convince people to invest in technologies they know absolutely nothing about.

Setting up a gopher server is my insignificant way of protesting the bloat that permeates all that is Internet-related.

--Brian