4 ms·

What kind of API do you see as valuable for something like that, disconnecting the ownership and control of data from stewardship? Can you see a design for some

by tmzt 13y ago

What kind of API do you see as valuable for something like that, disconnecting the ownership and control of data from stewardship? Can you see a design for something that would applicable to other products, whether it was built on S3 or a new shared data source, distributed solution, opaque data protection, etc. Would Firebase supporting API keys that can be delegated by the data owner, rather than the application provider, be a solution on the transactional/database side? I started thinking more about this following Fred Wilson's post on how this is happening in the investment community, as well as his vision for the future of VC (as I understand it). http://www.avc.com/a_vc/2013/06/decoupling-advisory-from-custody.html http://www.avc.com/a_vc/2013/06/decoupling-advisory-from-cus... As I mentioned on comments there, I'm working on a concept in a different area but with the same fundamental pattern, which I see emerging as we desire more ownership and control of our assets, and permanency of data and other resources. I'm also working on a blog post about this.

jmathai 13y ago
Not sure I understand exactly but I'll take a stab at answering. For us, the API needs to simply abstract how and where data is stored. The same API works for any supported storage service. We've open source large parts of our code and that falls under the "stewardship" banner. We act as a broker but make it as simple as possible if you want to be the broker yourself.
- tmzt 13y ago
  Thanks for the reply. Do you have a Github repository or some other URL for this code? Sorry for the confusion, but by "stewardship" I meant that you maintain or manipulate the data but do not control the place that is stored. I could have chosen a better word. This new model needs clearly defined terms for these roles.

4 ms·

What kind of API do you see as valuable for something like that, disconnecting the ownership and control of data from stewardship? Can you see a design for some

by tmzt 13y ago

jmathai 13y ago
Not sure I understand exactly but I'll take a stab at answering. For us, the API needs to simply abstract how and where data is stored. The same API works for any supported storage service. We've open source large parts of our code and that falls under the "stewardship" banner. We act as a broker but make it as simple as possible if you want to be the broker yourself.
- tmzt 13y ago
  Thanks for the reply. Do you have a Github repository or some other URL for this code? Sorry for the confusion, but by "stewardship" I meant that you maintain or manipulate the data but do not control the place that is stored. I could have chosen a better word. This new model needs clearly defined terms for these roles.