Fwd: elpher now supports gemini

[Sean Conner]

It was thus said that the Great Bradley D. Thornton once stated:
> 
> 2.) I experienced problems with gemini.conman.org loading beyond 1%.

  What type of problem?  I've been making a lot of changes to the server
code recently and there might be issues that aren't client releated but
server releated.  

> 3.) zaibatsu.circumlunar.space comes up, but it takes a while. Like I
> said above, in Asuka, all sites come up rather quickly, although I can
> tell the difference in the resources being served. In Elpher it can take
> several seconds, however.

  Of the servers, I get:

gemini://gemini.conman.org/		comes up quick [1]
gemini://zaibatsu.circumlunar.space/	comes up quick
gemini://carcosa.net/			comes up quick
gemini://heavysquare.com/		comes up quick
gemini://mozz.us/			comes up quick
gemini://dgold.eu/			error: cannot connect to dgold.eu
gemini://typed-hole.org/		comes up quick
gemini://gopher.black/			(gone---mentioned in another email)
gemini://tilde.black/			comes up quick
gemini://consensus.circumlunar.space/	error: cannot connect to consensus.circumlunar.space
gemini://tilde.pink/			comes up quick
gemini://165.22.178.247/		comes up quick (but returns status 51)
gemini://vger.cloud/			comes up quick

  And of certificates:

gemini://gemini.conman.org/		unknown CA [2]
gemini://zaibatsu.circumlunar.space/	self-signed
gemini://carcosa.net/			self-signed
gemini://heavysquare.com/		unknown CA
gemini://mozz.us/			valid
gemini://dgold.eu/			N/A (can't connect)
gemini://typed-hole.org/		self-signed
gemini://gopher.black/			N/A (gone)
gemini://tilde.black/			valid
gemini://consensus.circumlunar.space/	N/A (can't connect)
gemini://tilde.pink/			self-signed
gemini://165.22.178.247/		self-signed
gemini://vger.cloud/			valid



> A feature of Elpher that I find really kewl is that it doesn't presume
> it's okay to just plough ahead when it perceives there's something funky
> with the cert, as illustrated in this image (I'm unable to select this
> text in Elpher to paste it, if there's a way, please enlighten me):
> https://bit.ly/2kKJCrv
> 
> That originally came up for gemini://conman.org (certificate/host
> mismatch), because that's NOT the hostname the cert was issued for.

  Yup.  I don't know how to create a certificate for multiple hostnames.

> Again, Asuka and the other clients don't complain, but prolly should ;)

  Probably, but if you aren't doing certificate validation (to get around
the whole "self-signed" thing, perhaps it's a moot point?)

  -spc

[1]	It better for me.  I wrote the server.

[2]	I have my own private CA I signed the certificate with.