Do you know about GopherVR?
https://en.wikipedia.org/wiki/GopherVR
I used #gopher back in the 1990s.
But there has been a gopher revival going on
I.e., gopher is used today!
I wonder how many in the new Gopher community are aware of #gopherVR ?
.
( #gopherHole #gopherProtocol #gopherverse )
( #virtualReality #VR )
H/T @atomicpoet
#gopher #gophervr #gopherhole #GopherProtocol #gopherverse #virtualreality #vr
Do you know about GopherVR?
https://en.wikipedia.org/wiki/GopherVR
I used #gopher back in the 1990s.
But there has been a gopher revival going on
I.e., gopher is used today!
I wonder how many in the new Gopher community are aware of #gopherVR ?
.
( #gopherHole #gopherProtocol #gopherverse )
( #virtualReality #VR )
H/T @atomicpoet
#gopher #gophervr #gopherhole #GopherProtocol #gopherverse #virtualreality #vr
4/
I used #gopher back in the 1990s.
But there has been a gopher revival going on
I.e., gopher is used today!.
The new gopher community should be open to creating new line-type codes.
That is part of how the #gopherProtocol was future-proofed.
Creating new line-type codes is using gopher as intended by the specification writer(s).
#gopher #GopherProtocol #gopherhole #gopherverse
4/
I used #gopher back in the 1990s.
But there has been a gopher revival going on
I.e., gopher is used today!.
The new gopher community should be open to creating new line-type codes.
That is part of how the #gopherProtocol was future-proofed.
Creating new line-type codes is using gopher as intended by the specification writer(s).
#gopher #GopherProtocol #gopherhole #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
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
#GopherProtocol #gopher #gopherhole #gopherverse
#GopherProtocol #gopher #gopherhole #gopherverse
#GopherProtocol #gopher #gopherhole #gopherverse
#GopherProtocol #gopherhole #gopherverse