[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[gopher] Gopher-dev



Hey guys,

As a way to spend my $0.02 I would like to suggest to the owner of
complete.org to make at least one more list: gopher-dev. I've been doing
my best to keep up with discussions in here, but so far and for the most
part I've just been scratching my head, going "huh?". I respect you all
and appreciate the effort in contributing to gopher, but imho the
discussions that have been taking place over the last few months have
both drastically increased which is good, but also got overly
complicated to me, which isn't as good.

I am not a developer; I don't remember the times of the < 8088 PC's as
I'm (to some of you *only*) 24; and I just want to run a gopher server
without the general hardcore powergopher talk, which at this stage of my
familiarity with gopher, frankly, just turns me away from the original
idea of fun that popped up in my head years ago.

Though my English isn't that bad, it's also not as good as some of you
speak it. In my experience, even a simple question like "how do I do
this or that" can result in either a non-understandable answer or a
discussion that's way out of proportion. Not always, but often.=20

See, to me gopher is like I'm a new kid that drives an old car and
there's nothing wrong with that. I run a simple daemon, pygopherd, and
struggled myself through achieving a simple file called gophermap. Any
other features? Gopher+?  All of the discussions that took place over
the last few times only made me understand that I don't know anything
much about gopher.

I appreciate gopher for all its coolness and henceforth am suggesting
this list to be used as a "general entrance to gopher", with the main
idea to Keep It Simple=E2=84=A2, with another list like gopher-dev@comple=
te.org
for the advanced guru's that are too far away from the more "general
Joe's" like myself. Thanks in advance to the admin of complete.org if
this idea can be manifested.

-Mark
gopher://g.caffeine-powered.net




Reply to: