top | item 27473855

(no title)

petejodo | 4 years ago

This actually reminds me of an idea I once had. Rather than service providers holding onto your data, there could be something equivalent to custodians but instead of having lockboxes for your valuables, it'd be for your data. Service providers would then "borrow" your data from these custodians to provide their services.

This looks sort of like that but marketed from the tech angle using docker as an analogy rather than a custodian. I'll have to take a deeper dive into this!

discuss

order

jakobdabo|4 years 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|4 years ago

this 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"