From owner-freebsd-chromium@FreeBSD.ORG Mon May 23 15:40:17 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7769106564A for ; Mon, 23 May 2011 15:40:17 +0000 (UTC) (envelope-from evanm@google.com) Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by mx1.freebsd.org (Postfix) with ESMTP id 6B6ED8FC15 for ; Mon, 23 May 2011 15:40:16 +0000 (UTC) Received: from kpbe17.cbf.corp.google.com (kpbe17.cbf.corp.google.com [172.25.105.81]) by smtp-out.google.com with ESMTP id p4NFeF7a031477 for ; Mon, 23 May 2011 08:40:15 -0700 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1306165216; bh=D3MjWpG7hq7xv5+ZQWatsBvaDK4=; h=MIME-Version:Sender:In-Reply-To:References:Date:Message-ID: Subject:From:To:Cc:Content-Type:Content-Transfer-Encoding; b=RYud6MlN9mVbovVy/13MOvYnUvcfDvN7aTIKQ54Fq5K9NitbrkpDIeBKSsVcSbqQk 2PgMEqzV2q3H+T1JLSYEg== Received: from gyg8 (gyg8.prod.google.com [10.243.50.136]) by kpbe17.cbf.corp.google.com with ESMTP id p4NFdLj8024126 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Mon, 23 May 2011 08:40:14 -0700 Received: by gyg8 with SMTP id 8so2173367gyg.10 for ; Mon, 23 May 2011 08:40:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2NGMO+mImxzSvPT6vhE9oJj4retDxY4xTWIZcHjvR58=; b=kNDsFx1lAUPKo3zU61UOGGckm40XkK5kjR1RlpP/8LAHTW1pHpVpPOhFdEcTjq+vY1 6ALBT2GzTv4FW7J3DqEw== DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=JDQd88fIzXj2vV/CrgkGvTRWOr7rBfCR3iQnSB1VIJ6IFnPfo92mkyu2h+w0SS/5Lv X37NTxfV6V/zE1pXC1CA== MIME-Version: 1.0 Received: by 10.101.175.1 with SMTP id c1mr4304006anp.99.1306165213860; Mon, 23 May 2011 08:40:13 -0700 (PDT) Sender: evanm@google.com Received: by 10.101.1.17 with HTTP; Mon, 23 May 2011 08:40:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 May 2011 08:40:13 -0700 X-Google-Sender-Auth: 2Xrog2geB_z87o-xPdytuGLuEd8 Message-ID: From: Evan Martin To: =?ISO-8859-1?Q?Ren=E9_Ladan?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true Cc: chromium@freebsd.org Subject: Re: Chromium on FreeBSD presentation X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 15:40:18 -0000 On Mon, May 23, 2011 at 12:07 AM, Ren=E9 Ladan wrote: > I gave a presentation during BSDCan about Chromium, the sheets are > available here: > ftp://rene-ladan.nl/pub/chromium-bsdcan.pdf For what it's worth, we take privacy seriously and our bad reputation is not deserved. It is frustating to see you call out "spy code" in the header of a slide. Features you mention on that slide, like geolocation, require the user to explicitly grant that information to the site that requests it (geolocation uses an infobar, sync you must first enable through the preferences, etc.). The malware/phishing blocking code goes to great effort to avoid sending information about the URLs you're visiting. Features like that, where there is a utility/privacy tradeoff, are clearly grouped together under a "privacy" heading in the preferences. Here's more about privacy in Chrome: http://www.google.com/intl/en/landing/chrome/google-chrome-privacy-whitep= aper.pdf If you ever find any code that does something you find problematic from a privacy standpoint, I would love to hear about it.