The not-very-secret GOPHER server is well on its way to being back up; and those of you who know GOPHER will soon be able to get the latest development source snapshots of #nosh 1.41 and #djbwares 10 again.
*Of course* it is a machine running those self-same nosh and djbwares to serve up GOPHER et al.. The last one ran #OpenBSD. This one is running #NetBSD, hence the recent porting work.
It's not in its intended location yet. But it is facing the Internet now.
Yes, I have been musing about setting up a GEMINI server, especially as GOPHER doesn't really do virtual hosting and is thus a bit poor when it comes to the #publicfile content model.
I've pre-prepared a gemini6d service bundle, but an actual geminid server to go alongside httpd is still a to-do item.
I first learned of GEMINI's existence only a few days ago.
I made the mistake of starting to learn about GEMINI from its Frequently Asked Questions document.
It's not aimed at people like me, who already understand the benefits and tradeoffs of static content servers. So it drives lots of points home, repeatedly, that I already know.
It's apparently aimed at the same sort of monoculture Chrome+Apache Think for HTTP that parallels the old BIND Think and Sendmail Think that #qmail and #djbdns were up against years ago.
JdeBP