Delivery-Date: Mon, 03 Nov 2014 22:06:02 -0500
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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 E78941E0CF8;
	Mon,  3 Nov 2014 22:06:00 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6269D31788;
	Tue,  4 Nov 2014 03:05:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A802031782
 for <tor-talk@lists.torproject.org>; Tue,  4 Nov 2014 03:05:54 +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 TAxFdaDaa4ZK for <tor-talk@lists.torproject.org>;
 Tue,  4 Nov 2014 03:05:54 +0000 (UTC)
Received: from turtles.fscked.org (turtles.fscked.org [76.73.17.194])
 by eugeni.torproject.org (Postfix) with ESMTP id 878CD31741
 for <tor-talk@lists.torproject.org>; Tue,  4 Nov 2014 03:05:54 +0000 (UTC)
Date: Mon, 3 Nov 2014 19:05:45 -0800
From: Mike Perry <mikeperry@torproject.org>
To: tor-talk@lists.torproject.org
Message-ID: <20141104030545.GK21428@torproject.org>
References: <CADw1SfEvdtayywkz3jo3gnFtDRqdwwtcV2+iRuBej4tH8h6Rqw@mail.gmail.com>
 <20141103230522.GJ21428@torproject.org>
MIME-Version: 1.0
In-Reply-To: <20141103230522.GJ21428@torproject.org>
Subject: Re: [tor-talk] Krypton Anonymous: A Chromium Tor Browser
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: multipart/mixed; boundary="===============5119941063613136659=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


--===============5119941063613136659==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="45wMVEkw4XUbiYON"
Content-Disposition: inline


--45wMVEkw4XUbiYON
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Mike Perry:
> Cyrus Katrak:
> > https://github.com/kr36/seaturtle
> >=20
> > At a high level:
> > - Process per tab security model, with each tab owning it's own in-memo=
ry
> > state (cache, cookies, local storage, hsts db etc...).
>=20
> We've been going for URL bar domain isolation in Tor Browser to avoid
> divergence with how users expect the browser to behave:
> https://www.torproject.org/projects/torbrowser/design/#philosophy
> https://www.torproject.org/projects/torbrowser/design/#identifier-linkabi=
lity
>=20
> Even still, per-tab isolation is a common request, so it's easy to
> assume that this is what most people really want. But I think if you
> think through how it will work in practice, it becomes fairly clear it's
> actually a very bad property for usability.
>=20
> The easiest way to see how per-tab isolation will cause confusion is to
> imagine the twitter use case. In a normal twitter user flow, the user
> logs in to twitter, opens some lists and conversations (often in new
> tabs), perhaps opens tweetdeck in a new tab, follows links from people
> in their feed, and sends and receives twitter conversation links from
> their friends over DM, chat, IRC, and email.=20
>=20
> If each these actions happens in a new, isolated tab, the user will be
> forced to log in repeatedly to twitter, and worse, forget which tabs
> they logged in to twitter on, especially once they start following links
> (both on and off site) from people's feeds.

Actually, I should point out that I'd love to hear hard data on this, in
case I'm wrong.

I did some testing, and most interactions on twitter seem to in fact be
designed to keep you in the same tab while following links on the site,
but open all off-site links in independent tabs. At least in TBB on the
desktop.

I bet sites like Facebook, Google, and Twitter have data on how many of
their users end up using multiple tabs/windows vs staying in the same
tab until logout. It could be that I'm wrong and that
multitab/multiwindow users are not the norm for these services.



--=20
Mike Perry

--45wMVEkw4XUbiYON
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJUWEKJAAoJEEEC+JXS8eGGurQP/3yKwWgvRJqsTgG0Iqyrta0t
A/x+y57WNNdW7DDW62YsQybjq06Nc5WGSMHyceG0j1eEd21lkK2zh7QyZIH8ZV7M
r1+P0GWc0RRSZkg1r6F+Cq67FjdzVo59VvWypl70QsPRQSI7U2qk4vpKmYRSrT51
7zg4bINAL27in+oyzU+gzkxBGW7zNalbstorYZJ55J+2H86oN+PudAPD5qDi2gwq
cepxpXCammL/4l8i0dERD2WYPoJiVcbJg1tcPI+ixh0c2mdV12uwZ0Dew0a5FjGr
H+xTIKiSoeR8j2yRg9wsxJqkarF1lHDqES7ueTF2B568fW+qghRDELErWiptFdgB
Fe+PadFrjaoQELM2k9x28lX+fKzOUrJxWrW9ECH4z0Bbpn/3Gw2VCwGEzdYXjQd7
nR+uMzwCmAbjxhhaX2k0tXMv4PktdGpPInbmqWHnN1FqFy0C0NcrLeQsq4vXD1lS
bESjfosYJIRjj0ROvEwKkpQIkYhoNDYTgR+L6NeTl/45rkMRKAaETFR14xTPwUVY
r82T9WVRt/tVsSIh8FD78Jp0VwYoCXaPg00qkcUvsaKDHtEu/Z9JX8yNohHvO5uD
pvlEk+mvc4dc2Hlh/VfoirfmgB1Jvj+t76VOwKcFIa1epC9YcH2kLatfwNYsOYX5
B4jU44UZozpLbkQqaBuT
=tboi
-----END PGP SIGNATURE-----

--45wMVEkw4XUbiYON--

--===============5119941063613136659==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
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

--===============5119941063613136659==--

