I was inspired by @someodd's profound theory of computing to view the gopher ( #rfc1436 ) as a platonic solid of our universe's model of communication
in the same way that Alan Kay says that LISP is a fundamental part of our universe same as Maxwell's equations.
In so many words. I decided to just runtime signal the condition that I view some thing as being browsably of the gopher.
https://screwlisp.small-web.org/conditions/lispy-gopher/
Edit: Added example, then also added the running example
On the topic of #retro #lisp for, while trying to enknowledge myself about Xerox AI Workstations viz #interlisp-d , I happened across https://github.com/marcoxa/CL3270 ; a current/two year old #ibm3270 backend slash toolkit.
This is interesting because #gopher #rfc1436 defines T items as pointing to a tn3270 session.
So I could just talk to my #CommonLisp repl through x3270(1) and that CL3270. I'm getting the sinking feeling someone told me to do this before...
3/
An excerpt from #IETF #RFC1436
( https://www.rfc-editor.org/rfc/rfc1436 )
“[…] This removes the need to be able to anticipate all future needs and hard-wire them in the basic Internet Gopher protocol; it keeps the basic protocol extremely simple. In spite of this simplicity, the scheme has the capability to expand and change with the times by adding an agreed upon type-character for a new service.”
2/
An excerpt from #IETF #RFC1436 specification
( https://www.rfc-editor.org/rfc/rfc1436 )
“The first character of each line in a [ #Gopher ] server-supplied directory listing indicates whether the item is a file (character '0'), a directory (character '1'), or a search (character '7'). This is the base set of item types in the Gopher protocol. It is desirable for clients to be able to use different services and speak different protocols […] as needs dictate […]”
screwlisp
Albatross
vintage screwlisp account
@reiver ⊼ (Charles) 