,
10 tweets,
2 min read
Read on Twitter
Ownership of data works very differently to ownership of physical things.
You can't actually own data, but you can own a *copy* of data. Data copies have three ownership properties: distribution, dynamism, and legitimacy.
You can't actually own data, but you can own a *copy* of data. Data copies have three ownership properties: distribution, dynamism, and legitimacy.
🚚 Distribution
In what format does the data come in (image? JSON? CSV? Text? HTML?), and through what mechanisms does it propagate (centralized? centralized + mirrors? decentralized via DHT? decentralized via gossip)?
In what format does the data come in (image? JSON? CSV? Text? HTML?), and through what mechanisms does it propagate (centralized? centralized + mirrors? decentralized via DHT? decentralized via gossip)?
Depending on the distribution, the copy you own may be less authentic than the "original" copy.
For instance, if you get a low resolution image that is rendered in an app, it is a data copy less authentic than the original image downloaded as a high resolution file.
For instance, if you get a low resolution image that is rendered in an app, it is a data copy less authentic than the original image downloaded as a high resolution file.
Also it may feel like you have ownership if you control the means of distribution.
For example, say you host an original image on your own web server. If you shutdown the server, it's not likely (but still possible!) that others are re-hosting it. Not true for Torrent, though.
For example, say you host an original image on your own web server. If you shutdown the server, it's not likely (but still possible!) that others are re-hosting it. Not true for Torrent, though.
⏳ Dynamism
Is the data static (images, videos, historical data) or dynamic (social networks, blogs, time series, chats)?
If it's dynamic, you may even own a copy of the data, but it's just a snapshot, you're not owning the *database* itself.
Is the data static (images, videos, historical data) or dynamic (social networks, blogs, time series, chats)?
If it's dynamic, you may even own a copy of the data, but it's just a snapshot, you're not owning the *database* itself.
Depending on how dynamic the database is, your ownership of data copies may feel less authentic relative to owning the database.
This is how people complain about not owning their data on Facebook despite that there exists an export feature. Downloading a snapshot isn't enough.
This is how people complain about not owning their data on Facebook despite that there exists an export feature. Downloading a snapshot isn't enough.
📜 Legitimacy
Can you prove that your data copy is equal to the original data?
People take screenshots of (e.g.) tweets, but the these have no proof of legitimacy. Tweets get legitimacy when served directly from Twitter servers.
Can you prove that your data copy is equal to the original data?
People take screenshots of (e.g.) tweets, but the these have no proof of legitimacy. Tweets get legitimacy when served directly from Twitter servers.
Centralized services use your trust in the platform for legitimacy of their data copy. If/Once the platform deletes content, other data copies (e.g. screenshots) are not legitimate enough to replace the original copy on the platform. This is how the platform has more "ownership".
Many decentralized systems (like PGP, Torrent, SSB) use cryptographic signatures to prove legitimacy of copies.
So that even if the data author deletes their copy, all the other copies are still as legitimate as the original. This may *feel* like the author can't delete data.
So that even if the data author deletes their copy, all the other copies are still as legitimate as the original. This may *feel* like the author can't delete data.
The thread above is why I think it's pointless to talk about *owning your data*. We should instead talk about the authenticity and usefulness of data copies, and whether you control its distribution or not.
