From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: Tor Browser Date: Thu, 11 Aug 2016 08:51:36 +0000 Message-ID: <87twervgbr.fsf@we.make.ritual.n0.is> References: <20160623104107.GA2505@shadowwalker> <20160623132347.GA9193@shadowwalker> <87a8ia7pq4.fsf@gnu.org> <20160624134357.GA30727@shadowwalker> <87por637vi.fsf_-_@gnu.org> <20160624174913.GA19633@shadowwalker> <87r3bkmfja.fsf@gnu.org> <87bn2kxirt.fsf@we.make.ritual.n0.is> <87mvm355r3.fsf@gnu.org> <87fuqjmj7z.fsf@we.make.ritual.n0.is> <87shuisfst.fsf@gmail.com> <87mvkqxi7x.fsf@we.make.ritual.n0.is> <87twevbsbu.fsf@gmail.com> <87popgv1eg.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46586) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bXliK-0003Ey-1C for guix-devel@gnu.org; Thu, 11 Aug 2016 04:51:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bXliH-000222-EJ for guix-devel@gnu.org; Thu, 11 Aug 2016 04:51:43 -0400 Received: from mithlond.libertad.in-berlin.de ([2001:67c:1400:2490::1]:38670 helo=beleriand.n0.is) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bXliH-00021t-1r for guix-devel@gnu.org; Thu, 11 Aug 2016 04:51:41 -0400 In-Reply-To: <87popgv1eg.fsf@netris.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mark H Weaver , Alex Vong Cc: guix-devel@gnu.org Hi, Mark H Weaver writes: > Alex Vong writes: > >> ng0 writes: >> >>> Alex Vong writes: >>> >>>> Finally, I agree that icecat could switch to tor browser as its upstream. >>> >>> Maybe you want to help me out with writing the email / post to >>> torproject: >>> https://lists.gnu.org/archive/html/guix-devel/2016-08/msg00326.html >>> >>> On second note, maybe this is message should be addressed to both >>> torproject and icecat developer(s). What do you think? I have no fixed >>> plan in mind for this. >>> >> Hmm, maybe I will give my (rough) idea here. In my opinion, icecat has 2 >> important features, librejs (gpl3+) and the lack of non-free addons >> suggestion. > > We would also need to remove Firefox support for DRM (e.g. EME), avoid > steering users to non-free media codecs, and maybe some other things to > meet the requirements of the GNU FSDG. > > I suspect that these changes are substantial enough that we'll need to > change the branding, and avoid using the Firefox trademark, but I'm not > sure. I think there's a need to change the branding. Gentoo ships a firefox with a huge patchset applied and uses a branding with some changes (Aurora). I'd like to get the icecat developer involved in the discussion at some point, to get additional input and find out where help is needed. I think the same idea like for many projects applies for Icecat: when you get involved, bugfixing is faster. Icecat has the bug of being based on an insecure firefox version - let's help to move it somewhere safe. >> For librejs, TBB already have noscripts, although they serve different >> purposes (librejs intends to block non-free js only), I doubt devs would >> want to include 2 js blocker addons. But I think html5 everyhere will be >> a good addon for TBB since most html5 player requires js. Currently, >> enabling noscript breaks most video-playing sites. >> >> For the lack of non-free addons suggestion, TBB recommends not to >> install addon, but the addon page is still there, which suggest non-free >> addons. I don't really know what should we do here. > > The IceCat project maintains a page of free addons. I guess we should > use that. With our gentoo overlay, we started to include addons to be installed from outside the mozilla addon store, as the gentoo firefox is configured to have a system controlled addon location. Now starting with FF 48, addons will only be able to be installed from the official FF store, but I think this setting can be turned off hopefully. We (ybti overlay) discussed a similar approach for Guix, to configure firefox based browsers (and others) to additionally use addons from Guix, to allow more control of what's included etc. > I agree that the best outcome would be for IceCat to switch to Tor > Browser as its upstream, Agreed, but... > or at least to borrow heavily from their patch > set. > ...maybe that is not completely necessary, the bugtracker link of firefox which I was passed recently shows that firefox and torbrowser want to upstream the patchset of torbrowser. > Thanks, > Mark -- ♥Ⓐ ng0 For non-prism friendly talk find me on http://www.psyced.org