4 ms·
I've had some thoughts about it too. In addition, I think, entities which want a piece of your data, should be able to somehow define "queries" and the "custodi
by jakobdabo 5y ago
I've had some thoughts about it too. In addition, I think, entities which want a piece of your data, should be able to somehow define "queries" and the "custodian" (in your terms) should be able either to tell yes or no (if you accept to answer to the query).
I imagine it this way, you have some kind of device, wanna drink in a bar? The bartender can "query" whether you are over 21 or not, you see the query, authenticate (with bio and pin/password) and your device confirms that you are over 21.
Wanna take a credit, the entity queries to check if your credit score is over 9000, and if you agree to let them know then your device just answers yes/no.
But there must be ways to protect the data, ideally the data should be encrypted at rest (wherever) and decrypted only in your device in some kind of secure enclave, so that your custodian can sign the result of the query being sure that it is not altered.
- lurkerasdfh8 5y agothis is just a convoluted way to access information. Imagine the use case you want to apply a filter to all your photos. Either you give service provider access to all your photos, or they give you access to run the code out of their control. There's no way to compromise this. For this reason SOLID is pointless too. It is just a fancy way to saying "everyone will pay for their own S3 bucket and give access to random directories to random companies, oh and pay for the entire bandwidth"
- viraptor 5y agoThere's no currently practical way to compromise. On theory we have homomorphic encryption which would be able to apply filters over opaque data. But it's not fast enough yet.