Message-ID: <6928bac3@news.ausics.net>
From: not@telling.you.invalid (Computer Nerd Kev)
Subject: Re: Gopherpedia is Alive?!
Newsgroups: comp.infosystems.gopher
References: <10f2dji$1im9k$1@dont-email.me> <87o6p060jc.fsf@rpi3> <10fht6e$1j667$1@dont-email.me> <87tsymnwdz.fsf@rpi3> <10fsgt2$go5r$1@dont-email.me> <874iqi5pjr.fsf@rpi3> <10g4h67$3hd6i$2@dont-email.me> <87ms49hqna.fsf@rpi3> <69277b25@news.ausics.net> <87tsyge1mr.fsf@rpi3> <6927aa82@news.ausics.net> <10g93c3$17qmq$1@dont-email.me>
User-Agent: tin/2.6.5-20250707 ("Helmsdale") (Linux/2.4.31 (i586))
NNTP-Posting-Host: news.ausics.net
Date: 28 Nov 2025 06:55:31 +1000
Organization: Ausics - https://newsgroups.ausics.net
Lines: 23
X-Complaints: abuse@ausics.net
Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail
Xref: csiph.com comp.infosystems.gopher:813

Nuno Silva <nunojsilva@invalid.invalid> wrote:
> On 2025-11-27, Computer Nerd Kev wrote:
>> Have you tried UMN Gopher? Anyway given the behavior with long
>> selectors in other Gopher clients I'm fairly sure super-short
>> connention time-outs on the srver are the issue. Your internet
>> might be quick enough that the requests always get through in
>> time.
> 
> From US SDF, on what I think is the UMN gopher client (unless it has
> been replaced by something else?), I can load the front page, but any of
> the entries appear to fail to transfer content.
> 
> Is this some issue with gopher+? IIRC didn't the UMN client try to do
> gopher+ requests to all servers?

I'm not sure, although other clients are failing on some requests
for me too, most often with long request strings, so I doubt it's a
gopher+ problem. I've emailed Gopherpedia's author about it (at
the email address on the https://muffinlabs.com website).

-- 
__          __
#_ < |\| |< _#