Sigh. It seems gopher.club has changed its gopherd to Bucktooth...
again, and with no warning... again...  breaking all gopher moles
(CGIs)... again. Sdf.org still uses gophernicus, however, which is
kind of confusing, especially if you read the gopher tutorial and
setup a CGI like it describes there, only to have it fail when your
phlog gets listed on gopher.club.

slugmax@iceland:~> ssh gopher.club 'grep gopher /etc/inetd.conf'
...
gopher  stream  tcp     nowait  nobody:nobody   /usr/local/sbin/buckd     buckd

slugmax@iceland:~> ssh sdf  "grep '^gopher' /etc/inetd.conf"
...
gopher  stream  tcp  nowait  nobody  /usr/local/sbin/in.gophernicus  in.gophernicus -h sdf.org
slugmax@iceland:~>

Please, SDF/smj/membership@, you need to warn people when you make
major changes like that. Bucktooth is old, abandoned, insecure, and
I have no idea why anyone would use it anymore. Gophernicus is
actively maintained and written with security in mind (as are a few
other gopherds, any of which would have been preferable to
Bucktooth).

So, what can you do if you use a CGI for your phlog?

Workaround #1: Host your phlog somewhere else that uses gophernicus,
like circumlunar.space, or self-host.

Workaround #2: Access your phlog from sdf.org instead of
gopher.club. Sdf.org (for now) still uses Gophernicus, so you can
still run CGIs from your phlog if it uses sdf.org as the base
hostname. This one sucks, because gopher.club is so damned cool. But
at least logout [0] could change his phlog aggregator so that
gopher.club is replaced by sdf.org. But for how long?

[0] gopher://i-logout.cz/0/en/phlog/09-2018-phlog.txt