Delivery-Date: Thu, 20 Aug 2015 23:31:22 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,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 ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id D5DBF1E0FD0;
	Thu, 20 Aug 2015 23:31:20 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DEB8D36E34;
	Fri, 21 Aug 2015 03:31:15 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5D41C36E0A
 for <tor-talk@lists.torproject.org>; Fri, 21 Aug 2015 03:31:12 +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 Axp76zsSboC1 for <tor-talk@lists.torproject.org>;
 Fri, 21 Aug 2015 03:31:12 +0000 (UTC)
Received: from forward19m.cmail.yandex.net (forward19m.cmail.yandex.net
 [IPv6:2a02:6b8:b030::a0])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "forwards.mail.yandex.net",
 Issuer "Certum Level IV CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 2633936AE9
 for <tor-talk@lists.torproject.org>; Fri, 21 Aug 2015 03:31:12 +0000 (UTC)
X-Greylist: delayed 400 seconds by postgrey-1.34 at eugeni;
 Fri, 21 Aug 2015 03:31:12 UTC
Received: from web11m.yandex.ru (web11m.yandex.ru [IPv6:2a02:6b8:0:2519::211])
 by forward19m.cmail.yandex.net (Yandex) with ESMTP id C3D6A21A09
 for <tor-talk@lists.torproject.org>; Fri, 21 Aug 2015 06:23:56 +0300 (MSK)
Received: from 127.0.0.1 (localhost [127.0.0.1])
 by web11m.yandex.ru (Yandex) with ESMTP id 4CC0E2F20308;
 Fri, 21 Aug 2015 06:23:56 +0300 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail;
 t=1440127436; bh=PBsQ6EwPlovmR8EtyCTQv5mZ5tfC7WHlAlNsEuNSbYo=;
 h=From:To:Subject:Date;
 b=IAJ32yQ5iIA2+PMaigWkdB43zGYHceehxRL3buKvZTUFcx4/vsUyJFeHuzp3s3mpL
 0PtcB/6oDg+fQmYLNo5SK6qI2GDkURCizHm4ctPcIgMl+tP1b4bNgVFiDeCLEs8Vck
 scNWVNyfvZwKONcvHrOoWZ+nL9OIGbXfwq91HlI4=
Received: by web11m.yandex.ru with HTTP;
	Fri, 21 Aug 2015 06:23:55 +0300
From: Cain Ungothep <ungocain@yandex.com>
To: tor-talk@lists.torproject.org
MIME-Version: 1.0
Message-Id: <2374821440127435@web11m.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Fri, 21 Aug 2015 05:23:55 +0200
Subject: Re: [tor-talk] TBB 5 and Firefox Reader
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>

> Crappy design and wild adverts seem to be the norm on the Web. So
> Firefox Reader comes as a pretty useful app/extension/whatever they
> might call it.
> 
> But I see it is disabled in TBB5. Can anyone shed some light why?

I'd like to know as well.  All I could find in trac was this:

  https://trac.torproject.org/projects/tor/ticket/16786
  https://blog.torproject.org/blog/tor-browser-50-released#comment-101378

There's no explanation there, but it's possible that this part of the
code in 38 ESR just wasn't given a security-/privacy-conscious review
yet, with other more pressing work in the 5.0 pipeline.

In any case, my many-years-old workaround stays as dependable as ever:
disable js (this goes without saying, really) and disable css.
-- 
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

