RE: Post-RFC item types

Looking at the other end: I did an automated survey a couple of years ago to find all of the currently used Gopher menu types.

My comments about your list:

h     HTML			popular (3914)
s     sound file			uncommon (278)
w     WWW address		very uncommon (9)
:     Gopher plus image		“none”
;     Gopher plus movie		very uncommon (11)
<     Gopher plus sound		“none”
P     Gopher plus PDF		very uncommon (26)



Sent from Mail for Windows 10

From: Zachary Lee Andrews
Sent: Sunday, April 4, 2021 9:58 PM
To: [email protected]
Subject: Post-RFC item types


Hello folks,

I am wondering if all modern clients have adapted all of the item types 
supported by the UMN client and Lynx (libwww) which were not in RFC1436.
In libwww and Lynx they're defined in HTGopher.c
I am assuming that everybody has got the i item type supported by now 
(lol). But what about w? I think w is far better than the GET%20/ or the
hURL hacks.

For reference here are the item types I am referring to.

h     HTML
s     sound file
w     WWW address
:     Gopher plus image
;     Gopher plus movie
<     Gopher plus sound
P     Gopher plus PDF



Examples of w itemtype
:
wA website	https://gopher.zcrayfish.soy/	(NULL)	1
wSDF IRC	irc://irc.sdf.org:6667/gopher	(NULL)	1

-- 
  Zachary Lee Andrews
<[email protected]>
gopher://gopher.zcrayfish.soy/