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

[gopher] Re: Problem with SiMpLeMaChInEs

Seriouisly though please read the rest of the RFC as Brian posted, and remeber the secondary servers such as whois, WAIS , Jughead, Jugtail, Veronica and other gophers not privaleged to port 70 and multiple gophers from one IP, you simply are looking at it as a convienience to you and assuming that the world can or should comply with broken clients, this honestly is a ( in my opinion) silly if not selfish stance, and all joking aside and with no undo flaming please consider what your asking. Firstly all gophers at my location and others that use "other than" port 70 would be ... what eliminated? And then also would all search engines not on 70 (jughead and veronica are not meant to run on port 70 )? And of non privaleged to port 70 users all over elsewhere ? This to me is preposterous and against any and all RFC's written ever about the gopher protocol. I mean it too, it's simply unfathomable to me that because a client is not correct that a sever should change to match it..!
 . I mean really ?!? Whats with that?!
Whatever I spose its all mute since it's only gopher and nothing of any importance to anyone but.... a larger and more dangerous point and one your not seeing is that your prepared to stand with a side that is saying
.... because we built something this way the world shall now follow.
Not standing on the side that says ok we see all the potentials and capabilities so we will build our client accordingly. 
One has the horse lead the cart the other turns them around and later on if you feel as it sounds like you do you will watch as a great many things change and freedoms erode and fall away as monolpolies steer the course of software development, it happens already look at all the computers brought new to run the latest software which requires a larger more bloated O.S. , but my, how this steers away from gopher... or does it? 
Just my advice never let client side software steer the ship, or whomever made the client side software will own your boat.
But heck as for what happens to gopher does anyone really care except for like 6 people? I just want it kept as it is with the rules it has always had.
Again, I mean no flames or personal disrespect but I feel strongly about keeping gopher intact as is.

On Wed, 1 Aug 2007 09:08:42 -0700 (PDT)
JumpJet Mailbox <jumpjetinfo@yahoo.com> wrote:

> This is the last I will say about Port 70.  It comes from the second paragraph of the Introduction, in the Gopher Protocol RFC1436:
>      Gopher servers should listen on port 70 (port 70 is assigned to Internet Gopher by IANA).  
> Stegozor <stegozor@gmail.com> wrote:
>   On 7/24/07, SiMpLe MaChInEs wrote:
> > I'd appreciate any feedback for
> > other client/plateform combos of course.
> Lynx and Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:
> Gecko/20070716 SeaMonkey/1.1.3 (under Windows Millennium) work fine
> with gopher://jgw.mdns.org/ . Arachne v1.90;J1 under DOS (actually a
> boot diskette) also works quite well. That said, I agree with Jumper,
> it's better to stick with port 70 whenever possible. We're not all FSF
> members, you know (sorry Chris ;-) .
> > Have a hot summer,
> No, thanks. It's already too hot here... :-p
> -- 
> "Goebbels was in favor of free speech for views he liked. So was
> Stalin. If you're in favor of free speech, then you're in favor of
> freedom of speech precisely for views you despise. Otherwise, you're
> not in favor of free speech". Noam Chomsky.
> ---------------------------------
> Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.

Join FSF as an Associate Member at:

Reply to: