time and data - sharing the future, forgetting the past

Le 8 avr. 2011 à 14:09, SULLIVAN, BRYAN L (ATTSI) a écrit :
> enabling at least the disclosure of developer intent for use of private data, and if possible usable (e.g. effective UIs and control options for the user) means for the user to express their awareness and consent.

One of the issues I have with most EULA & privacy policies available out there is that they are binary. In the physical world, we change our privacy policies all the time and we do it by our own decisions and actions. 

There is also the way the system itself is designed. Autonomy (ACLs), history (logs), etc. For example, *time* is a key into factoring a privacy environment. Take a very simple example.

When you meet someone in the physical world, you can start the discussion by giving information about yourself. This information is careful given depending on the context of the meeting. It might happen that you are building the history as you speak and not giving anything about your past explicitly. (to make it easier to understand, for example, the name of your previous company).

On digital social networks, once people are granted you are not sharing the now (present) and the future, but also the full past. For example, on a "closed" twitter account, the person would be able to read the full past timeline. This doesn't allow a very interesting feature of our relationships, where we build ourselves with a lot of diversity.

Time comes up also into forgetting. People forget about you and your actions. Systems very rarely. Data which have been acquired are kept… for a very long time (identifiable or not). It also has consequences.

-- 
Karl Dubost - http://dev.opera.com/
Developer Relations & Tools, Opera Software

Received on Friday, 8 April 2011 21:38:52 UTC