headers
Michael Casadevall | 1 Jun 2008 06:04
Picon
Favicon

Gopher protocol confusion?

As I work to implement my libgopher, I'm kinda confused on what seems to
be an extension to the gopher protocol by pyGopherd.

Here's the results of talking to gopher://castleinfinity.org and
gopher://gopher.floodgap.com

mcasadevall <at> siren:~/libgopher/build$ telnet gopher.floodgap.com 70
Trying 66.159.214.138...
Connected to helsinki.floodgap.com.
Escape character is '^]'.

iWelcome to Floodgap Systems' official gopher server.       error.host  1
iFloodgap has been serving the gopher community since       error.host  1
i1999 (formerly gopher.ptloma.edu).     error.host  1
i       error.host  1
iWe run Bucktooth 0.2.4 on inetd as our server system.      error.host  1
igopher.floodgap.com is an Apple Power Macintosh 7300 with      error.host  1
ia G3/500 processor and 1GB RAM running NetBSD/macppc.      error.host  1
iSend questions on server maintenance to        error.host  1
i       error.host  1
i        gopher@...        error.host  1
i       error.host  1
0Does this gopher menu look correct?    /gopher/proxy   gopher.floodgap.com 70
i(plus using the Floodgap Public Gopher Proxy)      error.host  1
i       error.host  1
1Getting started with gopher, software, more    /gopher gopher.floodgap.com 70
0Using web browsers in Gopherspace  /gopher/wbgopher    gopher.floodgap.com 70
i(why you shouldn't use Internet Explorer, and other        error.host  1
iuseful tips for gopher newbies)        error.host  1
1Gopher clients for various platforms   /gopher/clients gopher.floodgap.com 70
(Continue reading)

Permalink | Reply | 1 comment |
headers
Cameron Kaiser | 1 Jun 2008 06:13
Favicon

Re: Gopher protocol confusion?

> 1Download Castle Infinity   /Download   castleinfinity.org  70  +
[...]
> What are those freaking +'s. They don't appear in RFC1436 vvv

They indicate that these resources may be accessed as Gopher+. You can
safely ignore them for standard Gopher purposes. That field might also be
overloaded by other markers which other standard Gopher clients also
ignore.

--

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@...
-- In memory of John Banner ---------------------------------------------------
Permalink | Reply | 0 comments |
headers
Dennis Schulmeister | 4 Jun 2008 19:09
Picon

WikiBerd and GopherBerd finaly together

Hi all,
this is to announce the marriage between WikiBerd (my personal wiki
running on my small home server) and GopherBerd (the gopher server I set
up recently on the same machine). Encouraged by Michael Casadevall's
hint to export large databases like Wikipedia to gopher I set out to do
the same for my own wiki.

For that purpose I wrote a small python script which pulls the wiki
pages out of the database in order to transform them into single
HTML-pages and to create a gophermap for better browsing. It also makes
sure that all links between the pages and all image references are kept
in tact so that the whole wiki can be browsed from gopher space alone.

You'll find WikiBerd here. But please note that only a few pages are
available in English language. Many if not most of them are German.
http://ncc-1701a.homelinux.net

This is GopherBerd:
gopher://ncc-1701a.homelinux.net

WikiBerd in gopher space:
gopher://ncc-1701a.homelinux.net/1/WikiBerd

The export script, released under the terms of the GPL:
http://ncc-1701a.homelinux.net/~dennis/WikiBerdGopherExport
gopher://ncc-1701a.homelinux.net/1/dennis/WikiBerdGopherExport

Yours sincerely,
Dennis Schulmeister
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Casadevall | 5 Jun 2008 00:49
Picon
Favicon

Yet another gopher protocol question ...

When dealing with a uuencoded file (type 6), do you treat it as a text
file, changing double periods to signal periods, or do you simply
download it raw similar to binary files?
Michael
Permalink | Reply | 3 comments |
headers
Cameron Kaiser | 5 Jun 2008 01:19
Favicon

Re: Yet another gopher protocol question ...

> When dealing with a uuencoded file (type 6), do you treat it as a text
> file, changing double periods to signal periods, or do you simply
> download it raw similar to binary files?

I'm not sure what you mean by double periods, but I've historically
handled it as text. The 0.2.5 version of Bucktooth which is coming out
will do this raw, but mostly out of expediency. I don't think most clients
care.

--

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@...
-- Maybe this world is another planet's hell. -- Aldous Huxley ----------------
Permalink | Reply | 2 comments |
headers
Michael Casadevall | 5 Jun 2008 01:30
Picon
Favicon

Re: Yet another gopher protocol question ...

According to RFC1436, if the source text file, and it finds a period on
a line by itself, it sends it as .. instead of just . so it doesn't
accidentally end the connection. I can't figure out though if that's the
proper behavior of the client when dealing with uuencoded files.
Michael

On Wed, 2008-06-04 at 16:19 -0700, Cameron Kaiser wrote:
> 
> I'm not sure what you mean by double periods, but I've historically
> handled it as text. The 0.2.5 version of Bucktooth which is coming out
> will do this raw, but mostly out of expediency. I don't think most
> clients
> care.
Permalink | Reply | 0 comments |
headers
Cameron Kaiser | 5 Jun 2008 15:19
Favicon

Unveiling the Overbite Project (and other announcements)

This message is really, really long. Here goes:

** OverbiteFF for Firefox 3: "RTM"

With the release of Firefox 3 RC2, I took the wraps off OverbiteFF. This is
the release version, 1.0-1381. It does have some small changes, including a
bug fix for port access, additional explicit ports and CSS tweaks, so it is a
recommended download if you are still using -1380. We'll see if anyone gets
the joke on the build number. ;-)

You can now preview the Overbite Project pages. There are HTTP and Gopher
versions:

	http://gopher.floodgap.com/overbite/

	gopher://gopher.floodgap.com/1/overbite/

(These are not publicly announced yet, but you can access them.) The
HTTP and Gopher pages are largely drawn from the same data store, so
people will get mostly the same views.

Additional language packs are still being accepted from translators and I
will gladly add them to OverbiteFF 1.1.

** Calling for OverbiteFF skins

If you are or you were making your own skin for OverbiteFF, I would love to
host them. I think this would give people something fun to play with -- I
know Avery wanted some interface changes: Avery, did you come up with something
of your own? The skins folder is here:
(Continue reading)

Permalink | Reply | 5 comments |
headers
Jay | 5 Jun 2008 16:22
Picon

Clients

Hello everyone!
I'm new to the list and currently using Gopherspace to get news and weather
updates without using the WWW, which hinders you a lot with too much ads and
net lag.

I like the projects that are going on and enjoy browsing a lot, Wikipedia on
Gopherspace would be great!

About clients, here is a question for you: I'm currently using the old
HGopher client, which is not bad but does not support long filenames. I know
Firefox supports the gopher protocol, but are there any other clients for
later Windows versions other than WSGopher or HGopher?

Thanks and remember: "The information WANTS to be free". (Bruce Sterling)

--

-- 
- Jay "CoolDragon" Arias-Chavez.
http://www.cooldragon.org (soon to be ported to Gopher this summer).

Gana Jugando... Play and earn:
http://www.cooldragon.biz/
Permalink | Reply | 2 comments |
headers
R.A.Pavlov | 5 Jun 2008 16:36
Picon

Re: Unveiling the Overbite Project (and other announcements)

Cameron, just to be sure, did you receive my email with a screenshot and 
description of the error with displaying links to files in Russian 
version which seems to be some unicode rendering problem? It's the same 
in 1.0-1381.

Cameron Kaiser wrote:
> This message is really, really long. Here goes:
> 
> ** OverbiteFF for Firefox 3: "RTM"
> 
> With the release of Firefox 3 RC2, I took the wraps off OverbiteFF. This is
> the release version, 1.0-1381. It does have some small changes, including a
> bug fix for port access, additional explicit ports and CSS tweaks, so it is a
> recommended download if you are still using -1380. We'll see if anyone gets
> the joke on the build number. ;-)
> 
> You can now preview the Overbite Project pages. There are HTTP and Gopher
> versions:
> 
> 	http://gopher.floodgap.com/overbite/
> 
> 	gopher://gopher.floodgap.com/1/overbite/
> 
> (These are not publicly announced yet, but you can access them.) The
> HTTP and Gopher pages are largely drawn from the same data store, so
> people will get mostly the same views.
> 
> Additional language packs are still being accepted from translators and I
> will gladly add them to OverbiteFF 1.1.
>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Cameron Kaiser | 5 Jun 2008 16:59
Favicon

Re: Unveiling the Overbite Project (and other announcements)

> Cameron, just to be sure, did you receive my email with a screenshot and 
> description of the error with displaying links to files in Russian 
> version which seems to be some unicode rendering problem? It's the same 
> in 1.0-1381.

No, I didn't. Can you resend?

--

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@...
-- The son becomes the father, the father becomes the son, the uncle has a beer.
Permalink | Reply | 1 comment |

Gmane