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...
#retro #lisp #interlisp #ibm3270 #gopher #rfc1436 #commonlisp
#Minnesota was Silicon Valley before #SiliconValley
Watch this wonderful #documentary from Twin Cities #PublicTelevision (TPT) and see if you can spot a much younger me in the half second that I appear in a photograph!
https://www.tpt.org/solid-state/
#InternetGopher #RFC1436
#minnesota #siliconvalley #documentary #PublicTelevision #InternetGopher #rfc1436
Last week @pzriddle@mastodon.io sent me some vintage Internet Gopher T-shirts that were apparently cluttering his attic. Now you can watch me model these way-too-small shirts with my stomach TOTALLY sucked in so I can't breathe!
Thanks Prentiss!
#InternetGopher #vintage #gopher #RFC1436 #GopherWorldTour93 #oldtimecomputing #vintagecomputing #peoplewhoshouldnevermodel #GopherCon
#InternetGopher #vintage #gopher #rfc1436 #gopherworldtour93 #oldtimecomputing #vintagecomputing #peoplewhoshouldnevermodel #gophercon
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.”
#ietf #rfc1436 #gopher #gopherhole #GopherProtocol #gopherverse
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.”
#ietf #rfc1436 #gopher #gopherhole #GopherProtocol #gopherverse
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 […]”
#ietf #rfc1436 #gopher #gopherhole #GopherProtocol #gopherverse
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 […]”
#ietf #rfc1436 #gopher #gopherhole #GopherProtocol #gopherverse
welCOM frendiverse fren
#lisp y #gopher with @screwtape on #aNONradio hosted by #SDF about #common-lisp #ecl #rfc1436 you could use #lynx
ecl <<EOG
(require 'asdf)
(mapc 'ext:system
'("lynx gopher://gopher.club"
"lynx gopher://gopher.club/1/users/screwtape")
EOG
#lisp #gopher #anonradio #sdf #common #ecl #rfc1436 #lynx