edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Forever
Date: Wed, 17 Jan 2018 14:35:20 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.03.1801171415080.18031@carhart.net> (raw)
In-Reply-To: <20180017074324.eklhad@comcast.net>



I know.  You're right.  I will try to pursue this.  I have actively 
procrastinated performance because this often was the next thing that 
unfolded after it didn't work at all, like on NASA.  (Note on NASA, I 
think it has had a regression and returns "1 character" again.  I think 
this has to do with cloneNode copying handlers which is in a jquery 
"supports" test.  Except we implemented that, so maybe this isn't the cause.)

> So this website hangs forever, and you can't even ^c out of it.
> https://sploid.gizmodo.com/this-giant-fireball-over-michigan-was-visible-from-six-1822143868

I get a libcurl error on this.  SSL connect error in libcurl: 
error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol 
version

But maybe I can upgrade my libcurl and take care of it.

You know that person who wrote on github and reordered the sections of the 
README?  Do you write to people like that and try to allure them into 
coding something?  "As long as you've done a lovely job improving the 
instructions, would you like to do some more.."



      reply	other threads:[~2018-01-17 22:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 12:43 Karl Dahlke
2018-01-17 22:35 ` Kevin Carhart [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.03.1801171415080.18031@carhart.net \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).