presentation you like. You get another thing you don't get in the Web -- not only do you not know when you leave a site, but you don't care. I've never actually used GopherVR or the "futuristic console" stuff, so I'll skip commenting on those... > left with a well organized page (anyone who has used Lynx on standard > web pages may attest to how disorganized the flow becomes upon removal > of tables and other such things). I need to review Gopher+ some more and see just how extensible we can make it. It may be possible to add some gopher+ attributes. > Something else that I would like to see is the conversion of some > http+html pages into gophers. This is of course more difficult then the It may not be as difficult as you think in some ways, and more difficult in others. You can use a tool like Pavuk to download entire sites. UMN gopherd can peek inside HTML files and use the for the menu entry. So there's most of your navigation. The problem is links. You can't just say <IMG SRC="foo.jpg"> in gopherspace, because, for instance, if you're at: gopher://foo.com/hindex.html You'll get: gopher://foo.com/hfoo.jpg Which says it's a HTML file. One very useful addition would be to communicate the type of a file when it is requested rather than only in the directory. However, this would mean a fundamental and incompatible change to the protocol. > you literally add order to the chaos. I am not really sure what this > will acheive, but I am both stubborn and insane. As a test case I might What a combination :-) > interesting venture could be to translate mathworld.wolfram.com, > although I am not sure why. Perhaps even Slashdot lite could be made > into a gopher <g> Gopher would be a natural way to represent something like Slashdot, I think. In fact, you can probably find my musings on a Gopher-to-NNTP gateway around somewhere, and the UMN source tree even includes an old one written in Perl. > much. I was also a bit surprised to find a really good file about > Aikido, which would normally have been lost in the crowds of the web. I This is one of my favorite things to do -- surfing gopherspace. It seems that just "surfing the web" is not really possible anymore. I always use it for answering a particular question these days, not just general curiosity. > lack of gopher+ support. And it is in perl, which is just groovy. As I > have seen several comments about problems with gopherd, which of these > servers do people think should be focused on? I am now trying to figure Personally, I think we need a gopherd written in Python, and I aim to do that one of these days. (Really!) UMN gopherd is probably the most full-featured we have at the moment. It also has some various kinds of cruft in it. Caveat emptor, I guess. > "Admittedly, Web servers and hypertext editors are scarce; but > the potential here makes the World-Wide Web one of the most interesting > new tools on the Internet." > Oh how the tables have turned. Nice! > PS: has this list replaced comp.infosystems.gopher? Technically, both are alive; however, there is much more traffic in the list than on the newsgroup. > Enough of this, I am pressing send; no turning back now! Thanks! -- John