From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] $ object in javascript
Date: Tue, 27 Dec 2016 07:21:08 -0800 [thread overview]
Message-ID: <87tw9pxusb.fsf@the-brannons.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1612262151380.28214@carhart.net> (Kevin Carhart's message of "Mon, 26 Dec 2016 22:53:11 -0800 (PST)")
Kevin Carhart <kevin@carhart.net> writes:
> Hi Chris,
>
>> I'll be honest, I am starting to find this project very
>> overwhelming on an intellectual level.
>> I don't know how long I can keep up.
>
> My alarm bells go off. You have a veto. If you think it is like
> this, the drawbacks may outweigh the benefits or something is awry and
> it shouldn't be done this way.
Oh not at all. I'm not saying "don't move forward" or anything like that!
I mean I have a problem wrapping my head around all of the complexity
here. That's a personal problem of mine, and I'll either get over it or
I won't. But by all means let's keep moving forward!
> I think there is a restriction, which may be a convention rather than
> something that is enforced by code, that AJAX cannot load from outside
> domains, but only from the domain of the original page.
Yes, and we should probably make sure we honor that.
> Although, is this different than the
> security implications of the web request browsed with the 'b' command
> in the first place?
Maybe not much, except all of this stuff is possibly taking place in the
background, totally out of user control.
-- Chris
next prev parent reply other threads:[~2016-12-27 15:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 16:03 Karl Dahlke
2016-11-29 16:24 ` Chris Brannon
2016-11-30 0:47 ` Kevin Carhart
2016-11-30 7:30 ` Karl Dahlke
2016-11-30 7:43 ` Tyler Spivey
2016-11-30 7:54 ` Karl Dahlke
2016-12-01 0:04 ` Kevin Carhart
2016-12-01 1:17 ` Karl Dahlke
2016-12-25 13:06 ` Adam Thompson
2016-12-26 14:52 ` Karl Dahlke
2016-12-27 3:04 ` Kevin Carhart
2016-12-27 3:49 ` Karl Dahlke
2016-12-27 4:17 ` Kevin Carhart
2016-12-27 4:38 ` Karl Dahlke
2016-12-27 18:37 ` Adam Thompson
2016-12-27 4:59 ` Chris Brannon
2016-12-27 6:53 ` Kevin Carhart
2016-12-27 15:21 ` Chris Brannon [this message]
2016-12-27 20:13 ` Kevin Carhart
2016-12-27 13:26 ` Karl Dahlke
2016-12-27 15:47 ` Chris Brannon
2016-12-27 18:48 ` Adam Thompson
2016-12-27 20:23 ` Chris Brannon
2016-12-28 11:42 ` [Edbrowse-dev] Edbrowse in NetBSD Adam Thompson
2016-12-28 11:50 ` Chris Brannon
2016-12-28 12:15 ` Adam Thompson
2016-12-27 19:11 ` [Edbrowse-dev] $ object in javascript Adam Thompson
2016-12-27 19:47 ` Kevin Carhart
2016-12-27 20:11 ` Karl Dahlke
2016-12-27 20:45 ` [Edbrowse-dev] nextSibling and previousSibling Kevin Carhart
2016-12-27 21:14 ` Chris Brannon
2016-12-28 11:38 ` [Edbrowse-dev] $ object in javascript Adam Thompson
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=87tw9pxusb.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--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).