decentralized-identity / confidential-storage

Confidential Storage Specification and Implementation
https://identity.foundation/confidential-storage/
Apache License 2.0
80 stars 23 forks source link

Where to store/reference source files? #20

Closed csuwildcat closed 4 years ago

csuwildcat commented 7 years ago

Example: if the user or an app stores an image, where is the file's source stored and referenced? Do we need a `/assets' to house this?

shea256 commented 7 years ago

We're discussing this a bit in this thread: https://github.com/blockstack/blockstack-desktop-specs/issues/4

csuwildcat commented 7 years ago

@shea256 I read through that thread, but it's not clear how/what translates back to the user's Hub instances. I am trying to decode how you will be routing the user/app-centric API model of the higher-level Blockstack app, to a Hub. Given the Hubs aren't solely users or apps, and their connected entities are not just users or apps, I want to better understand your approach.

csuwildcat commented 7 years ago

Example: your Tesla car may have its own hub, and it could have both apps and users connected to it. This is to illustrate the fact that apps are really just another type of entity, so we have to be sure that we are cognizant of a world that is far beyond the simplistic user/app paradigm of the current web.

cvan commented 7 years ago

Is it possible to have a store that is agnostic to entity associations?

There could be namespaced buckets. I kind of liked how npm now does user-scoped vs. global (standard, reserved-name) packages. Any ideas, interest in borrowing that or applying a similar pattern?

csuwildcat commented 7 years ago

@cvan totally open to it, just need to answer that question as we move past simple object storage, which I bet will happen in ~4 weeks.

ajunge commented 5 years ago

@csuwildcat any update on this?