Gopher is by definition the opposite of the web. However, the concept of "phlogroll" exist, though it's basically just linking to other holes from your own. Unless I misunderstand the concept of "webring" ?

The only thing a webring requires is a link on each website to another one. If it has external links then in theory it is possible.

However, resolution of the "next" site in the ring (as far as I understand it) is done when the link is clicked, which obviously requires some kind of code to run somewhere.

That's not how I remember it and Webring also suggests the previous/next links were fixed at time of creation. Incidently, it also mentions webrings became obsolete when search engines were good enough to find content easily, so it might still be a thing for gopher.

Gopher has search engines, and they work pretty well. See Veronica 2.

(25-09-2020, 12:58 PM)z3bra Wrote: You can also try setting up ipv6, that could be the occasion ^^

It turns out that there was a bug in phetch where it would only try the 1st returned IP address when a name lookup returns multiple IP addresses. Obviously the 1st IP address was IPv6 which my router isn't capable of.

Phetch has now been updated and this bug has been fixed.

(06-10-2020, 01:33 AM)Dworin Wrote: That's not how I remember it and Webring also suggests the previous/next links were fixed at time of creation. I

In that case it should be very easy then; page generation can just get the next site and stick it in.

Hey z3bra, is g.nixers.net down? I'm not getting through.

It was indeed, the gopher daemon didn't start after the reboot. Not sure why thouhg…

Thanks for the notice, it should be back up now !

I usually recommend just using Gophernicus behind inetd. Never had a problem with reliability here.

It's just that the server wasn't registered to start on boot. This should be fixed now.

(04-11-2021, 06:22 AM)z3bra Wrote: It's just that the server wasn't registered to start on boot. This should be fixed now.

I'm still not getting through.
I get this:

Should be fixed now. I inadvertently pushed the default index.gph of the server's project, which took precedence over the correct one.

Sorry about that and happy gophering !

(19-11-2021, 03:34 AM)z3bra Wrote: Should be fixed now.

Yep, thanks!

(15-09-2020, 02:59 AM)z3bra Wrote: There are a few ones already:

• lynx browser
  
• sacc
  
• clic (for emacs)
  
• bombadillo
  
• Many more
  

The elinks browser also supports the gopher protocol.

Not available in OpenBSD ports, but see here and here. Not sure if this resolves the issues the OpenBSD team had with it; if anyone can speak to that I'd like to hear what you think.

Upshot: use the latest git version, not the last stable release from 2009. (FWIW, Debian's package is based on the felinks fork, which is more actively maintained.)