Do Not. Extend. Gemini. Period

Drew's stance here is warranted, in my opinion. I don't think it was rude, just stern. His fear of Gemini growing into the next web is the same reason why I've stayed away from it for a while - I don't want to waste time on a second, Not-Invented-Here web.

To avoid confusion and prevent anyone from implementing this feature we should extend the Gemini server standard to respond with a well define error code as follows:

   The 501 (Not Implemented) status code indicates that the server does
   not support the functionality required to fulfill the request.  This
   is the appropriate response when the server does not recognize the
   request method and is not capable of supporting it for any resource.

/s

The problem with simple protocols designed to stay simple is that the only pressure is the client & server implementations. The only simple state is to not have any defined behavior so the favicon could be there, not be there, or be a 1GB image, or (in Drew's threat) a path-knocking path that blocks the requesting IP address.

However, all this discussion did was demonstrate that the protocol is no longer simple since now you have to read this Github thread to know why a server is blocking your Gemini client. If Gemini is simple, a valid client should only have to know what the spec says (I would assume it's here somewhere? https://gemini.circumlunar.space/). However I guess since the specification is not actually finalized (?) then maybe this isn't an issue yet.