Groups | Search | Server Info | Login | Register


Groups > comp.infosystems.gopher > #748

Re: UMN Gopher - menu title length.

From morena <morena@morena.rip>
Newsgroups comp.infosystems.gopher
Subject Re: UMN Gopher - menu title length.
Date 2025-03-03 23:42 +0100
Organization The internet is full.
Message-ID <vq5b8u$1gln2$1@dont-email.me> (permalink)
References (2 earlier) <vpvqp1$ce4a$1@dont-email.me> <vq0k2c$ki7$1@nnrp.usenet.blueworldhosting.com> <vq1dks$oafd$1@dont-email.me> <vq50ib$1er3n$1@dont-email.me> <vq559a$1fmbt$1@dont-email.me>

Show all headers | View raw


On 3/3/25 10:00 PM, IanJ wrote:

> An ASCII art banner, spacing and section headings. All of which can be
> safely ignored.

I don't see anything about ASCII art banner, spacing or section headings 
in the RFC 1436.

> Menus are not used for content in place of files, that is the point.

22 from 58 lines. Yes, that's not menu item, but content file.

>> Also that right aligned date is nonsense.
> 
> Your opinion.

Most people write opinion of somebody's else sadly, luckily I write my own.

> The subject of the thread is 'UMN Gopher - menu title length.'. Please
> let us focus on whether the changes I have made in my patch are an
> improvement to the client, worthy of submitting for inclusion in the
> main branch.

UMN Gopher client is broken and full of junk. It has issue with most 
Gopher servers available this time.
If you would like that it is RFC compliant, then you should probably 
make your own server that way. Then you may touch tools other people use 
too. You can get always inspired by my RFC 1436 compliant Gopher server.

Also if you mentioned "i" item type issue, you should allow others to 
write about it too.

Sometime is good to let things go. Let them die in peace. UMN Gopher 
want's to die, Gopher protocol too.

-- 
morena
gopher://morena.rip
nex://morena.rip

Back to comp.infosystems.gopher | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

UMN Gopher - menu title length. IanJ <SPAMian_jones_01@yahoo.co.uk.invalid> - 2025-02-25 18:57 +0000
  Re: UMN Gopher - menu title length. Stone Fox <stone@unix.dog> - 2025-02-26 21:29 +0000
  Re: UMN Gopher - menu title length. Lawrence Woodman <lorrywoodman@gmail.com> - 2025-02-28 09:03 +0000
    Re: UMN Gopher - menu title length. Lawrence Woodman <lorrywoodman@gmail.com> - 2025-02-28 09:35 +0000
      Re: UMN Gopher - menu title length. Stone Fox <stone@unix.dog> - 2025-02-28 22:21 +0000
    Re: UMN Gopher - menu title length. IanJ <SPAMian_jones_01@yahoo.co.uk.invalid> - 2025-03-01 20:30 +0000
      Re: UMN Gopher - menu title length. "Arti F. Idiot" <addr@is.invalid> - 2025-03-01 20:42 -0700
        Re: UMN Gopher - menu title length. Computer Nerd Kev <not@telling.you.invalid> - 2025-03-02 15:59 +1000
        Re: UMN Gopher - menu title length. IanJ <SPAMian_jones_01@yahoo.co.uk.invalid> - 2025-03-02 10:58 +0000
          Re: UMN Gopher - menu title length. jeojet@not.valid - 2025-03-02 16:13 +0000
            Re: UMN Gopher - menu title length. IanJ <SPAMian_jones_01@yahoo.co.uk.invalid> - 2025-03-02 18:36 +0000
          Re: UMN Gopher - menu title length. morena <morena@morena.rip> - 2025-03-03 20:39 +0100
            Re: UMN Gopher - menu title length. IanJ <SPAMian_jones_01@yahoo.co.uk.invalid> - 2025-03-03 21:00 +0000
              Re: UMN Gopher - menu title length. morena <morena@morena.rip> - 2025-03-03 23:42 +0100
                Re: UMN Gopher - menu title length. IanJ <SPAMian_jones_01@yahoo.co.uk.invalid> - 2025-03-03 23:04 +0000
      Re: UMN Gopher - menu title length. Stone Fox <stone@unix.dog> - 2025-03-02 21:34 +0000
        Re: UMN Gopher - menu title length. IanJ <SPAMian_jones_01@yahoo.co.uk.invalid> - 2025-03-03 23:23 +0000

csiph-web