From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Dynamic Scripts
Date: Mon, 29 Jan 2018 15:39:03 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1801291526500.22631@carhart.net> (raw)
In-Reply-To: <20180029174049.eklhad@comcast.net>
> Sadly, nasa still comes up empty, so that wasn't the answer.
It's part of the answer, I'm certain. It could be "necessary but not
sufficient." Immediate evaluation is big.
> Meantime, I'm betting, based on the domain, that they all deal with images, and we don't care.
I seem to remember thinking so, and then finding out that indeed they
addressed this domain to retrieve code that is more fundamental.
"ClientSideMetrics blah blah blah V2.js"
Possibly this takes a bunch of calculations and does that thing where they
use this as a proxy for user agent.
It may be that it is fine to exclude the domain, but that V2 code looks
like it might be a blocker on later steps if it hasn't run.
prev parent reply other threads:[~2018-01-29 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 22:40 Karl Dahlke
2018-01-29 23:39 ` 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.1801291526500.22631@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).