edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: "Peter Billam" <pj@pjb.com.au>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] adblocking ? was: experimental JS console patch
Date: Tue, 06 Oct 2015 22:14:48 -0700	[thread overview]
Message-ID: <87lhbfmf93.fsf@mushroom.localdomain> (raw)
In-Reply-To: <9ce37d$11ptkrh@ipmail07.adl2.internode.on.net> (Peter Billam's message of "Mon, 28 Sep 2015 16:33 +1000")

"Peter Billam" <pj@pjb.com.au> writes:

> I think this raises the question of adblocking for edbrowse ...

Hi Peter,
Sorry I didn't reply to this one earlier.  Nope, I didn't miss it, I was
just holding back.
You know, I've looked at a lot of JavaScript in recent weeks, and a
surprisingly large amount of it is related to, you guessed it, ads.
I wonder what the percentage is?
We aren't quite at a point where we really have to worry about it, but
I'm sure that whenever we can browse very "rich" dynamic sites with
edbrowse, online advertising is going to be a problem.

I have no idea how adblocking would work for edbrowse.  How does it work
in the mainstream browsers, exactly?  I think it's usually an extension
written by a third party, isn't it?  The only thing stopping us from
building it into edbrowse will be lack of developers.  At one time,
there used to be proxy servers for this sort of thing.  I remember one
called JunkBuster.  It would be nice if we could just install a proxy
server and point edbrowse at it, but I think that the proxy server
technique is no longer used.

-- Chris

  reply	other threads:[~2015-10-07  5:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28  6:33 Peter Billam
2015-10-07  5:14 ` Chris Brannon [this message]
2015-10-07  7:04   ` Karl Dahlke
2015-10-07  7:40 Peter Billam

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=87lhbfmf93.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=edbrowse-dev@lists.the-brannons.com \
    --cc=pj@pjb.com.au \
    /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).