Strange interaction between UM Gopher and Gophernicus
I noticed this odd interaction between the UM Gopher client and the
Gophernicus server that I initially thought was a bug in Gophernicus. I
reported it at https://github.com/gophernicus/gophernicus/issues/48
whereupon it seems to have been traced to a problem in UM Gopher. To make
things worse, it manifests only with this client/server combination.
The basic problem is that with some file downloads, UM Gopher appends a
bunch of dashes and the file's datestamp appended to the end of the
filename. Contrary to what Fosslinux states, the bug isn't necessarily
triggered by a long path. After playing with debugging fprintf()s, I
found that at gopher.661.org, in the "Computer Underground Digest"
directory, all of the textfiles there will show this problem. The path
there is simply cud/ with the text files conforming to 8.3 filename
length limits.
I'd have filed an issue at https://github.com/jgoerzen/gopher, but the
issues button is disabled.
--
David Griffith
dave@661.org
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Reply to: