headers
Cameron Kaiser | 7 May 2005 03:43
Favicon

updates to the public gopher proxy

The public gopher<->HTTP proxy at http://gopher.floodgap.com/gopher/ has been
updated. In particular, there is now a smarter parser that can recognize and
accomodate ASCII art, a few stupid bugs in the HTML generator were fixed, and
it now reports version numbers for your reference and my amusement.

There are also a few things afoot on the gopher server. I'm almost ready to
release Veronica-2 again to crawl, as well as a few fun things, and a project
I think will help gopher's general usefulness. Stay tuned.

--

-- 
---------------------------------- personal: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Floodgap Systems Ltd * So. Calif., USA * ckaiser@...
-- Never say never again. -----------------------------------------------------
Permalink | Reply | 1 comment |
headers
Alessandro Selli | 7 May 2005 06:48
Favicon

Re: updates to the public gopher proxy

Cameron Kaiser wrote:
> The public gopher<->HTTP proxy at http://gopher.floodgap.com/gopher/ has been
> updated. In particular, there is now a smarter parser that can recognize and
> accomodate ASCII art,

   Cool!

> a few stupid bugs in the HTML generator were fixed, and
> it now reports version numbers for your reference and my amusement.
>
> There are also a few things afoot on the gopher server. I'm almost ready to
> release Veronica-2 again to crawl, as well as a few fun things, and a project
> I think will help gopher's general usefulness. Stay tuned.

   Why make us anxious?  What's that about?

--

-- 
Alessandro Selli
Tel: 340.839.73.05
http://alessandro.route-add.net
Permalink | Reply | 0 comments |
headers
brian | 29 May 2005 21:36

Gopher block!

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.
(Continue reading)

Permalink | Reply | 6 comments |
headers
brian | 29 May 2005 22:30

CompressedFileHandler error

Testing the CompressedFileHandler functionality...I'm running in a
chroot'd environment, have the appropriate lib/bin dirs in
/var/gopher for gzip to work.  This is the stack trace I get when I
try to access a gzip'd file:

  File "/usr/lib/python2.4/site-packages/pygopherd/initialization.py",
line 82, in handle
  File "/usr/lib/python2.4/site-packages/pygopherd/protocols/base.py",
line 89, in handle
  File "/usr/lib/python2.4/site-packages/pygopherd/handlers/file.py",
line 87, in write
AttributeError: CompressedFileHandler instance has no attribute
'rfile'

I'm afraid Perl is my poison, so most of this Python stuff looks very
strange to me!

  --Brian
Permalink | Reply | 1 comment |
headers
brian | 29 May 2005 22:55

Getting links to work

Any trick to getting Links to work?  I'm assuming the UMNDirHandler is
implemented, since I can get .cap and .abstract files parsed.  But
nothing I do with other dotted files (.Links and .names are what I'm
using) seems to work. 

  --Brian
Permalink | Reply | 2 comments |
headers
brian | 29 May 2005 23:38

Re: Getting links to work

Hmm...upon further investigation, it appears that the functionality of
gophermap and .Links is mutually exclusive.  Is this the case? 

  --Brian

On Sun, May 29, 2005 at 03:55:56PM -0500, brian@... wrote:
> Any trick to getting Links to work?  I'm assuming the UMNDirHandler is
> implemented, since I can get .cap and .abstract files parsed.  But
> nothing I do with other dotted files (.Links and .names are what I'm
> using) seems to work. 
> 
>   --Brian
>
Permalink | Reply | 1 comment |
headers
John Goerzen | 30 May 2005 07:13
Favicon

Re: Gopher block!

On Sun, May 29, 2005 at 02:36:12PM -0500, brian@... wrote:
> If this is a dupe, I apologize...I don't believe I posted this the
> first time around from a subscribed e-mail address...

Just so you know, I got this and your other post, but am really busy
with other things right now.  I will send you a reply, but it will
probably happen Tuesday.

Sorry about that.

-- John
Permalink | Reply | 0 comments |
headers
John Goerzen | 30 May 2005 07:11
Favicon

Re: Getting links to work

On Sun, May 29, 2005 at 04:38:09PM -0500, brian@... wrote:
> Hmm...upon further investigation, it appears that the functionality of
> gophermap and .Links is mutually exclusive.  Is this the case? 

Yes, it is.  You can have one or the other in a directory, but not both.
The idea of gophermap is not really compatible with the UMN-style .Links
files.

-- John
Permalink | Reply | 0 comments |

Gmane