1. Forum
  2. USENET
  3. comp.infosystems.gopher

  • Re: Canonizing Gopher

    From morena@morena@morena.rip to comp.infosystems.gopher on Fri Oct 18 22:52:26 2024
    From Newsgroup: comp.infosystems.gopher

    On 5/4/18 10:42 PM, Jason Nemrow wrote:

    For my part, the Gopher protocol is that which is rendered correctly by the final version of the UMN Gopher client

    If the UMN gopher client can't render something properly, that something isn't gopher, no matter if it is a "new" type or a different rendering of a menu that can be seen as an improvement.

    If you add new functionality that breaks older clients or makes some menu items unusable or inaccessible to older clients, you are just not doing gopher anymore. I don't want to have to re-code a commodore 64 gopher client because someone decided to redefine gopher and make everything more incompatible...


    Dear Jason,

    I know it's pretty old statement, but not much changed in Gopher RFC
    from that time ;/

    What happened to your gopher? What is that new "gopher-ish" derivate you invented there? I was not here in 2019 where you original post this
    article, I Just assume and speculate that you had gopher which was
    compatible with UMN gopher client and was RFC 1436 compliant.

    I hope nobody and nothing forced you for this incompatibilities and it's
    just matter of time to fix things.

    May you be with gopher again
    --
    morena
    gopher://morena.rip/

    --- Synchronet 3.21d-Linux NewsLink 1.2