4 ms·

A peer to peer encrypted datastore that everyone can use to store their own metadata. Facebook knows what movies I like and interests I have, Spotify knows wha

A peer to peer encrypted datastore that everyone can use to store their own metadata. Facebook knows what movies I like and interests I have, Spotify knows what songs I listen to, Amazon knows what books I like to read. All of these pieces of data are currently silo'd and controlled by private corporations many of which can do whatever they like with that data. I want a private encrypted datastore that does this instead. Peer to peer so nobody controls it or can kill it. And controlled by you so Government can't get access. You set up a node and contribute CPU power and disk space. Then you get a private address and key and can push small pieces of metadata to it. This data is mirrored and very redundant so it won't disappear if some nodes go offline. Then any site can integrate with this store. People will build libraries to write to it with various languages and others will build websites which make it easy for the layman to store and get data from it. People could create online "metadata banks" so that less technical people don't have to run their own node. Integrating with this datastore will eventually be as easy as integrating with current oauth services. Having one global system not controlled by anyone also means there's now a standardized way for any service to request access to your data. They don't have to specifically integrate with Facebook, Spotify, Bandcamp, Last.fm etc, they just have one integration point and you can choose what data you want to share with them. And in theory it will live on forever so as future services grow and die your data doesn't die with it.

tixocloud 10y ago
Great idea. I was just thinking about this the other day and I too would be interested in something like this.
hossbeast 10y ago
Sounds like this? https://keybase.io/docs/kbfs https://keybase.io/docs/kbfs
websterisk 10y ago
...and phone number and physical address and all of the other "real-life" metadata that is commonly defined but disparately stored/leveraged/shared.
CapacitorSet 10y ago
That seems like a nice use case for ipfs: https://ipfs.io/ https://ipfs.io/ As of now there is no automatic mirroring, because nodes only store the data they request, but in the future one will use filecoin (http://filecoin.io/ http://filecoin.io/) to incentivize mirroring.
boltn 10y ago
This is an idea that'll start gaining traction over the next few years. I was thinking of building something like this out in go backed by storj.io just the other day. We're also starting to see others like the aforementioned keybase filesystem, ipfs, maidsafe, etc.
adbge 10y ago
I won't pretend to exactly understand Urbit, but it seems to be more or less what you're describing: > In an Urbit world, your data is no longer trapped in a jumble of proprietary servers. Your urbit is a permanent, versioned, typed archive the size of your digital life. Even before you move your data from a Web service to a local Urbit app, your urbit can drive your account with an API or scraper. http://urbit.org/posts/overview/ http://urbit.org/posts/overview/
Qwertystop 10y ago
Interesting. Major problem: Either existing services need to shift gears to support this third-party that reduces their control over data (when often, your data is how they make their money), or else new equivalent services using said third-party need to be made and meaningfully dislodge them (difficult, inertia is a thing).
- TimJRobinson 10y ago
  These services already have apis that give up the data. So anyone could build data extractors that allow you to regularly pull your Metadata from them and store it in this new datastore. Only the consumers of the data need to change their behavior. If there's easy to use libraries to access the data store and enough demand for it then more and more consumers will adopt it over time.
fian 10y ago
Sounds like something you could build on top of Retroshare: http://retroshare.net/ http://retroshare.net/ If you can export the meta data you want from Facebook et al then you should be able to find a way to share it in an encrypted peer-to-peer network.
foobar16372883 10y ago
I like this but how do you make sure that Facebook gives all the data that they collect directly from the user back into the system? Perhaps an audit system which compares data shown to the user on Facebook to what the system knows Facebook contributed?

tixocloud 10y ago

Great idea. I was just thinking about this the other day and I too would be interested in something like this.

hossbeast 10y ago

Sounds like this? https://keybase.io/docs/kbfs https://keybase.io/docs/kbfs

websterisk 10y ago

...and phone number and physical address and all of the other "real-life" metadata that is commonly defined but disparately stored/leveraged/shared.

CapacitorSet 10y ago

That seems like a nice use case for ipfs: https://ipfs.io/ https://ipfs.io/ As of now there is no automatic mirroring, because nodes only store the data they request, but in the future one will use filecoin (http://filecoin.io/ http://filecoin.io/) to incentivize mirroring.

boltn 10y ago

This is an idea that'll start gaining traction over the next few years. I was thinking of building something like this out in go backed by storj.io just the other day. We're also starting to see others like the aforementioned keybase filesystem, ipfs, maidsafe, etc.

adbge 10y ago

I won't pretend to exactly understand Urbit, but it seems to be more or less what you're describing: > In an Urbit world, your data is no longer trapped in a jumble of proprietary servers. Your urbit is a permanent, versioned, typed archive the size of your digital life. Even before you move your data from a Web service to a local Urbit app, your urbit can drive your account with an API or scraper. http://urbit.org/posts/overview/ http://urbit.org/posts/overview/

Qwertystop 10y ago

Interesting. Major problem: Either existing services need to shift gears to support this third-party that reduces their control over data (when often, your data is how they make their money), or else new equivalent services using said third-party need to be made and meaningfully dislodge them (difficult, inertia is a thing).

TimJRobinson 10y ago
These services already have apis that give up the data. So anyone could build data extractors that allow you to regularly pull your Metadata from them and store it in this new datastore. Only the consumers of the data need to change their behavior. If there's easy to use libraries to access the data store and enough demand for it then more and more consumers will adopt it over time.

fian 10y ago

Sounds like something you could build on top of Retroshare: http://retroshare.net/ http://retroshare.net/ If you can export the meta data you want from Facebook et al then you should be able to find a way to share it in an encrypted peer-to-peer network.

foobar16372883 10y ago

I like this but how do you make sure that Facebook gives all the data that they collect directly from the user back into the system? Perhaps an audit system which compares data shown to the user on Facebook to what the system knows Facebook contributed?