Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reviewing for Gaia usage #149

larrysalibra opened this issue Sep 3, 2019 · 2 comments


Copy link

commented Sep 3, 2019

Reviewing for use of gaia is challenging. Our current standard is that apps that write any data to gaia receive full marks. Even with this very low and simple to meet standard, it's not always clear if an app doesn't use Gaia or we are unable to find that app’s use of Gaia.

Proposal: As part of the monthly app mining submission process, developers should explain how Gaia is used by their app . Reviewers will follow those instructions to verify Gaia usage.


This comment has been minimized.

Copy link

commented Sep 3, 2019

The implementation for this is probably similar to #138.


This comment has been minimized.

Copy link

commented Sep 3, 2019

@larrysalibra Do you want to prevent server processing of data completely?

We had years of pushing cloud computing and many many libraries and tools to make life easier while putting processing on the server-side.
Take image processing as an example; we can not easily put OpenCV in every user mobile phone. Even if we can, battery life and network usage will be problematic.

I think this issue contains two parts, privacy and data ownership.
Data ownership will be easily done with bounding servers to do the write with a separate encryption key for every call and clients verify that.
But client-side encryption will exclude almost all cloud computing and leave us with cloud storage.
I love to see if we can find a way to do cloud computing, just like Blockstack did with solving identity and storage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.