[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lynx-dev] Gopher support for the "+" item type

From: James Tomasino
Subject: [Lynx-dev] Gopher support for the "+" item type
Date: Wed, 10 Jan 2018 11:18:51 -0500
User-agent: Mutt/1.5.20 (2009-12-10)

Hello Lynx developers,

First of all, thank you for your continued support of the gopher
protocol. Your browser helps keep the small but active gopher community

I recently discovered that Lynx does not have support for one of the
gopher item types defined in RFC 1436
( The + item type is defined as:

  The information applies to a duplicated server.  The information
  contained within is a duplicate of the primary server.  The primary
  server is defined as the last DirEntity that is has a non-plus "Type"
  field.  The client should use the transaction as defined by the
  primary server Type field.

Basically, it is a mirror of whatever the last type listing was. In
visual terms it can be hidden and used as a fall-back when trying to
access an item which fails to load. In gophermap terms, it could look
like: (\t used to represent tab characters)

1Tomasino's Gopher Hole\t/users/tomasino\\t70
+Tomasino's Gopher Hole Mirror\t/~tomasino\\t70

If my primary link is unresolvable, the system can fall back on the
alternate mirror.

If you want to see it in action, the gopher client named "gopher" has
support you can try out. Lynx reports "+" items as an unknown type.

Thanks again for your continued gopher support,

James Tomasino

reply via email to

[Prev in Thread] Current Thread [Next in Thread]