Extensions to Gopher, outcomes

--Sig_/Mq+FzLQRzw1=ypySo3Cc8=0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello gophers,
I am new to this mailing list and I am wondering what extensions to
Gopher have been proposed on the list, and what their outcomes were.

I recently started attempting to document the current state of Gopher:
<gopher://tilde.32bit.cafe/1/~vivivi/gopher_in_practice> but I have not
yet aggregated much info from this very mailing-list.
I'm seeing evidence that gophernicus.org also had similar
documentation to what I'm trying to make, but connecting to it with
gopher:// today just seems to stall.

I did find in this list's archives the following document:
<https://tinyurl.com/gopherrfc-draft>
I will comment (admittedly a decade or so late :p ) that 'example.com'
is probably not the best domain to use for an intended invalid link,
especially when the '.invalid' TLD exists for this very purpose.
And I will ask if the 'M' type was intended to follow the
message/rfc822 format =E2=80=94 that's the impression I got when testing Go=
pher
clients but perhaps it's more complicated than that.

--Sig_/Mq+FzLQRzw1=ypySo3Cc8=0
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEECRScMMLqbawFEVXLbbTQGyXkVXUFAmXHIYIACgkQbbTQGyXk
VXUZjggAojrk1EIvvqQ5nSQbjLReO7ZXBVVaJ4NZT/3fzDxotMYUvmsEdg4aDgZF
r/jhVu27gWjBf8rHiNrjo7+cqWlpzDyiKzpyhvcV7ZrDnofS19TWWdTTJg2QG+4/
Uu8X3+w/Ob9gJer80E1JZwhKHC8bOrPkhXd7t+FoiitTVWVQxERiAU5iqYijjRW6
9xCVzfcqv+JKK+leotGrZ0sgsWT2eADsEx+siw551zW1bGBeEZQLoiGfMsiDqUM4
hv4ldH71ZXrbk5N4eV1PN90C5Zo5gflanYFJ/tXlj8a1S+bHb1npd7jFZbg6h4LM
SiRQ9caLIjGeZ23EV/12xsHJ2PPkpQ==
=2swr
-----END PGP SIGNATURE-----

--Sig_/Mq+FzLQRzw1=ypySo3Cc8=0--