W3C home > Mailing lists > Public > public-privacy@w3.org > January to March 2015

Re: 'persona', indicating 'private browsing mode' over the net

From: Karl Dubost <karl@la-grange.net>
Date: Wed, 4 Mar 2015 10:52:42 +0900
Cc: David Singer <singer@apple.com>, Joseph Lorenzo Hall <joe@cdt.org>, "public-privacy (W3C mailing list)" <public-privacy@w3.org>
Message-Id: <92DCA42B-A253-4381-96E4-CA79F6F12832@la-grange.net>
To: ifette@google.com

Le 4 mars 2015 à 08:20, Ian Fette (イアンフェッティ) <ifette@google.com> a écrit :
> But you're asking every other site to build in something like that -- the household Amazon Prime account becomes "John's purchases" and "Jane's purchases". Or the kid-at-college's purchases. That's a rather large ask for a lot of sites…

In the spirit of not being perfect but human. Physical shops handle this quite well.

Outside of the browser world, If I buy a gift for someone else, there are many cases:
* The person is in a different realm than mine (location and money). No issue apart the word of mouth
* The person is in the same location than me. I'm trying to seal my whereabouts (different time, different same brand shop in the city, asking the shop owner to keep it secret (trust), etc.)
* The person has access to the record of my payments (bank slip). My strategy will be to use paper money or another payment option which doesn't leave trace.

On the Web
* Many sites are asking for unnecessary personal details wrt the execution of the task
* Many sites are considering a browser, an IP, a cookie == 1 person.

The discussion here revolves around having a good relationship with sites (which is not happening).
But more of a guerrilla strategy on how to avoid to be the prey. We have less power than in the physical world. And it's why it's so hard in terms of UX as Ian mentioned. Only a little number of people are ready to go on Guerrilla for protecting a bit of their privacy (whatever the reasons).
Example: you need to give a **mobile phone** number for using some online messaging app such as Line or whatsapp. 

Sites owners which feel there is a business benefit of having multi-profiles, silos, sealed information will implement. The others will not implement at a scale that will matter for the rest of us.

Poney and rainbow moment: I wish the data where on my side (body integrity in the physical world) and that sites needs an authorization to access things on my side at the moment of the transaction and not the opposite as it is currently the case. (not happening, will not happen).

I have the feeling that people will understand better these issues if they were more visible, aka if the browser was exposing more the consequences of internet usage. You are searching a plane ticket on Amazon, the **browser** could suggest: "open a private window for possibly saving money". etc. The difficulties being to guess the intent and not spam the user with tons of messages. Chaos and Nightmares.

Karl Dubost 🐄
Received on Wednesday, 4 March 2015 01:53:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 4 March 2015 01:53:05 UTC