Fwd: elpher now supports gemini

[plugd]

Hi Bradley,

Wow - I didn't expect such a detailed usage report!  Thank you very
much, this is incredibly useful.

I will go through all of your comments in detail later.  But at the
moment I want to rush out a quick reply to point out that some of the
"Gemini server reports PERMINANT FAILURE" errors might have been due to
a bug in the URL processing code.  I was mishandling the (important!)
edge case where the filename portion is empty, resulting in broken URLs
being sent to servers. This should now be fixed.

I agree that the the failed connection errors need cleaning up a bit.

I'm not sure what's causing zaibatsu to load slowly for you.  In my case
at the moment it's due to the IPv6 issues that I mentioned earlier.  (It
turns out that Emacs _does_ eventually fall back to the IPv4 address,
but only after a whole _minute_ or so of waiting.)  Is it possible that
your experience is just due to elpher not rendering anything until the
entire document is available?  (I would prefer not to have to do this,
but I'm not smart enough to figure out how to do this without breaking a
lot of the things I like about the current factoring of the code.)

Regarding the cert verification stuff: I'd love to take credit for this
but it is in fact just Emacs' defualt GnuTLS behaviour.  At some point I
hope to change this to reflect solderpunk's TOFU suggestion, as I expect
it'd get annoying when there are upwards of 100 or 1000 gemini servers
with different self-signed certificates.

Hopefully your server (which I don't think I'd stumbled on before)
should be accessible now following the URL parsing fixes.  I've also
added the URL of the current page to the header in the latest release,
so hopefully this also reduces confusion somewhat.


> As far as the IPv4/IPv6 issue, I don't really think most of those
> options should really be left to the author of the client software to
> tackle, and think server support for binding "::" to the NIC to be the
> best solution. Alternately, perhaps temporarily dropping the AAAA RR
> temporarily, until the Gemini server supports IPv6 bindings, if there
> aren't other services listening on the host.

I'm starting to think that this is more of an emacs networking issue.
While the problem does manifest with, for instance, AV-96, it's not
nearly as severe - there's "only" a 10-20s delay in the connection,
compared with a whole minute in emacs.  If only there were a way of
altering the default timeout used by emacs...

> I may have missed a few things here and there, but this is all really
> just the result of playing around with Elpher, which, if I'm not really
> careful, might get me to start saying nice things about Emacs ;)

Be careful, it's a slippery slope... :-P

> I hope that helps :)

It absolutely does!!

plugd

p.s. with the current release I have no problems with the following
servers:

* gemini://vger.cloud/
* gemini://tilde.black/
* gemini://tilde.pink/
* gemini://carcosa.net/
* gemini://heavysquare.com/
* gemini://mozz.us/
* gemini://typed-hole.org/
* gemini://zaibatsu.circumlunar.space/

The following I can't connect to at all (i.e. no server response):
* gemini://gopher.black/
* gemini://consensus.circumlunar.space/
* gemini://dgold.eu/

I cross-checked with AV-98 and got the same results.