|
Grex > Agora > #21: What happened to Grex's Gopher server? | |
|
| Author |
Message |
| 14 new of 79 responses total. |
tfurrows
|
|
response 66 of 79:
| 
Aug 25 23:29 UTC 2017 |
A few users here are active in the gopher space on grex, thanks for keeping
it running cross.
quick question: in our html folders we're not supposed to upload images, as
far as I understand. What about our gopher folders? I put a few images in mine
of an electronics project. Is it a common-sense-don't-overdo-it approach, or
are images simply not allowed period? Thanks.
|
papa
|
|
response 67 of 79:
|
Aug 26 00:06 UTC 2017 |
It's cross's call, but that's probably a rule made long ago to deal with abuse
of a very different Grex and a very different Internet from what we have now.
|
cross
|
|
response 68 of 79:
|
Aug 26 13:47 UTC 2017 |
Try either and see whether it works. :-)
|
tod
|
|
response 69 of 79:
|
Aug 29 10:10 UTC 2017 |
re #66
Depends if your modem is set for 7 or 8 bit? ;)
|
nydel
|
|
response 70 of 79:
|
Feb 25 04:19 UTC 2018 |
there is a bit of a security problem with the current version of gophernicus
we run. please do this to see:
$lynx gopher://grex.org:70/1/server-status
forgive me, i'm not in a multiplex, that /1/ may be a /0/
the page displays the ip address and content viewed from all open sessions.
is it possible to upgrade or otherwise disable this feature?
tildetown and sdf have been able to disable it. would other grexers agree with
or disagree with the suggestion that this is a potential security issue that
should be patched if possible?
thank you kindly grex for serving our gopherspaces. oh the fun we're having!
|
papa
|
|
response 71 of 79:
|
Feb 25 05:58 UTC 2018 |
I think the odds of it being exploited are low due to the obscurity of
gopherspace and grex, but publishing IP addresses is not a good idea. I have
no problem with this feature being disabled.
|
tfurrows
|
|
response 72 of 79:
|
Feb 26 02:20 UTC 2018 |
I'd love to see it disabled, even if it's never seen by anyone.
|
tfurrows
|
|
response 73 of 79:
|
Oct 25 16:03 UTC 2018 |
The gopher server at grex is behaving oddly. Visiting user's links directly
works fine, as does browsing their content, but attempting to visit grex.org
fails. Any idea what might be wrong?
|
cunnings
|
|
response 74 of 79:
|
Oct 26 01:58 UTC 2018 |
Visiting grex.org's gopher server works, if you wait a very long time.
At least that's what I've been seeing here. I wonder if it's because
the main menu is generated by script that runs very slowly (the last
time I tried it took 14 minutes!). But as you pointed out, there's no
delay when visiting a user's gopher directly.
|
tfurrows
|
|
response 75 of 79:
|
Oct 29 02:46 UTC 2018 |
14 min! eek, that's a long wait...
|
walkman
|
|
response 76 of 79:
|
Dec 10 22:36 UTC 2018 |
One can mail packages out of China but one cannot access the Grex Gopher
server behind the great wall.
(2) Social Credit Score points deducted.
New occupation: Groom of stool
|
tod
|
|
response 77 of 79:
|
Dec 12 15:23 UTC 2018 |
I'm holding out for Veronica
|
tfurrows
|
|
response 78 of 79:
|
Jan 4 21:12 UTC 2019 |
Any thoughts on the gopher server slowness? User pages seem to load quickly,
but the home/root does not. Anything in the logs that would indicate why?
Time to switch gopher servers?
|
cunnings
|
|
response 79 of 79:
|
Jan 5 05:56 UTC 2019 |
The main menu is a list of gopherholes at grex - how is that built??
I suspect that a script is searching all the home directories for
public_gopher subdirs to build the list dynamically. If that's true
then it would certainly take a while - just a theory though.
|