consensus
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU/consensus] [RFC][SH] User Data Manifesto


From: Melvin Carvalho
Subject: Re: [GNU/consensus] [RFC][SH] User Data Manifesto
Date: Sun, 15 Nov 2015 23:34:02 +0100



On 1 January 2013 at 01:17, hellekin (GNU Consensus) <address@hidden> wrote:
http://userdatamanifesto.org/ proposes 8 points "defining basic rights
for people to control their own data in the internet age"

I'd like to reach consensus on officially supporting this manifesto:

Resurrecting an old thread.  I've been pondering this for the last couple of years, and I think I have worked out some basic common issues:

UDM 2.0 is a good start but it doesnt address the basic issues that we have.  ie we dont have data freedom, in a practical sense.  Even those loving free software are not always offering data freedom.  Often we dont know what it means, so let's teach people.

The general high level aim of data freedom is complete control over all your data.  I divide it into two sections:

1. Where it is stored

This is about the data being able to control where the data is stored and perform operations on that data.

1.1 The user can choose where the data is stored

1.2 The user is free to view all their data.

1.3 The user is free to modify all their data the way they want, including adding arbitrary new fields, deleting anything existing

1.4 The user is free to move their data, provided that they are responsible for links to the old location


2. How the data is stored

2.1 The user is entitled to share their data, including on a global scale

2.2 The user can choose the format in which the data is stored (conforming to common standards)

This is PARTICULARLY important.  The USER decides NOT the developer. 

2.3 The user is able to protect and privacy control their data, determining exactly who sees what

2.4 The user is entitled to notify other users when updates to their data occurs

I think this is roughly what you need.  Take your own system and rate yourself honestly on how well you do.  I noticed those that signed up to UDM 2.0 didnt always pass the tests.

Too long have we been in a world were users have 90% freedom but cant get the last most important bit of power out of their machines.  The problem now isnt proprietary software, it's developer restrictions.  Let's open our eyes to where we are failing.

I believe we've got a great system that ready to deliver data freedom on the web, which should be a key strategic battle ground

https://github.com/solid/solid-spec

I spoke to frank (owncloud) last week, and I think there could be the basis of collaboration on here.

But we need much more help, to make this happen.  Let's free people's data and reclaim the internet!
 

==
hk

1. Own the data
The data that someone directly or indirectly creates belongs to the
person who created it.

2. Know where the data is stored
Everybody should be able to know: where their personal data is
physically stored, how long, on which server, in what country, and what
laws apply.

3. Choose the storage location
Everybody should always be able to migrate their personal data to a
different provider, server or their own machine at any time without
being locked in to a specific vendor.

4. Control access
Everybody should be able to know, choose and control who has access to
their own data to see or modify it.

5. Choose the conditions
If someone chooses to share their own data, then the owner of the data
selects the sharing license and conditions.

6. Invulnerability of data
Everybody should be able to protect their own data against surveillance
and to federate their own data for backups to prevent data loss or for
any other reason.

7. Use it optimally
Everybody should be able to access and use their own data at all times
with any device they choose and in the most convenient and easiest way
for them.

8. Server software transparency
Server software should be free and open source software so that the
source code of the software can be inspected to confirm that it works as
specified.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]