Depending what you are making, different protocols can be good (Gemini may be good for some things, NNTP may be good for some things, IRC may be good for some t

Depending what you are making, different protocols can be good (Gemini may be good for some things, NNTP may be good for some things, IRC may be good for some things, etc). Gemini file format also could be usable independently of the protocol, although I do not know of any implementations. I think that sometimes you might want to use Gemini without TLS (it is good they have it, but I am not sure that requiring it is so good), so my proposal is to make the new URI scheme "insecure-gemini:" for this purpose. In this mode, client certificates won't work, so TLS will still be required if you want to use client certificates. Also, unfortunately curl is not implementing Gemini protocol; adding that might help to increase its usage too, since then you can at least download files from it easily. However, I have seen discussions and some of them are valid concerns. For example, I think -k should not be the default; doing it different for different protocols doesn't seem like good to me. You can still specify -k yourself if you want to do. Also the patch does not implement redirects, even if -L is specified; it ought to be fixed to allow -L to work. Allowing longer URLs might also help. Furthermore, a better web browser will need to be made, excluding half of the stuff and implementing the other half of the stuff differently, before adding some more.