From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (71-38-131-64.ptld.qwest.net [71.38.131.64]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 051AF7895D; Tue, 6 Oct 2015 22:11:10 -0700 (PDT) From: Chris Brannon To: "Peter Billam" Cc: edbrowse-dev@lists.the-brannons.com References: <9ce37d$11ptkrh@ipmail07.adl2.internode.on.net> Date: Tue, 06 Oct 2015 22:14:48 -0700 In-Reply-To: <9ce37d$11ptkrh@ipmail07.adl2.internode.on.net> (Peter Billam's message of "Mon, 28 Sep 2015 16:33 +1000") Message-ID: <87lhbfmf93.fsf@mushroom.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] adblocking ? was: experimental JS console patch X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Oct 2015 05:11:11 -0000 "Peter Billam" 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