Delivery-Date: Mon, 16 May 2016 15:50:09 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 36DE61E08D5;
	Mon, 16 May 2016 15:50:07 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6635D38FFF;
	Mon, 16 May 2016 19:50:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 42B603894C
 for <tor-talk@lists.torproject.org>; Mon, 16 May 2016 19:49:59 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id McwntJhQ9jAp for <tor-talk@lists.torproject.org>;
 Mon, 16 May 2016 19:49:59 +0000 (UTC)
Received: from mout.web.de (mout.web.de [212.227.17.12])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id C4B2638944
 for <tor-talk@lists.torproject.org>; Mon, 16 May 2016 19:49:58 +0000 (UTC)
Received: from 127.0.0.1 ([65.19.167.130]) by smtp.web.de (mrweb103) with
 ESMTPSA (Nemesis) id 0MXpV5-1b7fZI2meN-00WpjN for
 <tor-talk@lists.torproject.org>; Mon, 16 May 2016 21:49:52 +0200
To: tor-talk@lists.torproject.org
References: <5739DF0A.1010903@web.de> <20160516172651.GG2654@demorgan>
From: haaber <haaber@web.de>
Message-ID: <573A2456.9000108@web.de>
Date: Mon, 16 May 2016 19:49:42 +0000
MIME-Version: 1.0
In-Reply-To: <20160516172651.GG2654@demorgan>
X-Provags-ID: V03:K0:0zhu4u9gsHORsTGaU0uJE1uOZbO7AnqghssATYpUR3Dr0XPJl+M
 6/J24jNJA2Q7bhA2xQ5T+hulO4B6RI0F6Litt8AzHq/8WQsXjbItKn4sXGiKCa9sUSx4y+5
 eYBM1L1tdynlRUPCMIWa9ZRHXo7lGNQvzhj8odQRcs5n5Kz7+5k9n0v8HzS0StB3lCBdw8o
 BaVWSpOnKlEHAtOQfFkvA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:I4ICQ8kI2CA=:18rg1vBKV83D4WE0Gq8Gzj
 WUEkIBw6g6TTnueAZfvUBFpBzqJEn6bptlxUH5XHLxfZ8AuKCQpLoUhl0y4rLxzQgTNudWCnQ
 AZR9UJ5pV0tclEy5cldItV+E7RJGn64bAln8cmqlN8nZbhZvfgVFH+pe+RoDpZDKKHWAvvaw0
 HYhEjeU6Eq9NM5P/KPVBB0+LntSp2axbRXrtvtafjJK+iRqBcHjUsHlzC351zHH6BtzLxOqaT
 1xS0Jn+sSjzsM5iNgnXypvFAmV1ZuILrLWjbeiTecvtaSqUKnDa0FpBrR+MULLFZG9A+Nazyu
 lyxHFbqFajAnH9gRnSN7QOwmziyGyAMSjjpPHR+O+3Q2Pn5QV+jrYfh4hAOx9tQjzwKUbsVGG
 gNdZC9eAqHYEw0LWH8NaCpEkpgLjK0iGZUYVB/HKKsU3iBTji7ngfBqFDhMkKE0KHsRYL4Ca7
 J16iWe88wi7CyBi2KTTQl5OtLdKq/JXvId2NqkW4pljCoH4qlJ62DmGJwaxrSK+Oc3tWap4n5
 Mv0u9kQDPQ3UPL0172Gcegh8/ycNZv1Lvr+xnk/Q6/5A9oFnW1J8brJtRruBPurD/URn9fXuC
 5bSSD60J3sX0DOaZcmUh+3tWNR/spLd111PsgcxbZXYFNM1R9lm1xjyMYBhVSOfSmGS5HTfBe
 P/G9ppCPfwjDNum5x8kWs1k1LMyPVlxp5eMnBZ170UqleyaJI5YTZAGeUZE8Klx5P+Ce0AW4v
 bh38+ix1sczGd22tP8vlGHI8HzIxTArmSEiIRoTTBri8q8g/sWZgNcZqv47za2zNispa2SuHu
 f1siDp9RinZrje0znTBf/UYEaDTRA==
Subject: Re: [tor-talk] augmented browsing - "sed inside torbrowser"
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


Thank you for your answer. I should have mentionoed that I have tried
Greasemonkey some time ago. But it is javascript based. None of the
example-scripts worked on a JS-deactivated firefox.  Am I wrong?

A sed / awk whatsoever is at least as powerful, more secure (code tested
for decades), and easy relatively to use, at least if you want
to browse JS-free.

- How to transform JS-enforcing codes like
  <span class=BS" dara-src="link"> into <img="link"> on the fly?
  Or codes like [link="[http://..."] into <href="http://...">

- How add a little openstreetmap into eBay or your favourite private
   local ads site that indicate the location of an object to sell?

and so forth. One/two lines of sed suffise in each case. Greasemonkey
seems to need JS activated (=security hole), and any of the above tasks
takes 30 lines of code.

Privoxy did the job, but it is nowadays useless since not really SSL
compatible. Somehow the "local postprocessing proxy" must sit inside the
browser. I still appreciate any help / comment!

thanks, Bernard



Seth David Schoen:
> haaber writes:
>
>> Hello,
>>
>> I wonder if there are more interested people out there to include a
>> "postprocessing" of the HTML code via  *sed*  type search & replace
>> expressions. A tiny sed copy could be included in the brwoser and a
>> domainbased list of expressions be given to sed that modifies the html
>> code(s) according to personal tastes.
>
> There is a nice existing and non-Tor Browser-specific tool that does
> something along these lines:
>
> https://en.wikipedia.org/wiki/Greasemonkey
>
> It may be a bit more elaborate than what you were thinking of but it's
> a nice tool that can handle a variety of use cases -- and should be
> fully compatible with Tor Browser already.
>


Seth David Schoen:
> haaber writes:
> 
>> Hello,
>>
>> I wonder if there are more interested people out there to include a
>> "postprocessing" of the HTML code via  *sed*  type search & replace
>> expressions. A tiny sed copy could be included in the brwoser and a
>> domainbased list of expressions be given to sed that modifies the html
>> code(s) according to personal tastes.
> 
> There is a nice existing and non-Tor Browser-specific tool that does
> something along these lines:
> 
> https://en.wikipedia.org/wiki/Greasemonkey
> 
> It may be a bit more elaborate than what you were thinking of but it's
> a nice tool that can handle a variety of use cases -- and should be
> fully compatible with Tor Browser already.
> 
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

